holm/nushell
1
1
Fork 0
forked from extern/nushell
Code Issues Pull Requests Packages Projects Releases Wiki Activity
ee5a18167c
nushell/Cargo.lock

6480 lines
151 KiB
Plaintext
Raw Normal View History

objectshell initial commit
2019-05-10 18:59:12 +02:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
Begin directory contrib docs and split commands (#3650) * Begin directory contrib docs and split commands * Fix unused import warning
2021-06-19 02:06:44 +02:00
version = 3
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
[[package]]
name = "addr2line"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.21.0"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "8a30b2e23b9e17a9f90641c7ab1549cd9b44f296d3ccbf309d2863cfe398a0cb"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
dependencies = [
"gimli",
]
Data summarize reporting overhaul. (#2299) Refactored out most of internal work for summarizing data opening the door for generating charts from it. A model is introduced to hold information needed for a summary, Histogram command is an example of a partial usage. This is the beginning. Removed implicit arithmetic traits on Value and Primitive to avoid mixed types panics. The std operations traits can't fail and we can't guarantee that. We can handle gracefully now since compute_values was introduced after the parser changes four months ago. The handling logic should be taken care of either explicitly or in compute_values. The zero identity trait was also removed (and implementing this forced us to also implement Add, Mult, etc) Also: the `math` operations now remove in the output if a given column is not computable: ``` > ls | math sum ──────┬────────── size │ 150.9 KB ──────┴────────── ```
2020-08-04 00:47:19 +02:00
[[package]]
name = "adler"
Move script to nu engine (#3092) * Move run_script to engine * Add which dep and feature to engine * Change unwrap to expect * Add wasm specification * Remove which from default, add specification correctly * Add nu-platform-specifics * Move is_external_cmd to platform_specifics * Add is_external_cmd to host and use it instead of nu_platform directly * Clean up if else logic in is_external_cmd * Bump nu-platform-specifics version * Pass context to print_err * Commit cargo.lock * Move print functions to own module inside nu-engine * Hypocratic change to run windows-nightly again * Add import for Ordering * Move printing of error to host * Move platform specific which functionality to basic host * Allow no use of cmd_name * Fix windows compile issue
2021-03-12 06:20:54 +01:00
version = "1.0.2"
Data summarize reporting overhaul. (#2299) Refactored out most of internal work for summarizing data opening the door for generating charts from it. A model is introduced to hold information needed for a summary, Histogram command is an example of a partial usage. This is the beginning. Removed implicit arithmetic traits on Value and Primitive to avoid mixed types panics. The std operations traits can't fail and we can't guarantee that. We can handle gracefully now since compute_values was introduced after the parser changes four months ago. The handling logic should be taken care of either explicitly or in compute_values. The zero identity trait was also removed (and implementing this forced us to also implement Add, Mult, etc) Also: the `math` operations now remove in the output if a given column is not computable: ``` > ls | math sum ──────┬────────── size │ 150.9 KB ──────┴────────── ```
2020-08-04 00:47:19 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Move script to nu engine (#3092) * Move run_script to engine * Add which dep and feature to engine * Change unwrap to expect * Add wasm specification * Remove which from default, add specification correctly * Add nu-platform-specifics * Move is_external_cmd to platform_specifics * Add is_external_cmd to host and use it instead of nu_platform directly * Clean up if else logic in is_external_cmd * Bump nu-platform-specifics version * Pass context to print_err * Commit cargo.lock * Move print functions to own module inside nu-engine * Hypocratic change to run windows-nightly again * Add import for Ordering * Move printing of error to host * Move platform specific which functionality to basic host * Allow no use of cmd_name * Fix windows compile issue
2021-03-12 06:20:54 +01:00
checksum = "f26201604c87b1e01bd3d98f8d5d9a8fcbb815e8cedb41ffccbeb4bf593a35fe"
Data summarize reporting overhaul. (#2299) Refactored out most of internal work for summarizing data opening the door for generating charts from it. A model is introduced to hold information needed for a summary, Histogram command is an example of a partial usage. This is the beginning. Removed implicit arithmetic traits on Value and Primitive to avoid mixed types panics. The std operations traits can't fail and we can't guarantee that. We can handle gracefully now since compute_values was introduced after the parser changes four months ago. The handling logic should be taken care of either explicitly or in compute_values. The zero identity trait was also removed (and implementing this forced us to also implement Add, Mult, etc) Also: the `math` operations now remove in the output if a given column is not computable: ``` > ls | math sum ──────┬────────── size │ 150.9 KB ──────┴────────── ```
2020-08-04 00:47:19 +02:00
Expose polars avro support (#10019) # Description Exposes polars avro support via dfr open and dfr to-avro --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-08-16 03:31:49 +02:00
[[package]]
name = "adler32"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "aae1277d39aeec15cb388266ecc24b11c80469deae6067e17a1a7aa9e5c1f234"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
[[package]]
name = "ahash"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.8.6"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "91429305e9f0a25f6205c5b8e0d2db09e0708a7a6df0f42212bb56c32c8ac97a"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"getrandom",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"once_cell",
"version_check",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"zerocopy",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "aho-corasick"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "1.1.2"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "b2969dcb958b36655471fc61f7e416fa76033bdd4bfed0678d8fee1e2d07a1f0"
objectshell initial commit
2019-05-10 18:59:12 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"memchr",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
[[package]]
name = "alloc-no-stdlib"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
version = "2.0.4"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
checksum = "cc7bb162ec39d46ab1ca8c77bf72e890535becd1751bb45f64c597edb4c8c6b3"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
[[package]]
name = "alloc-stdlib"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
version = "0.2.2"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
checksum = "94fb8275041c72129eb51b7d0322c29b8387a0386127718b096429201a5d6ece"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
dependencies = [
"alloc-no-stdlib",
]
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
[[package]]
name = "allocator-api2"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.2.16"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "0942ffc6dcaadf03badf6e6a2d0228460359d5e34b57ccdc720b7382dfbd5ec5"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
enable cd to work with directory abbreviations (#5452) * enable cd to work with abbreviations * add abbreviation example * fix tests * make it configurable
2022-05-06 14:58:32 +02:00
[[package]]
name = "alphanumeric-sort"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "1.5.3"
enable cd to work with directory abbreviations (#5452) * enable cd to work with abbreviations * add abbreviation example * fix tests * make it configurable
2022-05-06 14:58:32 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "d67c60c5f10f11c6ee04de72b2dd98bb9d2548cbc314d22a609bfa8bd9e87e8f"
enable cd to work with directory abbreviations (#5452) * enable cd to work with abbreviations * add abbreviation example * fix tests * make it configurable
2022-05-06 14:58:32 +02:00
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
[[package]]
name = "android-tzdata"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e999941b234f3131b00bc13c22d06e8c5ff726d1b6318ac7eb276997bbb4fef0"
Bump chrono dependency to fix panic (#6317)
2022-08-13 20:21:28 +02:00
[[package]]
name = "android_system_properties"
Bump iana-time-zone from 0.1.44 to 0.1.47 (#6448) Bumps [iana-time-zone](https://github.com/strawlab/iana-time-zone) from 0.1.44 to 0.1.47. - [Release notes](https://github.com/strawlab/iana-time-zone/releases) - [Changelog](https://github.com/strawlab/iana-time-zone/blob/main/CHANGELOG.md) - [Commits](https://github.com/strawlab/iana-time-zone/compare/0.1.44...v0.1.47) --- updated-dependencies: - dependency-name: iana-time-zone dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-08-31 13:19:20 +02:00
version = "0.1.5"
Bump chrono dependency to fix panic (#6317)
2022-08-13 20:21:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump iana-time-zone from 0.1.44 to 0.1.47 (#6448) Bumps [iana-time-zone](https://github.com/strawlab/iana-time-zone) from 0.1.44 to 0.1.47. - [Release notes](https://github.com/strawlab/iana-time-zone/releases) - [Changelog](https://github.com/strawlab/iana-time-zone/blob/main/CHANGELOG.md) - [Commits](https://github.com/strawlab/iana-time-zone/compare/0.1.44...v0.1.47) --- updated-dependencies: - dependency-name: iana-time-zone dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-08-31 13:19:20 +02:00
checksum = "819e7219dbd41043ac279b19830f2efc897156490d7fd6ea916720117ee66311"
Bump chrono dependency to fix panic (#6317)
2022-08-13 20:21:28 +02:00
dependencies = [
"libc",
]
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 20:39:54 +01:00
[[package]]
name = "anes"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4b46cbb362ab8752921c97e041f5e366ee6297bd428a31275b9fcf1e380f7299"
nu-table: Bump tabled to 0.12.1 (#9341) close #9335 I am not sure whether the fix was better to be delived as a minor bump but it is what is is. Could you @fdncred test it somehow? I did it by checking out back the the original commit before the PR refered in the issue. --------- Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-06-12 00:33:54 +02:00
[[package]]
name = "ansi-str"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1cf4578926a981ab0ca955dc023541d19de37112bc24c1a197bd806d3d86ad1d"
dependencies = [
"ansitok",
]
Consider space for single `...` column not enough space (#6080) * nu-table: Refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: consider space for single `...` column not enough space Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-19 19:35:25 +02:00
[[package]]
name = "ansitok"
nu-table: Check perf improvements (#6710) * nu-table: Checkout to test vte parsing Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled version Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-20 14:52:15 +02:00
version = "0.2.0"
Consider space for single `...` column not enough space (#6080) * nu-table: Refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: consider space for single `...` column not enough space Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-19 19:35:25 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-table: Check perf improvements (#6710) * nu-table: Checkout to test vte parsing Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled version Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-20 14:52:15 +02:00
checksum = "220044e6a1bb31ddee4e3db724d29767f352de47445a6cd75e1a173142136c83"
Consider space for single `...` column not enough space (#6080) * nu-table: Refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: consider space for single `...` column not enough space Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-19 19:35:25 +02:00
dependencies = [
Remove `math eval` command (#7284) Reasoning: Most missing math commands are implemented with #7258. The `meval` crate itself declares that it doesn't strive to stringent standards (https://docs.rs/meval/latest/meval/#related-projects). For example no particular special casing or transformations are performed to ensure numerical stability. It uses the same rust `std` library functions we use or have access to (and `f64`). While the command call syntax in nushell may be a bit more verbose, having a single source of truth and common commands is beneficial. Furthermore the `math` commands can themselves implement broadcasting over lists (or table columns). Closes #7073 Removed dependencies: - `meval` - `nom 1.2.4` (duplicate) User-Facing Changes: Scripts using `math eval` will break. We remove a further `eval` like behavior to get results through runtime evaluation (albeit limited in scope) Tests: - Updated tests that internally used `math eval`. - Removed one test that primarily used `math eval` to obtain a result from `str join`
2023-01-04 23:50:18 +01:00
"nom",
update `strip-ansi-escapes` to use new api (#9958) # Description This PR updates `strip-ansi-escapes` to support their new API. This also updates nushell to the latest reedline after the same fix https://github.com/nushell/reedline/pull/617 closes #9957 # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `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-08-08 22:20:37 +02:00
"vte 0.10.1",
Consider space for single `...` column not enough space (#6080) * nu-table: Refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: consider space for single `...` column not enough space Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-19 19:35:25 +02:00
]
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
[[package]]
name = "anstream"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "0.6.5"
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "d664a92ecae85fd0a7392615844904654d1d5f5514837f471ddef4a057aba1b6"
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
dependencies = [
"anstyle",
"anstyle-parse",
"anstyle-query",
"anstyle-wincon",
"colorchoice",
"utf8parse",
]
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
[[package]]
name = "anstyle"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.0.4"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "7079075b41f533b8c61d2a4d073c4676e1f8b249ff94a393b0595db304e0dd87"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
[[package]]
name = "anstyle-parse"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.2.3"
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "c75ac65da39e5fe5ab759307499ddad880d724eed2f6ce5b5e8a26f4f387928c"
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
dependencies = [
"utf8parse",
]
[[package]]
name = "anstyle-query"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "1.0.2"
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "e28923312444cdd728e4738b3f9c9cac739500909bb3d3c94b43551b16517648"
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
dependencies = [
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"windows-sys 0.52.0",
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
]
[[package]]
name = "anstyle-wincon"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "3.0.2"
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "1cd54b81ec8d6180e24654d0b371ad22fc3dd083b6ff8ba325b72e00c87660a7"
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
dependencies = [
"anstyle",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"windows-sys 0.52.0",
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
]
Start to move to polars 0.29 (#9145) This does part of the work of porting to polars 0.29. However, I am not familiar enough with this part of the codebase to finish it. Things to be done: - We match two times over `polars::Expr` but `Expr::Cache` isn't handled. I don't know what should be done here - `ArgExpr:::List` was renamed to `ArgExpr::Implode`. Does that mean that `dfr list` should be renamed to `dfr implode`? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-05-12 14:44:35 +02:00
[[package]]
name = "argminmax"
version = "0.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "202108b46429b765ef483f8a24d5c46f48c14acfdacc086dd4ab6dddf6bcdbd2"
dependencies = [
"num-traits",
]
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
[[package]]
name = "array-init-cursor"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bf7d0a018de4f6aa429b9d33d69edf69072b1c5b1cb8d3e4a5f7ef898fc3eb76"
Merge master
2019-11-16 18:17:05 +01:00
[[package]]
name = "arrayvec"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
version = "0.5.2"
Merge master
2019-11-16 18:17:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
checksum = "23b62fc65de8e4e7f52534fb52b0f3ed04746ae267519eef2a83941e8085068b"
Merge master
2019-11-16 18:17:05 +01:00
new `glob` command (#5087)
2022-04-04 22:45:01 +02:00
[[package]]
name = "arrayvec"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.7.4"
new `glob` command (#5087)
2022-04-04 22:45:01 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "96d30a06541fbafbc7f82ed10c06164cfbd2c401138f6addd8404629c4b16711"
new `glob` command (#5087)
2022-04-04 22:45:01 +02:00
Bump to 0.40 (#4129)
2021-11-16 09:53:03 +01:00
[[package]]
name = "arrow-format"
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 16:27:37 +01:00
version = "0.8.1"
Bump to 0.40 (#4129)
2021-11-16 09:53:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 16:27:37 +01:00
checksum = "07884ea216994cdc32a2d5f8274a8bee979cfe90274b83f86f440866ee3132c7"
Bump to 0.40 (#4129)
2021-11-16 09:53:03 +01:00
dependencies = [
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
"planus",
"serde",
Bump to 0.40 (#4129)
2021-11-16 09:53:03 +01:00
]
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
[[package]]
name = "assert-json-diff"
version = "2.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "47e4f2b81832e72834d7518d8487a0396a28cc408186a2e8854c0f98011faf12"
dependencies = [
"serde",
"serde_json",
]
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
[[package]]
name = "assert_cmd"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "2.0.12"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "88903cb14723e4d4003335bb7f8a14f27691649105346a0f0957466c096adfe6"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
dependencies = [
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
"anstyle",
Bump wax from 0.5.0 to 0.6.0 (#10574)
2023-10-09 14:31:50 +02:00
"bstr",
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
"doc-comment",
"predicates",
"predicates-core",
"predicates-tree",
"wait-timeout",
]
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
[[package]]
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
name = "async-stream"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
version = "0.3.5"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
checksum = "cd56dd203fef61ac097dd65721a419ddccb106b2d2b70ba60a6b529f03961a51"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
dependencies = [
"async-stream-impl",
"futures-core",
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
"pin-project-lite",
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
]
[[package]]
name = "async-stream-impl"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
version = "0.3.5"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
checksum = "16e62a023e7c117e27523144c5d2459f4397fcc3cab0085af8e2224f643a0193"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
dependencies = [
"proc-macro2",
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
]
Move run to be async (#1913)
2020-05-29 10:22:52 +02:00
[[package]]
name = "async-trait"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.1.74"
Move run to be async (#1913)
2020-05-29 10:22:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "a66537f1bb974b254c98ed142ff995236e81b9d0fe4db0575f46612cb15eb0f9"
Move run to be async (#1913)
2020-05-29 10:22:52 +02:00
dependencies = [
"proc-macro2",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
Move run to be async (#1913)
2020-05-29 10:22:52 +02:00
]
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
[[package]]
name = "atoi"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f28d99ec8bfea296261ca1af174f24225171fea9664ba9003cbebee704810528"
dependencies = [
"num-traits",
]
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "atoi_simd"
version = "0.15.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ccfc14f5c3e34de57539a7ba9c18ecde3d9bbde48d232ea1da3e468adb307fd0"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
[[package]]
name = "atomic-polyfill"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "1.0.3"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "8cf2bce30dfe09ef0bfaef228b9d414faaf7e563035494d7fe092dba54b300f4"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
dependencies = [
"critical-section",
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
[[package]]
name = "autocfg"
merge main
2022-02-08 14:28:21 +01:00
version = "1.1.0"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
merge main
2022-02-08 14:28:21 +01:00
checksum = "d468802bab17cbc0cc575e9b053f41e72aa36bfa6b7f55e3529ffa43161b97fa"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
Expose polars avro support (#10019) # Description Exposes polars avro support via dfr open and dfr to-avro --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-08-16 03:31:49 +02:00
[[package]]
name = "avro-schema"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b5281855b39aba9684d2f47bf96983fbfd8f1725f12fabb0513a8ab879647bbd"
dependencies = [
"crc",
"fallible-streaming-iterator",
"libflate",
"serde",
"serde_json",
"snap",
]
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
[[package]]
name = "backtrace"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.3.69"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "2089b7e3f35b9dd2d0ed921ead4f6d318c27680d4a5bd167b3ee120edb105837"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
dependencies = [
"addr2line",
"cc",
"cfg-if",
"libc",
"miniz_oxide",
"object",
"rustc-demangle",
]
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "base64"
version = "0.13.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9e1b586273c5702936fe7b7d6896644d8be71e6314cfe09d3167c95f712589e8"
update base64 implementation to newer crate (#7739) # Description This PR updates the base64 crate, which has changed significantly, so all the base64 implementations had to be changed too. Tests pass. I hope that's enough. # User-Facing Changes None, except added a new character encoding imap-mutf7 as mutf7. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 14:16:14 +01:00
[[package]]
name = "base64"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.21.5"
update base64 implementation to newer crate (#7739) # Description This PR updates the base64 crate, which has changed significantly, so all the base64 implementations had to be changed too. Tests pass. I hope that's enough. # User-Facing Changes None, except added a new character encoding imap-mutf7 as mutf7. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 14:16:14 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "35636a1494ede3b646cc98f74f8e62c773a38a659ebc777a2cf26b9b74171df9"
update base64 implementation to newer crate (#7739) # Description This PR updates the base64 crate, which has changed significantly, so all the base64 implementations had to be changed too. Tests pass. I hope that's enough. # User-Facing Changes None, except added a new character encoding imap-mutf7 as mutf7. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 14:16:14 +01:00
Add CustomValue support to plugins (#6070) * Skeleton implementation Lots and lots of TODOs * Bootstrap simple CustomValue plugin support test * Create nu_plugin_custom_value * Skeleton for nu_plugin_custom_values * Return a custom value from plugin * Encode CustomValues from plugin calls as PluginResponse::PluginData * Add new PluginCall variant CollapseCustomValue * Handle CollapseCustomValue plugin calls * Add CallInput::Data variant to CallInfo inputs * Handle CallInfo with CallInput::Data plugin calls * Send CallInput::Data if Value is PluginCustomValue from plugin calls * Remove unnecessary boxing of plugins CallInfo * Add fields needed to collapse PluginCustomValue to it * Document PluginCustomValue and its purpose * Impl collapsing using plugin calls in PluginCustomValue::to_base_value * Implement proper typetag based deserialization for CoolCustomValue * Test demonstrating that passing back a custom value to plugin works * Added a failing test for describing plugin CustomValues * Support describe for PluginCustomValues - Add name to PluginResponse::PluginData - Also turn it into a struct for clarity - Add name to PluginCustomValue - Return name field from PluginCustomValue * Demonstrate that plugins can create and handle multiple CustomValues * Add bincode to nu-plugin dependencies This is for demonstration purposes, any schemaless binary seralization format will work. I picked bincode since it's the most popular for Rust but there are defintely better options out there for this usecase * serde_json::Value -> Vec<u8> * Update capnp schema for new CallInfo.input field * Move call_input capnp serialization and deserialization into new file * Deserialize Value's span from Value itself instead of passing call.head I am not sure if this was correct and I am breaking it or if it was a bug, I don't fully understand how nu creates and uses Spans. What should reuse spans and what should recreate new ones? But yeah it felt weird that the Value's Span was being ignored since in the json serializer just uses the Value's Span * Add call_info value round trip test * Add capnp CallInput::Data serialization and deserialization support * Add CallInfo::CollapseCustomValue to capnp schema * Add capnp PluginCall::CollapseCustomValue serialization and deserialization support * Add PluginResponse::PluginData to capnp schema * Add capnp PluginResponse::PluginData serialization and deserialization support * Switch plugins::custom_values tests to capnp Both json and capnp would work now! Sadly I can't choose both at the same time :( * Add missing JsonSerializer round trip tests * Handle plugin returning PluginData as a response to CollapseCustomValue * Refactor plugin calling into a reusable function Many less levels of indentation now! * Export PluginData from nu_plugin So plugins can create their very own serve_plugin with whatever CustomValue behavior they may desire * Error if CustomValue cannot be handled by Plugin
2022-07-25 18:32:56 +02:00
[[package]]
name = "bincode"
version = "1.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b1f45e9417d87227c7a56d22e471c6206462cba514c7590c09aff4cf6d1ddcad"
dependencies = [
"serde",
]
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
[[package]]
name = "bindgen"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.68.1"
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "726e4313eb6ec35d2730258ad4e15b547ee75d6afaa1361a922e78e59b7d8078"
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
dependencies = [
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"bitflags 2.4.1",
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
"cexpr",
"clang-sys",
"lazy_static",
"lazycell",
"peeking_take_while",
"proc-macro2",
"quote",
"regex",
"rustc-hash",
"shlex",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
]
replace the regex crate with the fancy-regex crate (#6227)
2022-08-04 21:51:02 +02:00
[[package]]
name = "bit-set"
version = "0.5.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0700ddab506f33b20a03b13996eccd309a48e5ff77d0d95926aa0210fb4e95f1"
dependencies = [
"bit-vec",
]
[[package]]
name = "bit-vec"
version = "0.6.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "349f9b6a179ed607305526ca489b34ad0a41aed5f7980fa90eb03160b69598fb"
Bat
2019-05-18 03:24:13 +02:00
[[package]]
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
name = "bitflags"
version = "1.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bef38d45163c2f1dde094a7dfd33ccf595c92905c8f8f4fdc18d06fb1037718a"
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
[[package]]
name = "bitflags"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "2.4.1"
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "327762f6e5a765692301e5bb513e0d9fef63be86bbc14528052b1cd3e6f03e07"
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
dependencies = [
"serde",
]
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
Bump some deps (#503)
2021-12-16 10:40:05 +01:00
[[package]]
Autoenv rewrite, security and scripting (#2083) * Add args in .nurc file to environment * Working dummy version * Add add_nurc to sync_env command * Parse .nurc file * Delete env vars after leaving directory * Removing vals not working, strangely * Refactoring, add comment * Debugging * Debug by logging to file * Add and remove env var behavior appears correct However, it does not use existing code that well. * Move work to cli.rs * Parse config directories * I am in a state of distress * Rename .nurc to .nu * Some notes for me * Refactoring * Removing vars works, but not done in a very nice fashion * Refactor env_vars_to_delete * Refactor env_vars_to_add() * Move directory environment code to separate file * Refactor from_config * Restore env values * Working? * Working? * Update comments and change var name * Formatting * Remove vars after leaving dir * Remove notes I made * Rename config function * Clippy * Cleanup and handle errors * cargo fmt * Better error messages, remove last (?) unwrap * FORMAT PLZ * Rename whitelisted_directories to allowed_directories * Add comment to clarify how overwritten values are restored. * Change list of allowed dirs to indexmap * Rewrite starting * rewrite everything * Overwritten env values tracks an indexmap instead of vector * Refactor restore function * Untrack removed vars properly * Performance concerns * Performance concerns * Error handling * Clippy * Add type aliases for String and OsString * Deletion almost works * Working? * Error handling and refactoring * nicer errors * Add TODO file * Move outside of loop * Error handling * Reworking adding of vars * Reworking adding of vars * Ready for testing * Refactoring * Restore overwritten vals code * todo.org * Remove overwritten values tracking, as it is not needed * Cleanup, stop tracking overwritten values as nu takes care of it * Init autoenv command * Initialize autoenv and autoenv trust * autoenv trust toml * toml * Use serde for autoenv * Optional directory arg * Add autoenv untrust command * ... actually add autoenv untrust this time * OsString and paths * Revert "OsString and paths" This reverts commit e6eedf882498c1365ecfc899e5ec11bd83cb055c. * Fix path * Fix path * Autoenv trust and untrust * Start using autoenv * Check hashes * Use trust functionality when setting vars * Remove unused code * Clippy * Nicer errors for autoenv commands * Non-working errors * Update error description * Satisfy fmt * Errors * Errors print, but not nicely * Nicer errors * fmt * Delete accidentally added todo.org file * Rename direnv to autoenv * Use ShellError instead of Error * Change tests to pass, danger zone? * Clippy and errors * Clippy... again * Replace match with or_else * Use sha2 crate for hashing * parsing and error msg * Refactoring * Only apply vars once * if parent dir * Delete vars * Rework exit code * Adding works * restore * Fix possibility of infinite loop * Refactoring * Non-working * Revert "Non-working" This reverts commit e231b85570bcb3fc838f950e9f5004c6a7c5a2ac. * Revert "Revert "Non-working"" This reverts commit 804092e46a752266576b044401cc97c317e41f21. * Autoenv trust works without restart * Cargo fix * Script vars * Serde * Serde errors * Entry and exitscripts * Clippy * Support windows and handle errors * Formatting * Fix infinite loop on windows * Debugging windows loop * More windows infinite loop debugging * Windows loop debugging #3 * windows loop #4 * Don't return err * Cleanup unused code * Infinite loop debug * Loop debugging * Check if infinite loop is vars_to_add * env_vars_to_add does not terminate, skip loop as test * Hypothesis: std::env::current_dir() is messing with something * Hypothesis: std::env::current_dir() is messing with something * plz * make clippy happy * debugging in env_vars_to_add * Debbuging env_vars_to_add #2 * clippy * clippy.. * Fool clippy * Fix another infinite loop * Binary search for error location x) * Binary search #3 * fmt * Binary search #4 * more searching... * closing in... maybe * PLZ * Cleanup * Restore commented out functionality * Handle case when user gives the directory "." * fmt * Use fs::canonicalize for paths * Create optional script section * fmt * Add exitscripts even if no entryscripts are defined * All sections in .nu-env are now optional * Re-read config file each directory change * Hot reload after autoenv untrust, don't run exitscripts if untrusted * Debugging * Fix issue with recursive adding of vars * Thank you for finding my issues Mr. Azure * use std::env
2020-07-05 19:34:00 +02:00
name = "block-buffer"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "0.10.4"
Port `hash`, `hash md5` and `hash sha256` commands (#464) `hash` by itself is only printing the help message. The other two are simply using the same generic implementation.
2021-12-11 00:14:28 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "3078c7629b62d3f0439517fa394996acacc5cbc91c5a20d8c658e77abd503a71"
Port `hash`, `hash md5` and `hash sha256` commands (#464) `hash` by itself is only printing the help message. The other two are simply using the same generic implementation.
2021-12-11 00:14:28 +01:00
dependencies = [
Consider space for single `...` column not enough space (#6080) * nu-table: Refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: consider space for single `...` column not enough space Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-19 19:35:25 +02:00
"generic-array",
Bump some of our dependencies (#1809)
2020-05-17 00:34:10 +02:00
]
A new subcommand to str, str-expand. (#9290) # 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. --> Description can be found [here: https://github.com/nushell/nushell/discussions/9277#discussioncomment-5997793](https://github.com/nushell/nushell/discussions/9277#discussioncomment-5997793) # User-Facing Changes Again, examples can be found in the discussion #9277 <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting I've written tests that cover the changes I've made. <!-- 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-06-28 19:57:44 +02:00
[[package]]
name = "bracoxide"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.1.3"
A new subcommand to str, str-expand. (#9290) # 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. --> Description can be found [here: https://github.com/nushell/nushell/discussions/9277#discussioncomment-5997793](https://github.com/nushell/nushell/discussions/9277#discussioncomment-5997793) # User-Facing Changes Again, examples can be found in the discussion #9277 <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting I've written tests that cover the changes I've made. <!-- 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-06-28 19:57:44 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "ada7f35ca622a86a4d6c27be2633fc6c243ecc834859628fcce0681d8e76e1c8"
A new subcommand to str, str-expand. (#9290) # 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. --> Description can be found [here: https://github.com/nushell/nushell/discussions/9277#discussioncomment-5997793](https://github.com/nushell/nushell/discussions/9277#discussioncomment-5997793) # User-Facing Changes Again, examples can be found in the discussion #9277 <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting I've written tests that cover the changes I've made. <!-- 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-06-28 19:57:44 +02:00
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
[[package]]
name = "brotli"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "3.4.0"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "516074a47ef4bce09577a3b379392300159ce5b1ba2e501ff1c819950066100f"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
dependencies = [
"alloc-no-stdlib",
"alloc-stdlib",
"brotli-decompressor",
]
[[package]]
name = "brotli-decompressor"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "2.5.1"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "4e2e4afe60d7dd600fdd3de8d0f08c2b7ec039712e3b6137ff98b7004e82de4f"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
dependencies = [
"alloc-no-stdlib",
"alloc-stdlib",
]
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
[[package]]
name = "bstr"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "1.8.0"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "542f33a8835a0884b006a0c3df3dadd99c0c3f296ed26c2fdc8028e01ad6230c"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
dependencies = [
"memchr",
Revert "Bump regex from 1.9.6 to 1.10.2" (#10818) Reverts nushell/nushell#10812 This goes back to a version of `regex` and its dependencies that is shared with a lot of our other dependencies. Before this we did not duplicate big dependencies of `regex` that affect binary size and compile time. As there is no known bug or security problem we suffer from, we can wait on receiving the performance improvements to `regex` with the rest of our `regex` dependents.
2023-10-23 16:11:32 +02:00
"regex-automata",
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
"serde",
]
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
[[package]]
name = "bumpalo"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "3.14.0"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "7f30e7476521f6f8af1a1c4c0b8cc94f0bee37d91763d0ca2665f299b6cd8aec"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
Internals cleanup and | select ...fields
2019-05-15 20:14:51 +02:00
[[package]]
name = "byte-unit"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
version = "4.0.19"
Internals cleanup and | select ...fields
2019-05-15 20:14:51 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
checksum = "da78b32057b8fdfc352504708feeba7216dcd65a2c9ab02978cbd288d1279b6c"
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
dependencies = [
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
"serde",
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
"utf8-width",
]
Internals cleanup and | select ...fields
2019-05-15 20:14:51 +02:00
Give tabled a try (#5969) * Drop in replacement from nu-table to tabled. Must act the same way as original nu-table. Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Fix some issues Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump ansi-str version Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update to latest Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix footer issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header style Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Use latest tabled/ansi-str * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy warnings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-06 21:57:40 +02:00
[[package]]
name = "bytecount"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.6.7"
Give tabled a try (#5969) * Drop in replacement from nu-table to tabled. Must act the same way as original nu-table. Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Fix some issues Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump ansi-str version Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update to latest Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix footer issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header style Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Use latest tabled/ansi-str * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy warnings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-06 21:57:40 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "e1e5f035d16fc623ae5f74981db80a439803888314e3a555fd6f04acd51a3205"
Give tabled a try (#5969) * Drop in replacement from nu-table to tabled. Must act the same way as original nu-table. Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Fix some issues Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump ansi-str version Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update to latest Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix footer issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header style Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Use latest tabled/ansi-str * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy warnings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-06 21:57:40 +02:00
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
[[package]]
name = "bytemuck"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.14.0"
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "374d28ec25809ee0e23827c2ab573d729e293f281dfe393500e7ad618baa61c6"
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
dependencies = [
"bytemuck_derive",
]
[[package]]
name = "bytemuck_derive"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.5.0"
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "965ab7eb5f8f97d2a083c799f3a1b994fc397b2fe2da5d1da1626ce15a39f2b1"
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
dependencies = [
"proc-macro2",
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
]
Replace `clipboard` with `arboard` (#2832)
2020-12-30 18:16:02 +01:00
[[package]]
objectshell initial commit
2019-05-10 18:59:12 +02:00
name = "byteorder"
Bump byteorder from 1.4.3 to 1.5.0 (#10657)
2023-10-10 14:57:36 +02:00
version = "1.5.0"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump byteorder from 1.4.3 to 1.5.0 (#10657)
2023-10-10 14:57:36 +02:00
checksum = "1fd0f2584146f6f2ef48085050886acf353beff7305ebd1ae69500e27c67f64b"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Pipe external to internal Each line is a string object
2019-05-24 20:48:33 +02:00
[[package]]
name = "bytes"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.5.0"
Port fetch (with fixes) (#660) * Port fetch to engine-q * Fix check for path as a string * Add a timeout flag and fix some span issues * Add a temporary fetch command that returns byte streams. Got rid of async stuff as we're using the blocking feature of tokio * More tweaks for the bytestream * Rewrite fetch using ByteStreams * buffer read on bytes directly Co-authored-by: Stefan Stanciulescu <contact@stefanstanciulescu.com>
2022-01-04 03:01:18 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "a2bd12c1caf447e69cd4528f47f94d203fd2582878ecb9e9465484c4148a8223"
Port fetch (with fixes) (#660) * Port fetch to engine-q * Fix check for path as a string * Add a timeout flag and fix some span issues * Add a temporary fetch command that returns byte streams. Got rid of async stuff as we're using the blocking feature of tokio * More tweaks for the bytestream * Rewrite fetch using ByteStreams * buffer read on bytes directly Co-authored-by: Stefan Stanciulescu <contact@stefanstanciulescu.com>
2022-01-04 03:01:18 +01:00
add ability to parse strings like "100kib" and "100 kib"
2021-10-12 22:22:12 +02:00
[[package]]
name = "bytesize"
Bump bytesize from 1.2.0 to 1.3.0 (#10306)
2023-09-11 11:55:21 +02:00
version = "1.3.0"
add ability to parse strings like "100kib" and "100 kib"
2021-10-12 22:22:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump bytesize from 1.2.0 to 1.3.0 (#10306)
2023-09-11 11:55:21 +02:00
checksum = "a3e368af43e418a04d52505cf3dbc23dda4e3407ae2fa99fd0e4f308ce546acc"
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
[[package]]
name = "calamine"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.22.1"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "fe0ba51a659bb6c8bffd6f7c1c5ffafcafa0c97e4769411d841c3cc5c154ab47"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"byteorder",
"codepage",
"encoding_rs",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"log",
Bump `calamine` and fix clippy (#10314) Upgrade calamine to 0.22 Reduces one potential dependency duplication Supersedes #10305 Includes fixes for clippy lints as API changed to return owned data.
2023-09-11 12:39:52 +02:00
"quick-xml",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"serde",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"zip",
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
]
[MVP][WIP] `less` like pager (#6984) Run it as `explore`. #### example ```nu ls | explore ``` Configuration points in `config.nu` file. ``` # A 'explore' utility config explore_config: { highlight: { bg: 'yellow', fg: 'black' } status_bar: { bg: '#C4C9C6', fg: '#1D1F21' } command_bar: { fg: '#C4C9C6' } split_line: '#404040' cursor: true # selected_column: 'blue' # selected_row: { fg: 'yellow', bg: '#C1C2A3' } # selected_cell: { fg: 'white', bg: '#777777' } # line_shift: false, # line_index: false, # line_head_top: false, # line_head_bottom: false, } ``` You can start without a pipeline and type `explore` and it'll give you a few tips. ![image](https://user-images.githubusercontent.com/343840/205088971-a8c0262f-f222-4641-b13a-027fbd4f5e1a.png) If you type `:help` you an see the help screen with some information on what tui keybindings are available. ![image](https://user-images.githubusercontent.com/343840/205089461-c4c54217-7ec4-4fa0-96c0-643d68dc0062.png) From the `:help` screen you can now hit `i` and that puts you in `cursor` aka `inspection` mode and you can move the cursor left right up down and it you put it on an area such as `[table 5 rows]` and hit the enter key, you'll see something like this, which shows all the `:` commands. If you hit `esc` it will take you to the previous screen. ![image](https://user-images.githubusercontent.com/343840/205090155-3558a14b-87b7-4072-8dfb-dc8cc2ef4943.png) If you then type `:try` you'll get this type of window where you can type in the top portion and see results in the bottom. ![image](https://user-images.githubusercontent.com/343840/205089185-3c065551-0792-43d6-a13c-a52762856209.png) The `:nu` command is interesting because you can type pipelines like `:nu ls | sort-by type size` or another pipeline of your choosing such as `:nu sys` and that will show the table that looks like this, which we're calling "table mode". ![image](https://user-images.githubusercontent.com/343840/205090809-e686ff0f-6d0b-4347-8ed0-8c59adfbd741.png) If you hit the `t` key it will now transpose the view to look like this. ![image](https://user-images.githubusercontent.com/343840/205090948-a834d7f2-1713-4dfe-92fe-5432f287df3d.png) In table mode or transposed table mode you can use the `i` key to inspect any collapsed field like `{record 8 fields}`, `[table 16 rows]`, `[list x]`, etc. One of the original benefits was that when you're in a view that has a lot of columns, `explore` gives you the ability to scroll left, right, up, and down. `explore` is also smart enough to know when you're in table mode versus preview mode. If you do `open Cargo.toml | explore` you get this. ![image](https://user-images.githubusercontent.com/343840/205091822-cac79130-3a52-4ca8-9210-eba5be30ed58.png) If you type `open --raw Cargo.toml | explore` you get this where you can scroll left, right, up, down. This is called preview mode. ![image](https://user-images.githubusercontent.com/343840/205091990-69455191-ab78-4fea-a961-feafafc16d70.png) When you're in table mode, you can also type `:preview`. So, with `open --raw Cargo.toml | explore`, if you type `:preview`, it will look like this. ![image](https://user-images.githubusercontent.com/343840/205092569-436aa55a-0474-48d5-ab71-baddb1f43027.png) Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-12-01 16:32:10 +01:00
[[package]]
name = "cassowary"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "df8670b8c7b9dae1793364eafadf7239c40d669904660c5960d74cfd80b46a53"
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
[[package]]
name = "cast"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "37b2a672a2cb129a2e41c10b1224bb368f9f37a2b16b612598138befd7b37eb5"
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "cc"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.0.83"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "f1174fb0b6ec23863f8b971027804a42614e347eafb0a95bf0b12cdae21fc4d0"
Add basic 'did you mean' support
2019-09-13 05:44:21 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"jobserver",
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
"libc",
Add basic 'did you mean' support
2019-09-13 05:44:21 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
[[package]]
name = "cexpr"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6fac387a98bb7c37292057cffc56d62ecb629900026402633ae9160df93a8766"
dependencies = [
Remove `math eval` command (#7284) Reasoning: Most missing math commands are implemented with #7258. The `meval` crate itself declares that it doesn't strive to stringent standards (https://docs.rs/meval/latest/meval/#related-projects). For example no particular special casing or transformations are performed to ensure numerical stability. It uses the same rust `std` library functions we use or have access to (and `f64`). While the command call syntax in nushell may be a bit more verbose, having a single source of truth and common commands is beneficial. Furthermore the `math` commands can themselves implement broadcasting over lists (or table columns). Closes #7073 Removed dependencies: - `meval` - `nom 1.2.4` (duplicate) User-Facing Changes: Scripts using `math eval` will break. We remove a further `eval` like behavior to get results through runtime evaluation (albeit limited in scope) Tests: - Updated tests that internally used `math eval`. - Removed one test that primarily used `math eval` to obtain a result from `str join`
2023-01-04 23:50:18 +01:00
"nom",
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "cfg-if"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
Add encoding auto-detection for `decode` (#10030) # Description Allow `decode` command to guess the encoding of input if no encoding name is given. # User-Facing Changes * `decode` now has an optional parameter instead of required one. User can just run `decode` to let the command automatically detect encoding and convert it to utf-8. <img width="575" alt="Example" src="https://github.com/nushell/nushell/assets/1991933/03a0ba11-910e-4db9-89aa-79cfec06893f"> * Based on the detect result, user may have to give a encoding name <img width="572" alt="Error Sample1" src="https://github.com/nushell/nushell/assets/1991933/f21fda85-1f04-4cb3-9feb-cb9fb7dcee07"> or get informed that the input is not supported by `decode` <img width="568" alt="Error Sample2" src="https://github.com/nushell/nushell/assets/1991933/dd3cc4c0-f119-493e-8609-d07594fc055a"> # Tests + Formatting * `cargo fmt --all -- --check` : OK * `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect -A clippy::result_large_err`: OK * `cargo test --workspace` : OK * `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"`: OK # After Submitting [Command document](https://www.nushell.sh/commands/docs/decode.html) is auto-generated and requires no action. --------- Co-authored-by: Horasal <horsal@horsal.dev>
2023-08-25 02:21:17 +02:00
[[package]]
name = "chardetng"
version = "0.1.17"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "14b8f0b65b7b08ae3c8187e8d77174de20cb6777864c6b832d8ad365999cf1ea"
dependencies = [
"cfg-if",
"encoding_rs",
"memchr",
]
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "charset"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "18e9079d1a12a2cc2bffb5db039c43661836ead4082120d5844f02555aca2d46"
dependencies = [
"base64 0.13.1",
"encoding_rs",
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "chrono"
fix some new chrono warnings (#10384) # Description This PR cleans up some warnings on the latest chrono dependency. # 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-09-15 22:46:25 +02:00
version = "0.4.31"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
fix some new chrono warnings (#10384) # Description This PR cleans up some warnings on the latest chrono dependency. # 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-09-15 22:46:25 +02:00
checksum = "7f2c685bad3eb3d45a01354cedb7d5faa66194d1d58ba6e267a8de788f79db38"
objectshell initial commit
2019-05-10 18:59:12 +02:00
dependencies = [
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"android-tzdata",
Bump chrono dependency to fix panic (#6317)
2022-08-13 20:21:28 +02:00
"iana-time-zone",
allow parsing of human readable datetimes (#11051) # Description This PR adds the ability to parse human readable datetime strings as part of the `into datetime` command. I added a new `-n`/`--list-human` parameter that produces this list to give the user an idea of what is supported. ```nushell ❯ into datetime --list-human ╭#─┬parseable human datetime examples┬───result───╮ │0 │Today 18:30 │in 8 hours │ │1 │2022-11-07 13:25:30 │a year ago │ │2 │15:20 Friday │in 3 days │ │3 │This Friday 17:00 │in 3 days │ │4 │13:25, Next Tuesday │in a week │ │5 │Last Friday at 19:45 │3 days ago │ │6 │In 3 days │in 2 days │ │7 │In 2 hours │in 2 hours │ │8 │10 hours and 5 minutes ago │10 hours ago│ │9 │1 years ago │a year ago │ │10│A year ago │a year ago │ │11│A month ago │a month ago │ │12│A week ago │a week ago │ │13│A day ago │a day ago │ │14│An hour ago │an hour ago │ │15│A minute ago │a minute ago│ │16│A second ago │now │ │17│Now │now │ ╰#─┴parseable human datetime examples┴───result───╯ ``` Or with `$env.config.datetime_format.table` set. ```nushell ❯ into datetime --list-human ╭#─┬parseable human datetime examples┬──────result───────╮ │0 │Today 18:30 │11/14/23 06:30:00PM│ │1 │2022-11-07 13:25:30 │11/07/22 01:25:30PM│ │2 │15:20 Friday │11/17/23 03:20:00PM│ │3 │This Friday 17:00 │11/17/23 05:00:00PM│ │4 │13:25, Next Tuesday │11/21/23 01:25:00PM│ │5 │Last Friday at 19:45 │11/10/23 07:45:00PM│ │6 │In 3 days │11/17/23 10:12:54AM│ │7 │In 2 hours │11/14/23 12:12:54PM│ │8 │10 hours and 5 minutes ago │11/14/23 12:07:54AM│ │9 │1 years ago │11/13/22 10:12:54AM│ │10│A year ago │11/13/22 10:12:54AM│ │11│A month ago │10/15/23 11:12:54AM│ │12│A week ago │11/07/23 10:12:54AM│ │13│A day ago │11/13/23 10:12:54AM│ │14│An hour ago │11/14/23 09:12:54AM│ │15│A minute ago │11/14/23 10:11:54AM│ │16│A second ago │11/14/23 10:12:53AM│ │17│Now │11/14/23 10:12:54AM│ ╰#─┴parseable human datetime examples┴──────result───────╯ ``` # 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-11-16 00:43:37 +01:00
"js-sys",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"num-traits",
make `date format` supports locale (#6306) * add --locale flag to make output support locale * implement again based on nu-utils get_system_locale_string * add comment
2022-08-14 15:07:04 +02:00
"pure-rust-locales",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"serde",
allow parsing of human readable datetimes (#11051) # Description This PR adds the ability to parse human readable datetime strings as part of the `into datetime` command. I added a new `-n`/`--list-human` parameter that produces this list to give the user an idea of what is supported. ```nushell ❯ into datetime --list-human ╭#─┬parseable human datetime examples┬───result───╮ │0 │Today 18:30 │in 8 hours │ │1 │2022-11-07 13:25:30 │a year ago │ │2 │15:20 Friday │in 3 days │ │3 │This Friday 17:00 │in 3 days │ │4 │13:25, Next Tuesday │in a week │ │5 │Last Friday at 19:45 │3 days ago │ │6 │In 3 days │in 2 days │ │7 │In 2 hours │in 2 hours │ │8 │10 hours and 5 minutes ago │10 hours ago│ │9 │1 years ago │a year ago │ │10│A year ago │a year ago │ │11│A month ago │a month ago │ │12│A week ago │a week ago │ │13│A day ago │a day ago │ │14│An hour ago │an hour ago │ │15│A minute ago │a minute ago│ │16│A second ago │now │ │17│Now │now │ ╰#─┴parseable human datetime examples┴───result───╯ ``` Or with `$env.config.datetime_format.table` set. ```nushell ❯ into datetime --list-human ╭#─┬parseable human datetime examples┬──────result───────╮ │0 │Today 18:30 │11/14/23 06:30:00PM│ │1 │2022-11-07 13:25:30 │11/07/22 01:25:30PM│ │2 │15:20 Friday │11/17/23 03:20:00PM│ │3 │This Friday 17:00 │11/17/23 05:00:00PM│ │4 │13:25, Next Tuesday │11/21/23 01:25:00PM│ │5 │Last Friday at 19:45 │11/10/23 07:45:00PM│ │6 │In 3 days │11/17/23 10:12:54AM│ │7 │In 2 hours │11/14/23 12:12:54PM│ │8 │10 hours and 5 minutes ago │11/14/23 12:07:54AM│ │9 │1 years ago │11/13/22 10:12:54AM│ │10│A year ago │11/13/22 10:12:54AM│ │11│A month ago │10/15/23 11:12:54AM│ │12│A week ago │11/07/23 10:12:54AM│ │13│A day ago │11/13/23 10:12:54AM│ │14│An hour ago │11/14/23 09:12:54AM│ │15│A minute ago │11/14/23 10:11:54AM│ │16│A second ago │11/14/23 10:12:53AM│ │17│Now │11/14/23 10:12:54AM│ ╰#─┴parseable human datetime examples┴──────result───────╯ ``` # 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-11-16 00:43:37 +01:00
"wasm-bindgen",
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
"windows-targets 0.48.5",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
use chrono_humanize for datetime formatting (#3834) * use chrono_humanize for datetime formatting * fix tests
2021-07-25 10:38:45 +02:00
[[package]]
name = "chrono-humanize"
Don't use `oldtime` feature of chrono (#9577) <!-- 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 `chrono` crate enables `oldtime` feature by default, which has a vulnerability (https://rustsec.org/advisories/RUSTSEC-2020-0071). This PR tries to remove `time` v0.1.45 completely from nu and add an audit CI to check for security vulnerabilities. :hand: Wait for the following PRs: - [x] https://github.com/nushell/reedline/pull/599 - [x] https://github.com/bspeice/dtparse/pull/44 - [x] https://github.com/Byron/trash-rs/pull/75 - [x] https://gitlab.com/imp/chrono-humanize-rs/-/merge_requests/15 # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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. --> --------- Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-25 10:54:01 +02:00
version = "0.2.3"
use chrono_humanize for datetime formatting (#3834) * use chrono_humanize for datetime formatting * fix tests
2021-07-25 10:38:45 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Don't use `oldtime` feature of chrono (#9577) <!-- 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 `chrono` crate enables `oldtime` feature by default, which has a vulnerability (https://rustsec.org/advisories/RUSTSEC-2020-0071). This PR tries to remove `time` v0.1.45 completely from nu and add an audit CI to check for security vulnerabilities. :hand: Wait for the following PRs: - [x] https://github.com/nushell/reedline/pull/599 - [x] https://github.com/bspeice/dtparse/pull/44 - [x] https://github.com/Byron/trash-rs/pull/75 - [x] https://gitlab.com/imp/chrono-humanize-rs/-/merge_requests/15 # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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. --> --------- Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-25 10:54:01 +02:00
checksum = "799627e6b4d27827a814e837b9d8a504832086081806d45b1afa34dc982b023b"
use chrono_humanize for datetime formatting (#3834) * use chrono_humanize for datetime formatting * fix tests
2021-07-25 10:38:45 +02:00
dependencies = [
"chrono",
]
removed rustyline config duplication (#2306) * removed rustyline config duplication set other rustyline defaults if line_editor section doesn't exist updated keyseq_timeout to -1 if emacs mode is chosen * change checking rustyline config to if lets * removed some unneccessary code
2020-08-05 23:34:28 +02:00
[[package]]
name = "chrono-tz"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.8.4"
Add a simple scope variable
2021-11-02 04:08:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "e23185c0e21df6ed832a12e2bda87c7d1def6842881fb634a8511ced741b0d76"
Add a simple scope variable
2021-11-02 04:08:05 +01:00
dependencies = [
"chrono",
"chrono-tz-build",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"phf 0.11.2",
Add a simple scope variable
2021-11-02 04:08:05 +01:00
]
[[package]]
name = "chrono-tz-build"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.2.1"
Add a simple scope variable
2021-11-02 04:08:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "433e39f13c9a060046954e0592a8d0a4bcb1040125cbf91cb8ee58964cfb350f"
Add a simple scope variable
2021-11-02 04:08:05 +01:00
dependencies = [
"parse-zoneinfo",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"phf 0.11.2",
"phf_codegen 0.11.2",
Fix VCS markers not showing up in textview (#3530) Changes: * Bug fix - bat adds markers only when a file path is passed and it can use git2 on it. It doesn't add markers when bytes are passed. Hence, the code is adjusted accordingly. The sideeffect is files being opened multiple times and its content being unnecessarily loaded in memory. * Refactoring of the crate - Config is extracted to its struct file. Repetitive blocks of code are dried and nested conditionals are flattened.
2021-06-03 08:25:28 +02:00
]
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "chumsky"
version = "0.9.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8eebd66744a15ded14960ab4ccdbfb51ad3b81f51f3f04a80adac98c985396c9"
dependencies = [
"hashbrown 0.14.3",
"stacker",
]
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 20:39:54 +01:00
[[package]]
name = "ciborium"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
version = "0.2.1"
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 20:39:54 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
checksum = "effd91f6c78e5a4ace8a5d3c0b6bfaec9e2baaef55f3efc00e45fb2e477ee926"
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 20:39:54 +01:00
dependencies = [
"ciborium-io",
"ciborium-ll",
"serde",
]
[[package]]
name = "ciborium-io"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
version = "0.2.1"
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 20:39:54 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
checksum = "cdf919175532b369853f5d5e20b26b43112613fd6fe7aee757e35f7a44642656"
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 20:39:54 +01:00
[[package]]
name = "ciborium-ll"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
version = "0.2.1"
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 20:39:54 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
checksum = "defaa24ecc093c77630e6c15e17c51f5e187bf35ee514f4e2d67baaa96dae22b"
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 20:39:54 +01:00
dependencies = [
"ciborium-io",
"half",
]
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
[[package]]
name = "clang-sys"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
version = "1.6.1"
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
checksum = "c688fc74432808e3eb684cae8830a86be1d66a2bd58e1f248ed0960a590baf6f"
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
dependencies = [
"glob",
"libc",
"libloading",
]
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
[[package]]
name = "clap"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "4.4.11"
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "bfaff671f6b22ca62406885ece523383b9b64022e341e53e009a62ebc47a45f2"
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
dependencies = [
Bump criterion from 0.4.0 to 0.5.1 (#9361)
2023-06-07 15:29:54 +02:00
"clap_builder",
]
[[package]]
name = "clap_builder"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "4.4.11"
Bump criterion from 0.4.0 to 0.5.1 (#9361)
2023-06-07 15:29:54 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "a216b506622bb1d316cd51328dce24e07bdff4a6128a47c7e7fad11878d5adbb"
Bump criterion from 0.4.0 to 0.5.1 (#9361)
2023-06-07 15:29:54 +02:00
dependencies = [
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
"anstream",
Bump criterion from 0.4.0 to 0.5.1 (#9361)
2023-06-07 15:29:54 +02:00
"anstyle",
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 20:39:54 +01:00
"clap_lex",
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
"strsim",
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
"terminal_size 0.3.0",
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 20:39:54 +01:00
]
[[package]]
name = "clap_lex"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.6.0"
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 20:39:54 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "702fc72eb24e5a1e48ce58027a675bc24edd52096d5397d4aea7c6dd9eca0bd1"
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
[[package]]
name = "codepage"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
checksum = "8b0e9222c0cdf2c6ac27d73f664f9520266fa911c3106329d359f8861cb8bde9"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"encoding_rs",
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
]
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
[[package]]
name = "colorchoice"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "acbf1af155f9b9ef647e42cdc158db4b64a1b61f743629225fde6f3e0be2a7c7"
Polars update (#4875) * update to polars 0.20 * add to date parser for series
2022-03-19 12:13:34 +01:00
[[package]]
name = "comfy-table"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "7.1.0"
Polars update (#4875) * update to polars 0.20 * add to date parser for series
2022-03-19 12:13:34 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "7c64043d6c7b7a4c58e39e7efccfdea7b93d885a795d0c054a69dbbf4dd52686"
Polars update (#4875) * update to polars 0.20 * add to date parser for series
2022-03-19 12:13:34 +01:00
dependencies = [
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"crossterm",
"strum",
"strum_macros",
Polars update (#4875) * update to polars 0.20 * add to date parser for series
2022-03-19 12:13:34 +01:00
"unicode-width",
]
Move from language-reporting to codespan (#1825)
2020-05-18 20:44:27 +02:00
[[package]]
Try out select completions from dialoguer
2021-10-15 20:37:58 +02:00
name = "console"
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
version = "0.15.7"
Try out select completions from dialoguer
2021-10-15 20:37:58 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
checksum = "c926e00cc70edefdc64d3a5ff31cc65bb97a3460097762bd23afb4d8145fccf8"
Try out select completions from dialoguer
2021-10-15 20:37:58 +02:00
dependencies = [
"encode_unicode",
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
"lazy_static",
Try out select completions from dialoguer
2021-10-15 20:37:58 +02:00
"libc",
"unicode-width",
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
"windows-sys 0.45.0",
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
]
update ini dependency (#9426) # Description This PR updates the ini dependency. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 20:33:00 +02:00
[[package]]
name = "const-random"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.1.17"
update ini dependency (#9426) # Description This PR updates the ini dependency. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 20:33:00 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "5aaf16c9c2c612020bcfd042e170f6e32de9b9d75adb5277cdbbd2e2c8c8299a"
update ini dependency (#9426) # Description This PR updates the ini dependency. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 20:33:00 +02:00
dependencies = [
"const-random-macro",
]
[[package]]
name = "const-random-macro"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.1.16"
update ini dependency (#9426) # Description This PR updates the ini dependency. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 20:33:00 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "f9d839f2a20b0aee515dc581a6172f2321f96cab76c1a38a4c584a194955390e"
update ini dependency (#9426) # Description This PR updates the ini dependency. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 20:33:00 +02:00
dependencies = [
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"getrandom",
update ini dependency (#9426) # Description This PR updates the ini dependency. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 20:33:00 +02:00
"once_cell",
"tiny-keccak",
]
update shadow-rs, update git2, remove indexmap from `version` (#5086)
2022-04-04 16:59:59 +02:00
[[package]]
name = "const_format"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.2.32"
update shadow-rs, update git2, remove indexmap from `version` (#5086)
2022-04-04 16:59:59 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "e3a214c7af3d04997541b18d432afaff4c455e79e2029079647e72fc2bd27673"
update shadow-rs, update git2, remove indexmap from `version` (#5086)
2022-04-04 16:59:59 +02:00
dependencies = [
"const_format_proc_macros",
]
[[package]]
name = "const_format_proc_macros"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.2.32"
update shadow-rs, update git2, remove indexmap from `version` (#5086)
2022-04-04 16:59:59 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "c7f6ff08fd20f4f299298a28e2dfa8a8ba1036e6cd2460ac1de7b425d76f2500"
update shadow-rs, update git2, remove indexmap from `version` (#5086)
2022-04-04 16:59:59 +02:00
dependencies = [
"proc-macro2",
"quote",
"unicode-xid",
]
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
[[package]]
name = "core-foundation"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.9.4"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "91e195e091a93c46f7102ec7818a2aa394e1e1771c3ab4825963fa03e45afb8f"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
dependencies = [
Temporarily(?) switch from heim+uom to sysinfo (#2954) * Switch from heim to sysinfo * WIP * more cleanup * fmt * lint
2021-01-20 08:18:38 +01:00
"core-foundation-sys",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"libc",
Add opening urls
2019-06-08 20:09:17 +02:00
]
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
[[package]]
name = "core-foundation-sys"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.8.6"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "06ea2b9bc92be3c2baa9334a323ebca2d6f074ff852cd1d7b11064035cd3868f"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
Autoenv rewrite, security and scripting (#2083) * Add args in .nurc file to environment * Working dummy version * Add add_nurc to sync_env command * Parse .nurc file * Delete env vars after leaving directory * Removing vals not working, strangely * Refactoring, add comment * Debugging * Debug by logging to file * Add and remove env var behavior appears correct However, it does not use existing code that well. * Move work to cli.rs * Parse config directories * I am in a state of distress * Rename .nurc to .nu * Some notes for me * Refactoring * Removing vars works, but not done in a very nice fashion * Refactor env_vars_to_delete * Refactor env_vars_to_add() * Move directory environment code to separate file * Refactor from_config * Restore env values * Working? * Working? * Update comments and change var name * Formatting * Remove vars after leaving dir * Remove notes I made * Rename config function * Clippy * Cleanup and handle errors * cargo fmt * Better error messages, remove last (?) unwrap * FORMAT PLZ * Rename whitelisted_directories to allowed_directories * Add comment to clarify how overwritten values are restored. * Change list of allowed dirs to indexmap * Rewrite starting * rewrite everything * Overwritten env values tracks an indexmap instead of vector * Refactor restore function * Untrack removed vars properly * Performance concerns * Performance concerns * Error handling * Clippy * Add type aliases for String and OsString * Deletion almost works * Working? * Error handling and refactoring * nicer errors * Add TODO file * Move outside of loop * Error handling * Reworking adding of vars * Reworking adding of vars * Ready for testing * Refactoring * Restore overwritten vals code * todo.org * Remove overwritten values tracking, as it is not needed * Cleanup, stop tracking overwritten values as nu takes care of it * Init autoenv command * Initialize autoenv and autoenv trust * autoenv trust toml * toml * Use serde for autoenv * Optional directory arg * Add autoenv untrust command * ... actually add autoenv untrust this time * OsString and paths * Revert "OsString and paths" This reverts commit e6eedf882498c1365ecfc899e5ec11bd83cb055c. * Fix path * Fix path * Autoenv trust and untrust * Start using autoenv * Check hashes * Use trust functionality when setting vars * Remove unused code * Clippy * Nicer errors for autoenv commands * Non-working errors * Update error description * Satisfy fmt * Errors * Errors print, but not nicely * Nicer errors * fmt * Delete accidentally added todo.org file * Rename direnv to autoenv * Use ShellError instead of Error * Change tests to pass, danger zone? * Clippy and errors * Clippy... again * Replace match with or_else * Use sha2 crate for hashing * parsing and error msg * Refactoring * Only apply vars once * if parent dir * Delete vars * Rework exit code * Adding works * restore * Fix possibility of infinite loop * Refactoring * Non-working * Revert "Non-working" This reverts commit e231b85570bcb3fc838f950e9f5004c6a7c5a2ac. * Revert "Revert "Non-working"" This reverts commit 804092e46a752266576b044401cc97c317e41f21. * Autoenv trust works without restart * Cargo fix * Script vars * Serde * Serde errors * Entry and exitscripts * Clippy * Support windows and handle errors * Formatting * Fix infinite loop on windows * Debugging windows loop * More windows infinite loop debugging * Windows loop debugging #3 * windows loop #4 * Don't return err * Cleanup unused code * Infinite loop debug * Loop debugging * Check if infinite loop is vars_to_add * env_vars_to_add does not terminate, skip loop as test * Hypothesis: std::env::current_dir() is messing with something * Hypothesis: std::env::current_dir() is messing with something * plz * make clippy happy * debugging in env_vars_to_add * Debbuging env_vars_to_add #2 * clippy * clippy.. * Fool clippy * Fix another infinite loop * Binary search for error location x) * Binary search #3 * fmt * Binary search #4 * more searching... * closing in... maybe * PLZ * Cleanup * Restore commented out functionality * Handle case when user gives the directory "." * fmt * Use fs::canonicalize for paths * Create optional script section * fmt * Add exitscripts even if no entryscripts are defined * All sections in .nu-env are now optional * Re-read config file each directory change * Hot reload after autoenv untrust, don't run exitscripts if untrusted * Debugging * Fix issue with recursive adding of vars * Thank you for finding my issues Mr. Azure * use std::env
2020-07-05 19:34:00 +02:00
[[package]]
Dataframe commands (#3502) * Sample command * Join command with checks * More dataframes commands * Groupby and aggregate commands * Missing feature dataframe flag * Renamed file * New commands for dataframes * error parser and df reference * filter command for dataframes * removed name from nu_dataframe * commands to save to parquet and csv
2021-06-03 08:23:14 +02:00
name = "cpufeatures"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.2.11"
Autoenv rewrite, security and scripting (#2083) * Add args in .nurc file to environment * Working dummy version * Add add_nurc to sync_env command * Parse .nurc file * Delete env vars after leaving directory * Removing vals not working, strangely * Refactoring, add comment * Debugging * Debug by logging to file * Add and remove env var behavior appears correct However, it does not use existing code that well. * Move work to cli.rs * Parse config directories * I am in a state of distress * Rename .nurc to .nu * Some notes for me * Refactoring * Removing vars works, but not done in a very nice fashion * Refactor env_vars_to_delete * Refactor env_vars_to_add() * Move directory environment code to separate file * Refactor from_config * Restore env values * Working? * Working? * Update comments and change var name * Formatting * Remove vars after leaving dir * Remove notes I made * Rename config function * Clippy * Cleanup and handle errors * cargo fmt * Better error messages, remove last (?) unwrap * FORMAT PLZ * Rename whitelisted_directories to allowed_directories * Add comment to clarify how overwritten values are restored. * Change list of allowed dirs to indexmap * Rewrite starting * rewrite everything * Overwritten env values tracks an indexmap instead of vector * Refactor restore function * Untrack removed vars properly * Performance concerns * Performance concerns * Error handling * Clippy * Add type aliases for String and OsString * Deletion almost works * Working? * Error handling and refactoring * nicer errors * Add TODO file * Move outside of loop * Error handling * Reworking adding of vars * Reworking adding of vars * Ready for testing * Refactoring * Restore overwritten vals code * todo.org * Remove overwritten values tracking, as it is not needed * Cleanup, stop tracking overwritten values as nu takes care of it * Init autoenv command * Initialize autoenv and autoenv trust * autoenv trust toml * toml * Use serde for autoenv * Optional directory arg * Add autoenv untrust command * ... actually add autoenv untrust this time * OsString and paths * Revert "OsString and paths" This reverts commit e6eedf882498c1365ecfc899e5ec11bd83cb055c. * Fix path * Fix path * Autoenv trust and untrust * Start using autoenv * Check hashes * Use trust functionality when setting vars * Remove unused code * Clippy * Nicer errors for autoenv commands * Non-working errors * Update error description * Satisfy fmt * Errors * Errors print, but not nicely * Nicer errors * fmt * Delete accidentally added todo.org file * Rename direnv to autoenv * Use ShellError instead of Error * Change tests to pass, danger zone? * Clippy and errors * Clippy... again * Replace match with or_else * Use sha2 crate for hashing * parsing and error msg * Refactoring * Only apply vars once * if parent dir * Delete vars * Rework exit code * Adding works * restore * Fix possibility of infinite loop * Refactoring * Non-working * Revert "Non-working" This reverts commit e231b85570bcb3fc838f950e9f5004c6a7c5a2ac. * Revert "Revert "Non-working"" This reverts commit 804092e46a752266576b044401cc97c317e41f21. * Autoenv trust works without restart * Cargo fix * Script vars * Serde * Serde errors * Entry and exitscripts * Clippy * Support windows and handle errors * Formatting * Fix infinite loop on windows * Debugging windows loop * More windows infinite loop debugging * Windows loop debugging #3 * windows loop #4 * Don't return err * Cleanup unused code * Infinite loop debug * Loop debugging * Check if infinite loop is vars_to_add * env_vars_to_add does not terminate, skip loop as test * Hypothesis: std::env::current_dir() is messing with something * Hypothesis: std::env::current_dir() is messing with something * plz * make clippy happy * debugging in env_vars_to_add * Debbuging env_vars_to_add #2 * clippy * clippy.. * Fool clippy * Fix another infinite loop * Binary search for error location x) * Binary search #3 * fmt * Binary search #4 * more searching... * closing in... maybe * PLZ * Cleanup * Restore commented out functionality * Handle case when user gives the directory "." * fmt * Use fs::canonicalize for paths * Create optional script section * fmt * Add exitscripts even if no entryscripts are defined * All sections in .nu-env are now optional * Re-read config file each directory change * Hot reload after autoenv untrust, don't run exitscripts if untrusted * Debugging * Fix issue with recursive adding of vars * Thank you for finding my issues Mr. Azure * use std::env
2020-07-05 19:34:00 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "ce420fe07aecd3e67c5f910618fe65e94158f6dcc0adf44e00d69ce2bdfe0fd0"
Dataframe commands (#3502) * Sample command * Join command with checks * More dataframes commands * Groupby and aggregate commands * Missing feature dataframe flag * Renamed file * New commands for dataframes * error parser and df reference * filter command for dataframes * removed name from nu_dataframe * commands to save to parquet and csv
2021-06-03 08:23:14 +02:00
dependencies = [
"libc",
]
Autoenv rewrite, security and scripting (#2083) * Add args in .nurc file to environment * Working dummy version * Add add_nurc to sync_env command * Parse .nurc file * Delete env vars after leaving directory * Removing vals not working, strangely * Refactoring, add comment * Debugging * Debug by logging to file * Add and remove env var behavior appears correct However, it does not use existing code that well. * Move work to cli.rs * Parse config directories * I am in a state of distress * Rename .nurc to .nu * Some notes for me * Refactoring * Removing vars works, but not done in a very nice fashion * Refactor env_vars_to_delete * Refactor env_vars_to_add() * Move directory environment code to separate file * Refactor from_config * Restore env values * Working? * Working? * Update comments and change var name * Formatting * Remove vars after leaving dir * Remove notes I made * Rename config function * Clippy * Cleanup and handle errors * cargo fmt * Better error messages, remove last (?) unwrap * FORMAT PLZ * Rename whitelisted_directories to allowed_directories * Add comment to clarify how overwritten values are restored. * Change list of allowed dirs to indexmap * Rewrite starting * rewrite everything * Overwritten env values tracks an indexmap instead of vector * Refactor restore function * Untrack removed vars properly * Performance concerns * Performance concerns * Error handling * Clippy * Add type aliases for String and OsString * Deletion almost works * Working? * Error handling and refactoring * nicer errors * Add TODO file * Move outside of loop * Error handling * Reworking adding of vars * Reworking adding of vars * Ready for testing * Refactoring * Restore overwritten vals code * todo.org * Remove overwritten values tracking, as it is not needed * Cleanup, stop tracking overwritten values as nu takes care of it * Init autoenv command * Initialize autoenv and autoenv trust * autoenv trust toml * toml * Use serde for autoenv * Optional directory arg * Add autoenv untrust command * ... actually add autoenv untrust this time * OsString and paths * Revert "OsString and paths" This reverts commit e6eedf882498c1365ecfc899e5ec11bd83cb055c. * Fix path * Fix path * Autoenv trust and untrust * Start using autoenv * Check hashes * Use trust functionality when setting vars * Remove unused code * Clippy * Nicer errors for autoenv commands * Non-working errors * Update error description * Satisfy fmt * Errors * Errors print, but not nicely * Nicer errors * fmt * Delete accidentally added todo.org file * Rename direnv to autoenv * Use ShellError instead of Error * Change tests to pass, danger zone? * Clippy and errors * Clippy... again * Replace match with or_else * Use sha2 crate for hashing * parsing and error msg * Refactoring * Only apply vars once * if parent dir * Delete vars * Rework exit code * Adding works * restore * Fix possibility of infinite loop * Refactoring * Non-working * Revert "Non-working" This reverts commit e231b85570bcb3fc838f950e9f5004c6a7c5a2ac. * Revert "Revert "Non-working"" This reverts commit 804092e46a752266576b044401cc97c317e41f21. * Autoenv trust works without restart * Cargo fix * Script vars * Serde * Serde errors * Entry and exitscripts * Clippy * Support windows and handle errors * Formatting * Fix infinite loop on windows * Debugging windows loop * More windows infinite loop debugging * Windows loop debugging #3 * windows loop #4 * Don't return err * Cleanup unused code * Infinite loop debug * Loop debugging * Check if infinite loop is vars_to_add * env_vars_to_add does not terminate, skip loop as test * Hypothesis: std::env::current_dir() is messing with something * Hypothesis: std::env::current_dir() is messing with something * plz * make clippy happy * debugging in env_vars_to_add * Debbuging env_vars_to_add #2 * clippy * clippy.. * Fool clippy * Fix another infinite loop * Binary search for error location x) * Binary search #3 * fmt * Binary search #4 * more searching... * closing in... maybe * PLZ * Cleanup * Restore commented out functionality * Handle case when user gives the directory "." * fmt * Use fs::canonicalize for paths * Create optional script section * fmt * Add exitscripts even if no entryscripts are defined * All sections in .nu-env are now optional * Re-read config file each directory change * Hot reload after autoenv untrust, don't run exitscripts if untrusted * Debugging * Fix issue with recursive adding of vars * Thank you for finding my issues Mr. Azure * use std::env
2020-07-05 19:34:00 +02:00
Expose polars avro support (#10019) # Description Exposes polars avro support via dfr open and dfr to-avro --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-08-16 03:31:49 +02:00
[[package]]
name = "crc"
version = "2.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "49fc9a695bca7f35f5f4c15cddc84415f66a74ea78eef08e90c5024f2b540e23"
dependencies = [
"crc-catalog",
]
[[package]]
name = "crc-catalog"
version = "1.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ccaeedb56da03b09f598226e25e80088cb4cd25f316e6e4df7d695f0feeb1403"
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "crc32fast"
merge main
2022-02-08 14:28:21 +01:00
version = "1.3.2"
Bat
2019-05-18 03:24:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
merge main
2022-02-08 14:28:21 +01:00
checksum = "b540bd8bc810d3885c6ea91e2018302f68baba2129ab3e88f32389ee9370880d"
`from xlsx` `from ods` and `from toml` (#352) * MathEval Variance and Stddev * Fix tests and linting * Typo * Deal with streams when they are not tables * `from toml` command * From ods * From XLSX
2021-11-19 20:23:35 +01:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Bat
2019-05-18 03:24:13 +02:00
]
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
[[package]]
name = "criterion"
Bump criterion from 0.4.0 to 0.5.1 (#9361)
2023-06-07 15:29:54 +02:00
version = "0.5.1"
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump criterion from 0.4.0 to 0.5.1 (#9361)
2023-06-07 15:29:54 +02:00
checksum = "f2b12d017a929603d80db1831cd3a24082f8137ce19c69e6447f54f5fc8d692f"
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
dependencies = [
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 20:39:54 +01:00
"anes",
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
"cast",
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 20:39:54 +01:00
"ciborium",
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
"clap",
"criterion-plot",
Bump criterion from 0.4.0 to 0.5.1 (#9361)
2023-06-07 15:29:54 +02:00
"is-terminal",
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 02:22:25 +02:00
"itertools 0.10.5",
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
"num-traits",
Bump criterion from 0.4.0 to 0.5.1 (#9361)
2023-06-07 15:29:54 +02:00
"once_cell",
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
"oorandom",
"plotters",
"rayon",
"regex",
"serde",
"serde_derive",
"serde_json",
"tinytemplate",
"walkdir",
]
[[package]]
name = "criterion-plot"
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 20:39:54 +01:00
version = "0.5.0"
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 20:39:54 +01:00
checksum = "6b50826342786a51a89e2da3a28f1c32b06e387201bc2d19791f622c673706b1"
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
dependencies = [
"cast",
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 02:22:25 +02:00
"itertools 0.10.5",
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
]
cargo update (#5639)
2022-05-25 19:13:14 +02:00
[[package]]
name = "critical-section"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.1.2"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "7059fff8937831a9ae6f0fe4d658ffabf58f2ca96aa9dec1c889f936f705f216"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
Added `math product` support (#2249) * added math product: working initial impl * resolving merge conflicts * impl std::ops::Mul for Filesize * rebased with main; refactored product implementation * fixed error msg, added docs for math product
2020-08-27 07:58:01 +02:00
[[package]]
name = "crossbeam-channel"
Revert lock file changes due to openssl build fail (#11328) A theoretically semver compatible version bump of dependencies in the `Cargo.lock` was part of #11302. The particular upstream openSSL version pulled in by that fails to build on our RISC-V build config (3.2.0) - https://github.com/nushell/nushell/pull/11302#issuecomment-1856011363 - https://github.com/nushell/nightly/actions/runs/7210339119/job/19643253780 So far no updated openssl release is available or it is unclear how the runner needs to be configured to avoid the issue described in: - https://github.com/openssl/openssl/issues/22871 Out of abundance of caution let's try to revert this version bump and try to figure out a solution later, so we can ship our `0.88.1` patch release.
2023-12-14 18:09:28 +01:00
version = "0.5.8"
Added `math product` support (#2249) * added math product: working initial impl * resolving merge conflicts * impl std::ops::Mul for Filesize * rebased with main; refactored product implementation * fixed error msg, added docs for math product
2020-08-27 07:58:01 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Revert lock file changes due to openssl build fail (#11328) A theoretically semver compatible version bump of dependencies in the `Cargo.lock` was part of #11302. The particular upstream openSSL version pulled in by that fails to build on our RISC-V build config (3.2.0) - https://github.com/nushell/nushell/pull/11302#issuecomment-1856011363 - https://github.com/nushell/nightly/actions/runs/7210339119/job/19643253780 So far no updated openssl release is available or it is unclear how the runner needs to be configured to avoid the issue described in: - https://github.com/openssl/openssl/issues/22871 Out of abundance of caution let's try to revert this version bump and try to figure out a solution later, so we can ship our `0.88.1` patch release.
2023-12-14 18:09:28 +01:00
checksum = "a33c2bf77f2df06183c3aa30d1e96c0695a313d4f9c453cc3762a6db39f99200"
add sys command
2021-10-01 08:53:47 +02:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"crossbeam-utils",
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 15:47:30 +02:00
]
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
[[package]]
name = "crossbeam-deque"
Revert lock file changes due to openssl build fail (#11328) A theoretically semver compatible version bump of dependencies in the `Cargo.lock` was part of #11302. The particular upstream openSSL version pulled in by that fails to build on our RISC-V build config (3.2.0) - https://github.com/nushell/nushell/pull/11302#issuecomment-1856011363 - https://github.com/nushell/nightly/actions/runs/7210339119/job/19643253780 So far no updated openssl release is available or it is unclear how the runner needs to be configured to avoid the issue described in: - https://github.com/openssl/openssl/issues/22871 Out of abundance of caution let's try to revert this version bump and try to figure out a solution later, so we can ship our `0.88.1` patch release.
2023-12-14 18:09:28 +01:00
version = "0.8.3"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Revert lock file changes due to openssl build fail (#11328) A theoretically semver compatible version bump of dependencies in the `Cargo.lock` was part of #11302. The particular upstream openSSL version pulled in by that fails to build on our RISC-V build config (3.2.0) - https://github.com/nushell/nushell/pull/11302#issuecomment-1856011363 - https://github.com/nushell/nightly/actions/runs/7210339119/job/19643253780 So far no updated openssl release is available or it is unclear how the runner needs to be configured to avoid the issue described in: - https://github.com/openssl/openssl/issues/22871 Out of abundance of caution let's try to revert this version bump and try to figure out a solution later, so we can ship our `0.88.1` patch release.
2023-12-14 18:09:28 +01:00
checksum = "ce6fd6f855243022dcecf8702fef0c297d4338e226845fe067f6341ad9fa0cef"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"crossbeam-epoch",
"crossbeam-utils",
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 15:47:30 +02:00
]
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
[[package]]
name = "crossbeam-epoch"
Revert lock file changes due to openssl build fail (#11328) A theoretically semver compatible version bump of dependencies in the `Cargo.lock` was part of #11302. The particular upstream openSSL version pulled in by that fails to build on our RISC-V build config (3.2.0) - https://github.com/nushell/nushell/pull/11302#issuecomment-1856011363 - https://github.com/nushell/nightly/actions/runs/7210339119/job/19643253780 So far no updated openssl release is available or it is unclear how the runner needs to be configured to avoid the issue described in: - https://github.com/openssl/openssl/issues/22871 Out of abundance of caution let's try to revert this version bump and try to figure out a solution later, so we can ship our `0.88.1` patch release.
2023-12-14 18:09:28 +01:00
version = "0.9.15"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Revert lock file changes due to openssl build fail (#11328) A theoretically semver compatible version bump of dependencies in the `Cargo.lock` was part of #11302. The particular upstream openSSL version pulled in by that fails to build on our RISC-V build config (3.2.0) - https://github.com/nushell/nushell/pull/11302#issuecomment-1856011363 - https://github.com/nushell/nightly/actions/runs/7210339119/job/19643253780 So far no updated openssl release is available or it is unclear how the runner needs to be configured to avoid the issue described in: - https://github.com/openssl/openssl/issues/22871 Out of abundance of caution let's try to revert this version bump and try to figure out a solution later, so we can ship our `0.88.1` patch release.
2023-12-14 18:09:28 +01:00
checksum = "ae211234986c545741a7dc064309f67ee1e5ad243d0e48335adc0484d960bcc7"
add sys command
2021-10-01 08:53:47 +02:00
dependencies = [
Help menu (#4992) * nu-completer with suggestions * help menu with scrolling * updates description rows based on space * configuration for help menu * update nu-ansi-term * corrected test for update cells * changed keybinding
2022-03-27 15:01:04 +02:00
"autocfg",
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"crossbeam-utils",
"memoffset",
Revert lock file changes due to openssl build fail (#11328) A theoretically semver compatible version bump of dependencies in the `Cargo.lock` was part of #11302. The particular upstream openSSL version pulled in by that fails to build on our RISC-V build config (3.2.0) - https://github.com/nushell/nushell/pull/11302#issuecomment-1856011363 - https://github.com/nushell/nightly/actions/runs/7210339119/job/19643253780 So far no updated openssl release is available or it is unclear how the runner needs to be configured to avoid the issue described in: - https://github.com/openssl/openssl/issues/22871 Out of abundance of caution let's try to revert this version bump and try to figure out a solution later, so we can ship our `0.88.1` patch release.
2023-12-14 18:09:28 +01:00
"scopeguard",
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
]
Update `polars` to `0.33` (#10672) # Description Open question: Undocumented behavior for the new argument `ambiguous` to the `as_datetime` methods. I cheated by passing a default (assuming empty string). This appears like an API primarily serving the python impl: https://pola-rs.github.io/polars/py-polars/html/reference/expressions/api/polars.Expr.str.to_datetime.html#polars-expr-str-to-datetime # User-Facing Changes Only dependent on breaking changes to the behavior of polars. # Tests + Formatting No observed changes to tests Manually checked `dfr as-datetime`, doesn't seem to panic.
2023-10-11 21:28:18 +02:00
[[package]]
name = "crossbeam-queue"
Revert lock file changes due to openssl build fail (#11328) A theoretically semver compatible version bump of dependencies in the `Cargo.lock` was part of #11302. The particular upstream openSSL version pulled in by that fails to build on our RISC-V build config (3.2.0) - https://github.com/nushell/nushell/pull/11302#issuecomment-1856011363 - https://github.com/nushell/nightly/actions/runs/7210339119/job/19643253780 So far no updated openssl release is available or it is unclear how the runner needs to be configured to avoid the issue described in: - https://github.com/openssl/openssl/issues/22871 Out of abundance of caution let's try to revert this version bump and try to figure out a solution later, so we can ship our `0.88.1` patch release.
2023-12-14 18:09:28 +01:00
version = "0.3.8"
Update `polars` to `0.33` (#10672) # Description Open question: Undocumented behavior for the new argument `ambiguous` to the `as_datetime` methods. I cheated by passing a default (assuming empty string). This appears like an API primarily serving the python impl: https://pola-rs.github.io/polars/py-polars/html/reference/expressions/api/polars.Expr.str.to_datetime.html#polars-expr-str-to-datetime # User-Facing Changes Only dependent on breaking changes to the behavior of polars. # Tests + Formatting No observed changes to tests Manually checked `dfr as-datetime`, doesn't seem to panic.
2023-10-11 21:28:18 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Revert lock file changes due to openssl build fail (#11328) A theoretically semver compatible version bump of dependencies in the `Cargo.lock` was part of #11302. The particular upstream openSSL version pulled in by that fails to build on our RISC-V build config (3.2.0) - https://github.com/nushell/nushell/pull/11302#issuecomment-1856011363 - https://github.com/nushell/nightly/actions/runs/7210339119/job/19643253780 So far no updated openssl release is available or it is unclear how the runner needs to be configured to avoid the issue described in: - https://github.com/openssl/openssl/issues/22871 Out of abundance of caution let's try to revert this version bump and try to figure out a solution later, so we can ship our `0.88.1` patch release.
2023-12-14 18:09:28 +01:00
checksum = "d1cfb3ea8a53f37c40dea2c7bedcbd88bdfae54f5e2175d6ecaff1c988353add"
Update `polars` to `0.33` (#10672) # Description Open question: Undocumented behavior for the new argument `ambiguous` to the `as_datetime` methods. I cheated by passing a default (assuming empty string). This appears like an API primarily serving the python impl: https://pola-rs.github.io/polars/py-polars/html/reference/expressions/api/polars.Expr.str.to_datetime.html#polars-expr-str-to-datetime # User-Facing Changes Only dependent on breaking changes to the behavior of polars. # Tests + Formatting No observed changes to tests Manually checked `dfr as-datetime`, doesn't seem to panic.
2023-10-11 21:28:18 +02:00
dependencies = [
"cfg-if",
"crossbeam-utils",
]
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
[[package]]
name = "crossbeam-utils"
Revert lock file changes due to openssl build fail (#11328) A theoretically semver compatible version bump of dependencies in the `Cargo.lock` was part of #11302. The particular upstream openSSL version pulled in by that fails to build on our RISC-V build config (3.2.0) - https://github.com/nushell/nushell/pull/11302#issuecomment-1856011363 - https://github.com/nushell/nightly/actions/runs/7210339119/job/19643253780 So far no updated openssl release is available or it is unclear how the runner needs to be configured to avoid the issue described in: - https://github.com/openssl/openssl/issues/22871 Out of abundance of caution let's try to revert this version bump and try to figure out a solution later, so we can ship our `0.88.1` patch release.
2023-12-14 18:09:28 +01:00
version = "0.8.16"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Revert lock file changes due to openssl build fail (#11328) A theoretically semver compatible version bump of dependencies in the `Cargo.lock` was part of #11302. The particular upstream openSSL version pulled in by that fails to build on our RISC-V build config (3.2.0) - https://github.com/nushell/nushell/pull/11302#issuecomment-1856011363 - https://github.com/nushell/nightly/actions/runs/7210339119/job/19643253780 So far no updated openssl release is available or it is unclear how the runner needs to be configured to avoid the issue described in: - https://github.com/openssl/openssl/issues/22871 Out of abundance of caution let's try to revert this version bump and try to figure out a solution later, so we can ship our `0.88.1` patch release.
2023-12-14 18:09:28 +01:00
checksum = "5a22b2d63d4d1dc0b7f1b6b2747dd0088008a9be28b6ddf0b1e7d335e3037294"
add sys command
2021-10-01 08:53:47 +02:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
]
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 02:22:25 +02:00
[[package]]
name = "crossterm"
version = "0.27.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f476fe445d41c9e991fd07515a6f463074b782242ccf4a5b7b1d1012e70824df"
dependencies = [
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"bitflags 2.4.1",
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 02:22:25 +02:00
"crossterm_winapi",
"libc",
"mio",
"parking_lot",
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
"serde",
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
"signal-hook",
"signal-hook-mio",
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"winapi",
Bar Chart baseline. (#2621) Bar Chart ready.
2020-09-30 20:27:52 +02:00
]
updated dependencies (#2857) Same as #2786 Co-authored-by: sousajo <sousajo@pop-os.localdomain> Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-07 01:38:22 +01:00
[[package]]
name = "crossterm_winapi"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.9.1"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "acdd7c62a3665c7f6830a51635d9ac9b23ed385797f70a83bb8bafe9c572ab2b"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"winapi",
updated dependencies (#2857) Same as #2786 Co-authored-by: sousajo <sousajo@pop-os.localdomain> Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-07 01:38:22 +01:00
]
update ini dependency (#9426) # Description This PR updates the ini dependency. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 20:33:00 +02:00
[[package]]
name = "crunchy"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7a81dae078cea95a014a339291cec439d2f232ebe854a9d672b796c6afafa9b7"
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
[[package]]
Port `hash`, `hash md5` and `hash sha256` commands (#464) `hash` by itself is only printing the help message. The other two are simply using the same generic implementation.
2021-12-11 00:14:28 +01:00
name = "crypto-common"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
version = "0.1.6"
Port `hash`, `hash md5` and `hash sha256` commands (#464) `hash` by itself is only printing the help message. The other two are simply using the same generic implementation.
2021-12-11 00:14:28 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
checksum = "1bfb12502f3fc46cca1bb51ac28df9d618d813cdc3d2f25b9fe775a34af26bb3"
Port `hash`, `hash md5` and `hash sha256` commands (#464) `hash` by itself is only printing the help message. The other two are simply using the same generic implementation.
2021-12-11 00:14:28 +01:00
dependencies = [
Consider space for single `...` column not enough space (#6080) * nu-table: Refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: consider space for single `...` column not enough space Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-19 19:35:25 +02:00
"generic-array",
corrected history menu (#4814)
2022-03-10 21:58:11 +01:00
"typenum",
updated fetch to surf2.2 and feature h1-client-rustls (#3120)
2021-03-03 19:18:11 +01:00
]
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
[[package]]
name = "cssparser"
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
version = "0.31.2"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
checksum = "5b3df4f93e5fbbe73ec01ec8d3f68bba73107993a5b1e7519273c32db9b0d5be"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
dependencies = [
"cssparser-macros",
"dtoa-short",
Bump scraper from 0.14.0 to 0.15.0 (#8331) Bumps [scraper](https://github.com/causal-agent/scraper) from 0.14.0 to 0.15.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/causal-agent/scraper/releases">scraper's releases</a>.</em></p> <blockquote> <h2>0.15.0</h2> <h2>What's Changed</h2> <ul> <li>Bump cssparser to 0.28 and selectors to 0.23. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li>Create dependabot.yml by <a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li>Re-export Element trait from selectors crate by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/98">causal-agent/scraper#98</a></li> <li>build(deps): fix unchecked lock and update deps by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li>Re-export selectors' CaseSensitivity enum as it is part of our public API. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/108">causal-agent/scraper#108</a></li> <li>perf(element): add one sweep element creation by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/109">causal-agent/scraper#109</a></li> <li>Added feature flag <code>atomic</code> to make use of atomic <code>StrTendril</code> type. by <a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li><a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li><a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li><a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/causal-agent/scraper/commit/3cb7e9a3202fc6f8b80820135ad071916bc2908b"><code>3cb7e9a</code></a> Version 0.15.0</li> <li><a href="https://github.com/causal-agent/scraper/commit/06f395efe0fb4e9c31cdbd81a9f9e41802572b33"><code>06f395e</code></a> Apply clippy suggestion</li> <li><a href="https://github.com/causal-agent/scraper/commit/ec91bf1ebc9921ca2adeddf93555081912c33334"><code>ec91bf1</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/102">#102</a> from jaboatman/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/4b7fb13446f5ab4400b1fdfb3092b71b3157af9a"><code>4b7fb13</code></a> Merge remote-tracking branch 'upstream/master'</li> <li><a href="https://github.com/causal-agent/scraper/commit/aa479ea170b7f2b463ccba85de0c802318d19abe"><code>aa479ea</code></a> perf(element): add one sweep element creation (<a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/109">#109</a>)</li> <li><a href="https://github.com/causal-agent/scraper/commit/9a6a638db208682593d83bef53c29052336c0487"><code>9a6a638</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/108">#108</a> from adamreichold/also-re-export-case-sensitivity</li> <li><a href="https://github.com/causal-agent/scraper/commit/794b5eef87aa1009a31d4d29093269a04e7d80fa"><code>794b5ee</code></a> Re-export selectors' CaseSensitivity enum as it is part of our public API.</li> <li><a href="https://github.com/causal-agent/scraper/commit/6abb8cd625af5ea4f5a59530f03436aa448f7c56"><code>6abb8cd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/107">#107</a> from j-mendez/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/c3dd2600dcd4c17424a307c2f82cfcab41943014"><code>c3dd260</code></a> chore(minor): fix element classes map format</li> <li><a href="https://github.com/causal-agent/scraper/commit/b7955b9049ccf5b685f53854d88cca322aa80bac"><code>b7955b9</code></a> perf(selectors): add lazy classes map</li> <li>Additional commits viewable in <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=scraper&package-manager=cargo&previous-version=0.14.0&new-version=0.15.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-06 04:37:22 +01:00
"itoa",
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"phf 0.11.2",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"smallvec",
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
]
[[package]]
name = "cssparser-macros"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.6.1"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "13b588ba4ac1a99f7f2964d24b3d896ddc6bf847ee3855dbd4366f058cfcd331"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
dependencies = [
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "csv"
Bump csv from 1.2.2 to 1.3.0 (#10733)
2023-10-18 23:01:14 +02:00
version = "1.3.0"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump csv from 1.2.2 to 1.3.0 (#10733)
2023-10-18 23:01:14 +02:00
checksum = "ac574ff4d437a7b5ad237ef331c17ccca63c46479e5b5453eb8e10bb99a759fe"
objectshell initial commit
2019-05-10 18:59:12 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"csv-core",
Bump scraper from 0.14.0 to 0.15.0 (#8331) Bumps [scraper](https://github.com/causal-agent/scraper) from 0.14.0 to 0.15.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/causal-agent/scraper/releases">scraper's releases</a>.</em></p> <blockquote> <h2>0.15.0</h2> <h2>What's Changed</h2> <ul> <li>Bump cssparser to 0.28 and selectors to 0.23. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li>Create dependabot.yml by <a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li>Re-export Element trait from selectors crate by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/98">causal-agent/scraper#98</a></li> <li>build(deps): fix unchecked lock and update deps by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li>Re-export selectors' CaseSensitivity enum as it is part of our public API. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/108">causal-agent/scraper#108</a></li> <li>perf(element): add one sweep element creation by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/109">causal-agent/scraper#109</a></li> <li>Added feature flag <code>atomic</code> to make use of atomic <code>StrTendril</code> type. by <a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li><a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li><a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li><a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/causal-agent/scraper/commit/3cb7e9a3202fc6f8b80820135ad071916bc2908b"><code>3cb7e9a</code></a> Version 0.15.0</li> <li><a href="https://github.com/causal-agent/scraper/commit/06f395efe0fb4e9c31cdbd81a9f9e41802572b33"><code>06f395e</code></a> Apply clippy suggestion</li> <li><a href="https://github.com/causal-agent/scraper/commit/ec91bf1ebc9921ca2adeddf93555081912c33334"><code>ec91bf1</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/102">#102</a> from jaboatman/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/4b7fb13446f5ab4400b1fdfb3092b71b3157af9a"><code>4b7fb13</code></a> Merge remote-tracking branch 'upstream/master'</li> <li><a href="https://github.com/causal-agent/scraper/commit/aa479ea170b7f2b463ccba85de0c802318d19abe"><code>aa479ea</code></a> perf(element): add one sweep element creation (<a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/109">#109</a>)</li> <li><a href="https://github.com/causal-agent/scraper/commit/9a6a638db208682593d83bef53c29052336c0487"><code>9a6a638</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/108">#108</a> from adamreichold/also-re-export-case-sensitivity</li> <li><a href="https://github.com/causal-agent/scraper/commit/794b5eef87aa1009a31d4d29093269a04e7d80fa"><code>794b5ee</code></a> Re-export selectors' CaseSensitivity enum as it is part of our public API.</li> <li><a href="https://github.com/causal-agent/scraper/commit/6abb8cd625af5ea4f5a59530f03436aa448f7c56"><code>6abb8cd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/107">#107</a> from j-mendez/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/c3dd2600dcd4c17424a307c2f82cfcab41943014"><code>c3dd260</code></a> chore(minor): fix element classes map format</li> <li><a href="https://github.com/causal-agent/scraper/commit/b7955b9049ccf5b685f53854d88cca322aa80bac"><code>b7955b9</code></a> perf(selectors): add lazy classes map</li> <li>Additional commits viewable in <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=scraper&package-manager=cargo&previous-version=0.14.0&new-version=0.15.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-06 04:37:22 +01:00
"itoa",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"ryu",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"serde",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
[[package]]
name = "csv-core"
Bump csv from 1.2.2 to 1.3.0 (#10733)
2023-10-18 23:01:14 +02:00
version = "0.1.11"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump csv from 1.2.2 to 1.3.0 (#10733)
2023-10-18 23:01:14 +02:00
checksum = "5efa2b3d7902f4b634a20cae3c9c4e6209dc4779feb6863329607560143efa70"
objectshell initial commit
2019-05-10 18:59:12 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"memchr",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Add initial ctrl-c support
2021-10-28 06:13:10 +02:00
[[package]]
name = "ctrlc"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "3.4.1"
Add initial ctrl-c support
2021-10-28 06:13:10 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "82e95fbd621905b854affdc67943b043a0fbb6ed7385fd5a25650d19a8a6cfdf"
Add initial ctrl-c support
2021-10-28 06:13:10 +02:00
dependencies = [
rename nushell's cp command to cp-old making coreutils the default cp (#10678) # Description This PR renames nushell's `cp` command to `cp-old` to make room for `ucp` to be renamed to `cp`, making the coreutils version of `cp` the default for nushell. After some period of time, we should remove `cp-old` entirely. # 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-10-11 01:13:28 +02:00
"nix",
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
"windows-sys 0.48.0",
Handle Ctrl-C gracefully
2019-06-07 02:31:22 +02:00
]
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
[[package]]
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
name = "dashmap"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "5.5.3"
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "978747c1d849a7d2ee5e8adc0159961c48fb7e5db2f06af6723b80123bb53856"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"hashbrown 0.14.3",
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
"lock_api",
"once_cell",
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
"parking_lot_core",
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
]
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
[[package]]
name = "deranged"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.3.10"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "8eb30d70a07a3b04884d2677f06bec33509dc67ca60d92949e5535352d3191dc"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
dependencies = [
"powerfmt",
]
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
Replace `clipboard` with `arboard` (#2832)
2020-12-30 18:16:02 +01:00
[[package]]
query command with json, web, xml (#870) * query command with json, web, xml * query xml now working * clippy * comment out web tests * Initial work on query web For now we can query everything except tables * Support for querying tables Now we can query multiple tables just like before, now the only thing missing is the test coverage * finish off * comment out web test Co-authored-by: Luccas Mateus de Medeiros Gomes <luccasmmg@gmail.com>
2022-02-01 19:45:48 +01:00
name = "derive_more"
version = "0.99.17"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4fb810d30a7c1953f91334de7244731fc3f3c10d7fe163338a35b9f640960321"
dependencies = [
"proc-macro2",
"quote",
Bump miette from 5.6.0 to 5.7.0 (#8720)
2023-04-06 22:39:54 +02:00
"syn 1.0.109",
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
]
Autoenv rewrite, security and scripting (#2083) * Add args in .nurc file to environment * Working dummy version * Add add_nurc to sync_env command * Parse .nurc file * Delete env vars after leaving directory * Removing vals not working, strangely * Refactoring, add comment * Debugging * Debug by logging to file * Add and remove env var behavior appears correct However, it does not use existing code that well. * Move work to cli.rs * Parse config directories * I am in a state of distress * Rename .nurc to .nu * Some notes for me * Refactoring * Removing vars works, but not done in a very nice fashion * Refactor env_vars_to_delete * Refactor env_vars_to_add() * Move directory environment code to separate file * Refactor from_config * Restore env values * Working? * Working? * Update comments and change var name * Formatting * Remove vars after leaving dir * Remove notes I made * Rename config function * Clippy * Cleanup and handle errors * cargo fmt * Better error messages, remove last (?) unwrap * FORMAT PLZ * Rename whitelisted_directories to allowed_directories * Add comment to clarify how overwritten values are restored. * Change list of allowed dirs to indexmap * Rewrite starting * rewrite everything * Overwritten env values tracks an indexmap instead of vector * Refactor restore function * Untrack removed vars properly * Performance concerns * Performance concerns * Error handling * Clippy * Add type aliases for String and OsString * Deletion almost works * Working? * Error handling and refactoring * nicer errors * Add TODO file * Move outside of loop * Error handling * Reworking adding of vars * Reworking adding of vars * Ready for testing * Refactoring * Restore overwritten vals code * todo.org * Remove overwritten values tracking, as it is not needed * Cleanup, stop tracking overwritten values as nu takes care of it * Init autoenv command * Initialize autoenv and autoenv trust * autoenv trust toml * toml * Use serde for autoenv * Optional directory arg * Add autoenv untrust command * ... actually add autoenv untrust this time * OsString and paths * Revert "OsString and paths" This reverts commit e6eedf882498c1365ecfc899e5ec11bd83cb055c. * Fix path * Fix path * Autoenv trust and untrust * Start using autoenv * Check hashes * Use trust functionality when setting vars * Remove unused code * Clippy * Nicer errors for autoenv commands * Non-working errors * Update error description * Satisfy fmt * Errors * Errors print, but not nicely * Nicer errors * fmt * Delete accidentally added todo.org file * Rename direnv to autoenv * Use ShellError instead of Error * Change tests to pass, danger zone? * Clippy and errors * Clippy... again * Replace match with or_else * Use sha2 crate for hashing * parsing and error msg * Refactoring * Only apply vars once * if parent dir * Delete vars * Rework exit code * Adding works * restore * Fix possibility of infinite loop * Refactoring * Non-working * Revert "Non-working" This reverts commit e231b85570bcb3fc838f950e9f5004c6a7c5a2ac. * Revert "Revert "Non-working"" This reverts commit 804092e46a752266576b044401cc97c317e41f21. * Autoenv trust works without restart * Cargo fix * Script vars * Serde * Serde errors * Entry and exitscripts * Clippy * Support windows and handle errors * Formatting * Fix infinite loop on windows * Debugging windows loop * More windows infinite loop debugging * Windows loop debugging #3 * windows loop #4 * Don't return err * Cleanup unused code * Infinite loop debug * Loop debugging * Check if infinite loop is vars_to_add * env_vars_to_add does not terminate, skip loop as test * Hypothesis: std::env::current_dir() is messing with something * Hypothesis: std::env::current_dir() is messing with something * plz * make clippy happy * debugging in env_vars_to_add * Debbuging env_vars_to_add #2 * clippy * clippy.. * Fool clippy * Fix another infinite loop * Binary search for error location x) * Binary search #3 * fmt * Binary search #4 * more searching... * closing in... maybe * PLZ * Cleanup * Restore commented out functionality * Handle case when user gives the directory "." * fmt * Use fs::canonicalize for paths * Create optional script section * fmt * Add exitscripts even if no entryscripts are defined * All sections in .nu-env are now optional * Re-read config file each directory change * Hot reload after autoenv untrust, don't run exitscripts if untrusted * Debugging * Fix issue with recursive adding of vars * Thank you for finding my issues Mr. Azure * use std::env
2020-07-05 19:34:00 +02:00
[[package]]
Try out select completions from dialoguer
2021-10-15 20:37:58 +02:00
name = "dialoguer"
Bump `dialoguer` to `0.11.0` (#10510) Includes fixes for breaking changes Supersedes #10494
2023-09-26 18:00:16 +02:00
version = "0.11.0"
Try out select completions from dialoguer
2021-10-15 20:37:58 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump `dialoguer` to `0.11.0` (#10510) Includes fixes for breaking changes Supersedes #10494
2023-09-26 18:00:16 +02:00
checksum = "658bce805d770f407bc62102fca7c2c64ceef2fbcb2b8bd19d2765ce093980de"
Try out select completions from dialoguer
2021-10-15 20:37:58 +02:00
dependencies = [
little cleanup
2021-10-15 20:51:25 +02:00
"console",
adds a list subcommand to input (interactive selections) (#8963) # Description Adds a subcommand `list` to `input` (can be migrated wherever if needed) that allows interactive single and multi selection from an input list. ![image](https://user-images.githubusercontent.com/7041726/236072161-5954dad9-8152-4752-ae3b-b21577711fd1.png) https://user-images.githubusercontent.com/7041726/233747242-1ca6c44b-e32c-48f1-8fa8-ae50f813be16.mp4 In case it's not clear, only the results are captured (for now the results are also printed to stderr next to the prompt) https://user-images.githubusercontent.com/7041726/233785814-f2c8c584-9dd4-4b26-9ae9-c819ed6aa954.mp4 # User-Facing Changes - Adds a new command `input list` # Tests + Formatting Not sure how we can test interactives any ideas? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-05-04 19:14:41 +02:00
"fuzzy-matcher",
Bump dialoguer from 0.9.0 to 0.10.3 (#7765)
2023-01-16 03:04:47 +01:00
"shell-words",
Bump `dialoguer` to `0.11.0` (#10510) Includes fixes for breaking changes Supersedes #10494
2023-09-26 18:00:16 +02:00
"thiserror",
Try out select completions from dialoguer
2021-10-15 20:37:58 +02:00
]
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
[[package]]
name = "diff"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
version = "0.1.13"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
checksum = "56254986775e3233ffa9c4d7d3faaf6d36a2c09d30b20687e9f88bc8bafc16c8"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
[[package]]
name = "difflib"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6184e33543162437515c2e2b48714794e37845ec9851711914eec9d308f6ebe8"
Bump some deps (#503)
2021-12-16 10:40:05 +01:00
[[package]]
Autoenv rewrite, security and scripting (#2083) * Add args in .nurc file to environment * Working dummy version * Add add_nurc to sync_env command * Parse .nurc file * Delete env vars after leaving directory * Removing vals not working, strangely * Refactoring, add comment * Debugging * Debug by logging to file * Add and remove env var behavior appears correct However, it does not use existing code that well. * Move work to cli.rs * Parse config directories * I am in a state of distress * Rename .nurc to .nu * Some notes for me * Refactoring * Removing vars works, but not done in a very nice fashion * Refactor env_vars_to_delete * Refactor env_vars_to_add() * Move directory environment code to separate file * Refactor from_config * Restore env values * Working? * Working? * Update comments and change var name * Formatting * Remove vars after leaving dir * Remove notes I made * Rename config function * Clippy * Cleanup and handle errors * cargo fmt * Better error messages, remove last (?) unwrap * FORMAT PLZ * Rename whitelisted_directories to allowed_directories * Add comment to clarify how overwritten values are restored. * Change list of allowed dirs to indexmap * Rewrite starting * rewrite everything * Overwritten env values tracks an indexmap instead of vector * Refactor restore function * Untrack removed vars properly * Performance concerns * Performance concerns * Error handling * Clippy * Add type aliases for String and OsString * Deletion almost works * Working? * Error handling and refactoring * nicer errors * Add TODO file * Move outside of loop * Error handling * Reworking adding of vars * Reworking adding of vars * Ready for testing * Refactoring * Restore overwritten vals code * todo.org * Remove overwritten values tracking, as it is not needed * Cleanup, stop tracking overwritten values as nu takes care of it * Init autoenv command * Initialize autoenv and autoenv trust * autoenv trust toml * toml * Use serde for autoenv * Optional directory arg * Add autoenv untrust command * ... actually add autoenv untrust this time * OsString and paths * Revert "OsString and paths" This reverts commit e6eedf882498c1365ecfc899e5ec11bd83cb055c. * Fix path * Fix path * Autoenv trust and untrust * Start using autoenv * Check hashes * Use trust functionality when setting vars * Remove unused code * Clippy * Nicer errors for autoenv commands * Non-working errors * Update error description * Satisfy fmt * Errors * Errors print, but not nicely * Nicer errors * fmt * Delete accidentally added todo.org file * Rename direnv to autoenv * Use ShellError instead of Error * Change tests to pass, danger zone? * Clippy and errors * Clippy... again * Replace match with or_else * Use sha2 crate for hashing * parsing and error msg * Refactoring * Only apply vars once * if parent dir * Delete vars * Rework exit code * Adding works * restore * Fix possibility of infinite loop * Refactoring * Non-working * Revert "Non-working" This reverts commit e231b85570bcb3fc838f950e9f5004c6a7c5a2ac. * Revert "Revert "Non-working"" This reverts commit 804092e46a752266576b044401cc97c317e41f21. * Autoenv trust works without restart * Cargo fix * Script vars * Serde * Serde errors * Entry and exitscripts * Clippy * Support windows and handle errors * Formatting * Fix infinite loop on windows * Debugging windows loop * More windows infinite loop debugging * Windows loop debugging #3 * windows loop #4 * Don't return err * Cleanup unused code * Infinite loop debug * Loop debugging * Check if infinite loop is vars_to_add * env_vars_to_add does not terminate, skip loop as test * Hypothesis: std::env::current_dir() is messing with something * Hypothesis: std::env::current_dir() is messing with something * plz * make clippy happy * debugging in env_vars_to_add * Debbuging env_vars_to_add #2 * clippy * clippy.. * Fool clippy * Fix another infinite loop * Binary search for error location x) * Binary search #3 * fmt * Binary search #4 * more searching... * closing in... maybe * PLZ * Cleanup * Restore commented out functionality * Handle case when user gives the directory "." * fmt * Use fs::canonicalize for paths * Create optional script section * fmt * Add exitscripts even if no entryscripts are defined * All sections in .nu-env are now optional * Re-read config file each directory change * Hot reload after autoenv untrust, don't run exitscripts if untrusted * Debugging * Fix issue with recursive adding of vars * Thank you for finding my issues Mr. Azure * use std::env
2020-07-05 19:34:00 +02:00
name = "digest"
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
version = "0.10.7"
Autoenv rewrite, security and scripting (#2083) * Add args in .nurc file to environment * Working dummy version * Add add_nurc to sync_env command * Parse .nurc file * Delete env vars after leaving directory * Removing vals not working, strangely * Refactoring, add comment * Debugging * Debug by logging to file * Add and remove env var behavior appears correct However, it does not use existing code that well. * Move work to cli.rs * Parse config directories * I am in a state of distress * Rename .nurc to .nu * Some notes for me * Refactoring * Removing vars works, but not done in a very nice fashion * Refactor env_vars_to_delete * Refactor env_vars_to_add() * Move directory environment code to separate file * Refactor from_config * Restore env values * Working? * Working? * Update comments and change var name * Formatting * Remove vars after leaving dir * Remove notes I made * Rename config function * Clippy * Cleanup and handle errors * cargo fmt * Better error messages, remove last (?) unwrap * FORMAT PLZ * Rename whitelisted_directories to allowed_directories * Add comment to clarify how overwritten values are restored. * Change list of allowed dirs to indexmap * Rewrite starting * rewrite everything * Overwritten env values tracks an indexmap instead of vector * Refactor restore function * Untrack removed vars properly * Performance concerns * Performance concerns * Error handling * Clippy * Add type aliases for String and OsString * Deletion almost works * Working? * Error handling and refactoring * nicer errors * Add TODO file * Move outside of loop * Error handling * Reworking adding of vars * Reworking adding of vars * Ready for testing * Refactoring * Restore overwritten vals code * todo.org * Remove overwritten values tracking, as it is not needed * Cleanup, stop tracking overwritten values as nu takes care of it * Init autoenv command * Initialize autoenv and autoenv trust * autoenv trust toml * toml * Use serde for autoenv * Optional directory arg * Add autoenv untrust command * ... actually add autoenv untrust this time * OsString and paths * Revert "OsString and paths" This reverts commit e6eedf882498c1365ecfc899e5ec11bd83cb055c. * Fix path * Fix path * Autoenv trust and untrust * Start using autoenv * Check hashes * Use trust functionality when setting vars * Remove unused code * Clippy * Nicer errors for autoenv commands * Non-working errors * Update error description * Satisfy fmt * Errors * Errors print, but not nicely * Nicer errors * fmt * Delete accidentally added todo.org file * Rename direnv to autoenv * Use ShellError instead of Error * Change tests to pass, danger zone? * Clippy and errors * Clippy... again * Replace match with or_else * Use sha2 crate for hashing * parsing and error msg * Refactoring * Only apply vars once * if parent dir * Delete vars * Rework exit code * Adding works * restore * Fix possibility of infinite loop * Refactoring * Non-working * Revert "Non-working" This reverts commit e231b85570bcb3fc838f950e9f5004c6a7c5a2ac. * Revert "Revert "Non-working"" This reverts commit 804092e46a752266576b044401cc97c317e41f21. * Autoenv trust works without restart * Cargo fix * Script vars * Serde * Serde errors * Entry and exitscripts * Clippy * Support windows and handle errors * Formatting * Fix infinite loop on windows * Debugging windows loop * More windows infinite loop debugging * Windows loop debugging #3 * windows loop #4 * Don't return err * Cleanup unused code * Infinite loop debug * Loop debugging * Check if infinite loop is vars_to_add * env_vars_to_add does not terminate, skip loop as test * Hypothesis: std::env::current_dir() is messing with something * Hypothesis: std::env::current_dir() is messing with something * plz * make clippy happy * debugging in env_vars_to_add * Debbuging env_vars_to_add #2 * clippy * clippy.. * Fool clippy * Fix another infinite loop * Binary search for error location x) * Binary search #3 * fmt * Binary search #4 * more searching... * closing in... maybe * PLZ * Cleanup * Restore commented out functionality * Handle case when user gives the directory "." * fmt * Use fs::canonicalize for paths * Create optional script section * fmt * Add exitscripts even if no entryscripts are defined * All sections in .nu-env are now optional * Re-read config file each directory change * Hot reload after autoenv untrust, don't run exitscripts if untrusted * Debugging * Fix issue with recursive adding of vars * Thank you for finding my issues Mr. Azure * use std::env
2020-07-05 19:34:00 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
checksum = "9ed9a281f7bc9b7576e61468ba615a66a5c8cfdff42420a70aa82701a3b1e292"
Autoenv rewrite, security and scripting (#2083) * Add args in .nurc file to environment * Working dummy version * Add add_nurc to sync_env command * Parse .nurc file * Delete env vars after leaving directory * Removing vals not working, strangely * Refactoring, add comment * Debugging * Debug by logging to file * Add and remove env var behavior appears correct However, it does not use existing code that well. * Move work to cli.rs * Parse config directories * I am in a state of distress * Rename .nurc to .nu * Some notes for me * Refactoring * Removing vars works, but not done in a very nice fashion * Refactor env_vars_to_delete * Refactor env_vars_to_add() * Move directory environment code to separate file * Refactor from_config * Restore env values * Working? * Working? * Update comments and change var name * Formatting * Remove vars after leaving dir * Remove notes I made * Rename config function * Clippy * Cleanup and handle errors * cargo fmt * Better error messages, remove last (?) unwrap * FORMAT PLZ * Rename whitelisted_directories to allowed_directories * Add comment to clarify how overwritten values are restored. * Change list of allowed dirs to indexmap * Rewrite starting * rewrite everything * Overwritten env values tracks an indexmap instead of vector * Refactor restore function * Untrack removed vars properly * Performance concerns * Performance concerns * Error handling * Clippy * Add type aliases for String and OsString * Deletion almost works * Working? * Error handling and refactoring * nicer errors * Add TODO file * Move outside of loop * Error handling * Reworking adding of vars * Reworking adding of vars * Ready for testing * Refactoring * Restore overwritten vals code * todo.org * Remove overwritten values tracking, as it is not needed * Cleanup, stop tracking overwritten values as nu takes care of it * Init autoenv command * Initialize autoenv and autoenv trust * autoenv trust toml * toml * Use serde for autoenv * Optional directory arg * Add autoenv untrust command * ... actually add autoenv untrust this time * OsString and paths * Revert "OsString and paths" This reverts commit e6eedf882498c1365ecfc899e5ec11bd83cb055c. * Fix path * Fix path * Autoenv trust and untrust * Start using autoenv * Check hashes * Use trust functionality when setting vars * Remove unused code * Clippy * Nicer errors for autoenv commands * Non-working errors * Update error description * Satisfy fmt * Errors * Errors print, but not nicely * Nicer errors * fmt * Delete accidentally added todo.org file * Rename direnv to autoenv * Use ShellError instead of Error * Change tests to pass, danger zone? * Clippy and errors * Clippy... again * Replace match with or_else * Use sha2 crate for hashing * parsing and error msg * Refactoring * Only apply vars once * if parent dir * Delete vars * Rework exit code * Adding works * restore * Fix possibility of infinite loop * Refactoring * Non-working * Revert "Non-working" This reverts commit e231b85570bcb3fc838f950e9f5004c6a7c5a2ac. * Revert "Revert "Non-working"" This reverts commit 804092e46a752266576b044401cc97c317e41f21. * Autoenv trust works without restart * Cargo fix * Script vars * Serde * Serde errors * Entry and exitscripts * Clippy * Support windows and handle errors * Formatting * Fix infinite loop on windows * Debugging windows loop * More windows infinite loop debugging * Windows loop debugging #3 * windows loop #4 * Don't return err * Cleanup unused code * Infinite loop debug * Loop debugging * Check if infinite loop is vars_to_add * env_vars_to_add does not terminate, skip loop as test * Hypothesis: std::env::current_dir() is messing with something * Hypothesis: std::env::current_dir() is messing with something * plz * make clippy happy * debugging in env_vars_to_add * Debbuging env_vars_to_add #2 * clippy * clippy.. * Fool clippy * Fix another infinite loop * Binary search for error location x) * Binary search #3 * fmt * Binary search #4 * more searching... * closing in... maybe * PLZ * Cleanup * Restore commented out functionality * Handle case when user gives the directory "." * fmt * Use fs::canonicalize for paths * Create optional script section * fmt * Add exitscripts even if no entryscripts are defined * All sections in .nu-env are now optional * Re-read config file each directory change * Hot reload after autoenv untrust, don't run exitscripts if untrusted * Debugging * Fix issue with recursive adding of vars * Thank you for finding my issues Mr. Azure * use std::env
2020-07-05 19:34:00 +02:00
dependencies = [
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
"block-buffer",
Port `hash`, `hash md5` and `hash sha256` commands (#464) `hash` by itself is only printing the help message. The other two are simply using the same generic implementation.
2021-12-11 00:14:28 +01:00
"crypto-common",
Use the directories crate instead of app_dirs (#1782) The app_dirs crate is abandonned since quite a bit of time. Use the directories crate instead, which is maintained and have more OS support.
2020-05-14 10:17:23 +02:00
]
updated dependencies (#2857) Same as #2786 Co-authored-by: sousajo <sousajo@pop-os.localdomain> Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-07 01:38:22 +01:00
[[package]]
name = "dirs-next"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b98cf8ebf19c3d1b223e151f99a4f9f0690dca41414773390fc824184ac833e1"
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
updated dependencies (#2857) Same as #2786 Co-authored-by: sousajo <sousajo@pop-os.localdomain> Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-07 01:38:22 +01:00
"dirs-sys-next",
]
Revert "Bump Rustyline to 7.0.0 (#2776)" (#2778) This reverts commit e73278990c66fdd49c263b5533773f2ef62d4f7e.
2020-12-05 05:12:42 +01:00
[[package]]
name = "dirs-sys-next"
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
version = "0.1.2"
Revert "Bump Rustyline to 7.0.0 (#2776)" (#2778) This reverts commit e73278990c66fdd49c263b5533773f2ef62d4f7e.
2020-12-05 05:12:42 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
checksum = "4ebda144c4fe02d1f7ea1a7d9641b6fc6b580adcfa024ae48797ecdeb6825b4d"
Revert "Bump Rustyline to 7.0.0 (#2776)" (#2778) This reverts commit e73278990c66fdd49c263b5533773f2ef62d4f7e.
2020-12-05 05:12:42 +01:00
dependencies = [
"libc",
Polars update (#4875) * update to polars 0.20 * add to date parser for series
2022-03-19 12:13:34 +01:00
"redox_users",
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"winapi",
Revert "Bump Rustyline to 7.0.0 (#2776)" (#2778) This reverts commit e73278990c66fdd49c263b5533773f2ef62d4f7e.
2020-12-05 05:12:42 +01:00
]
Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from (#8009) # Description Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from # Tests + Formatting Added a test to support addition of the rust-ini crate. `cargo test --package nu-command --lib -- formats::from::ini::tests --nocapture` Executed all tests. `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-09 12:47:45 +01:00
[[package]]
name = "dlv-list"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.5.2"
Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from (#8009) # Description Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from # Tests + Formatting Added a test to support addition of the rust-ini crate. `cargo test --package nu-command --lib -- formats::from::ini::tests --nocapture` Executed all tests. `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-09 12:47:45 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "442039f5147480ba31067cb00ada1adae6892028e40e45fc5de7b7df6dcc1b5f"
update ini dependency (#9426) # Description This PR updates the ini dependency. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 20:33:00 +02:00
dependencies = [
"const-random",
]
Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from (#8009) # Description Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from # Tests + Formatting Added a test to support addition of the rust-ini crate. `cargo test --package nu-command --lib -- formats::from::ini::tests --nocapture` Executed all tests. `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-09 12:47:45 +01:00
Temporarily(?) switch from heim+uom to sysinfo (#2954) * Switch from heim to sysinfo * WIP * more cleanup * fmt * lint
2021-01-20 08:18:38 +01:00
[[package]]
name = "doc-comment"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fea41bba32d969b513997752735605054bc0dfa92b4c56bf1189f2e174be7a10"
Lots of misc improvements
2019-06-03 09:41:28 +02:00
[[package]]
name = "dtoa"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.0.9"
Lots of misc improvements
2019-06-03 09:41:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "dcbb2bf8e87535c23f7a8a321e364ce21462d0ff10cb6407820e8e96dfff6653"
Lots of misc improvements
2019-06-03 09:41:28 +02:00
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
[[package]]
name = "dtoa-short"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.3.4"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "dbaceec3c6e4211c79e7b1800fb9680527106beb2f9c51904a3210c03a448c74"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
dependencies = [
"dtoa",
]
removed rustyline config duplication (#2306) * removed rustyline config duplication set other rustyline defaults if line_editor section doesn't exist updated keyseq_timeout to -1 if emacs mode is chosen * change checking rustyline config to if lets * removed some unneccessary code
2020-08-05 23:34:28 +02:00
[[package]]
name = "dtparse"
Don't use `oldtime` feature of chrono (#9577) <!-- 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 `chrono` crate enables `oldtime` feature by default, which has a vulnerability (https://rustsec.org/advisories/RUSTSEC-2020-0071). This PR tries to remove `time` v0.1.45 completely from nu and add an audit CI to check for security vulnerabilities. :hand: Wait for the following PRs: - [x] https://github.com/nushell/reedline/pull/599 - [x] https://github.com/bspeice/dtparse/pull/44 - [x] https://github.com/Byron/trash-rs/pull/75 - [x] https://gitlab.com/imp/chrono-humanize-rs/-/merge_requests/15 # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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. --> --------- Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-25 10:54:01 +02:00
version = "2.0.0"
removed rustyline config duplication (#2306) * removed rustyline config duplication set other rustyline defaults if line_editor section doesn't exist updated keyseq_timeout to -1 if emacs mode is chosen * change checking rustyline config to if lets * removed some unneccessary code
2020-08-05 23:34:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Don't use `oldtime` feature of chrono (#9577) <!-- 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 `chrono` crate enables `oldtime` feature by default, which has a vulnerability (https://rustsec.org/advisories/RUSTSEC-2020-0071). This PR tries to remove `time` v0.1.45 completely from nu and add an audit CI to check for security vulnerabilities. :hand: Wait for the following PRs: - [x] https://github.com/nushell/reedline/pull/599 - [x] https://github.com/bspeice/dtparse/pull/44 - [x] https://github.com/Byron/trash-rs/pull/75 - [x] https://gitlab.com/imp/chrono-humanize-rs/-/merge_requests/15 # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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. --> --------- Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-25 10:54:01 +02:00
checksum = "458c7cfe1c34b1ef7c2c435076064711050aedabae9952a261687c500f80e839"
removed rustyline config duplication (#2306) * removed rustyline config duplication set other rustyline defaults if line_editor section doesn't exist updated keyseq_timeout to -1 if emacs mode is chosen * change checking rustyline config to if lets * removed some unneccessary code
2020-08-05 23:34:28 +02:00
dependencies = [
"chrono",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"lazy_static",
"num-traits",
removed rustyline config duplication (#2306) * removed rustyline config duplication set other rustyline defaults if line_editor section doesn't exist updated keyseq_timeout to -1 if emacs mode is chosen * change checking rustyline config to if lets * removed some unneccessary code
2020-08-05 23:34:28 +02:00
"rust_decimal",
]
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
[[package]]
name = "dunce"
version = "1.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "56ce8c6da7551ec6c462cbaf3bfbc75131ebbfa1c944aeaa9dab51ca1c5f0c3b"
Polars upgrade 0.23 (#6303) * more lazy expressions * upgrade polars and correct functions * arg-where example * cargo clippy * restore modified filter files * correct string addition with str * correct string addition with str * correct message in test
2022-08-12 14:10:36 +02:00
[[package]]
name = "dyn-clone"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "1.0.16"
Polars upgrade 0.23 (#6303) * more lazy expressions * upgrade polars and correct functions * arg-where example * cargo clippy * restore modified filter files * correct string addition with str * correct string addition with str * correct message in test
2022-08-12 14:10:36 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "545b22097d44f8a9581187cdf93de7a71e4722bf51200cfaba810865b49a495d"
Polars upgrade 0.23 (#6303) * more lazy expressions * upgrade polars and correct functions * arg-where example * cargo clippy * restore modified filter files * correct string addition with str * correct string addition with str * correct message in test
2022-08-12 14:10:36 +02:00
Update some deps (#3011)
2021-02-05 21:54:54 +01:00
[[package]]
add table selector for downloading web tables (#4004) * add table selector for downloading web tables * type-o * updated debug mode to inspect mode
2021-09-16 16:02:30 +02:00
name = "ego-tree"
version = "0.6.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3a68a4904193147e0a8dec3314640e6db742afd5f6e634f428a6af230d9b3591"
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "either"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.9.0"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "a26ae43d7bcc3b814de94796a5e736d4029efb0ee900c12e2d54c993ad1a1e07"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
Add not-in: operator (#1661)
2020-04-26 07:32:17 +02:00
[[package]]
name = "eml-parser"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.1.4"
Add not-in: operator (#1661)
2020-04-26 07:32:17 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "a7db8d15f812e08f76427c555195583e3ab8a99fd8b208f8d9e2899262e80f2e"
Add not-in: operator (#1661)
2020-04-26 07:32:17 +02:00
dependencies = [
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"regex",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"rfc2047-decoder",
Add not-in: operator (#1661)
2020-04-26 07:32:17 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "encode_unicode"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.3.6"
Add a bunch more tokens and delimited ()
2019-06-12 19:44:45 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
checksum = "a357d28ed41a50f9c765dbfe56cbc04a64e53e5fc58ba79fbc34c10ef3df831f"
Add a bunch more tokens and delimited ()
2019-06-12 19:44:45 +02:00
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
[[package]]
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
name = "encoding_rs"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.8.33"
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "7268b386296a025e474d5140678f75d6de9493ae55a5d709eeb9dd08149945e1"
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
]
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
[[package]]
name = "enum_dispatch"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.3.12"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "8f33313078bb8d4d05a2733a94ac4c2d8a0df9a2b84424ebf4f33bfc224a890e"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
dependencies = [
"once_cell",
"proc-macro2",
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
]
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
[[package]]
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
name = "env_logger"
version = "0.8.4"
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
checksum = "a19187fea3ac7e84da7dacf48de0c45d63c6a76f9490dae389aead16c243fce3"
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
dependencies = [
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
"log",
"regex",
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
]
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
[[package]]
name = "equivalent"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.0.1"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "5443807d6dff69373d433ab9ef5378ad8df50ca6298caf15de6e52e24aaf54d5"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
[[package]]
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
name = "erased-serde"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "0.4.0"
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "a3286168faae03a0e583f6fde17c02c8b8bba2dcc2061d0f7817066e5b0af706"
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
dependencies = [
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
"serde",
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
]
Bump errno from 0.2.8 to 0.3.0 (#8131) Bumps [errno](https://github.com/lambda-fairy/rust-errno) from 0.2.8 to 0.3.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/lambda-fairy/rust-errno/blob/main/CHANGELOG.md">errno's changelog</a>.</em></p> <blockquote> <h1>[0.3.0] - 2023-02-12</h1> <ul> <li> <p>Add haiku support <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/42">#42</a></p> </li> <li> <p>Add AIX support <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/54">#54</a></p> </li> <li> <p>Add formatting with <code>#![no_std]</code> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/44">#44</a></p> </li> <li> <p>Switch from <code>winapi</code> to <code>windows-sys</code> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/55">#55</a></p> </li> <li> <p>Update minimum Rust version to 1.48 <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/48">#48</a> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/55">#55</a></p> </li> <li> <p>Upgrade to Rust 2018 edition <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/59">#59</a></p> </li> <li> <p>wasm32-wasi: Use <code>__errno_location</code> instead of <code>feature(thread_local)</code>. <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/66">#66</a></p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/e1882701f6d21bd9f45c2941a85416c59fa019ac"><code>e188270</code></a> Release 0.3.0</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/3983d26f982014d083bf58ac9dafa69805c458ca"><code>3983d26</code></a> Add <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/66">#66</a> to changelog</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/362d7c6c358d82e19182fb46ebb0b23beeb50713"><code>362d7c6</code></a> Update windows-sys requirement from 0.42 to 0.45 (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/67">#67</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/b8cc39bb8de7194d64f52d762310a113a998048d"><code>b8cc39b</code></a> wasm32-wasi: Use <code>__errno_location</code> instead of <code>feature(thread_local)</code>. (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/66">#66</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/dbd02cf02f6cb81bcf93e1b754167b59c0996b9a"><code>dbd02cf</code></a> Replace deprecated <code>trim_right</code> with <code>trim_end</code> (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/65">#65</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/c999f38356ce5c291296ab2e09ea584df45d2a9b"><code>c999f38</code></a> Add comparison with <code>std::io::Error</code></li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/8a4c62af22f85c7f0214e6e6bdc710edf67d0088"><code>8a4c62a</code></a> Bump actions/checkout from 2 to 3 (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/64">#64</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/04379ae703bc48c4a3fdf51be748cbddbf565b8c"><code>04379ae</code></a> Add Dependabot (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/63">#63</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/18e34d3895840a82a074b41bd0029385fddb6e5c"><code>18e34d3</code></a> Setup caching for CI</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/81c3ba4cba053185cc02f51c12650e86f3bb2fc8"><code>81c3ba4</code></a> Run clippy in CI</li> <li>Additional commits viewable in <a href="https://github.com/lambda-fairy/rust-errno/compare/v0.2.8...v0.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=errno&package-manager=cargo&previous-version=0.2.8&new-version=0.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-22 13:56:31 +01:00
[[package]]
name = "errno"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.3.8"
Bump errno from 0.2.8 to 0.3.0 (#8131) Bumps [errno](https://github.com/lambda-fairy/rust-errno) from 0.2.8 to 0.3.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/lambda-fairy/rust-errno/blob/main/CHANGELOG.md">errno's changelog</a>.</em></p> <blockquote> <h1>[0.3.0] - 2023-02-12</h1> <ul> <li> <p>Add haiku support <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/42">#42</a></p> </li> <li> <p>Add AIX support <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/54">#54</a></p> </li> <li> <p>Add formatting with <code>#![no_std]</code> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/44">#44</a></p> </li> <li> <p>Switch from <code>winapi</code> to <code>windows-sys</code> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/55">#55</a></p> </li> <li> <p>Update minimum Rust version to 1.48 <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/48">#48</a> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/55">#55</a></p> </li> <li> <p>Upgrade to Rust 2018 edition <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/59">#59</a></p> </li> <li> <p>wasm32-wasi: Use <code>__errno_location</code> instead of <code>feature(thread_local)</code>. <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/66">#66</a></p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/e1882701f6d21bd9f45c2941a85416c59fa019ac"><code>e188270</code></a> Release 0.3.0</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/3983d26f982014d083bf58ac9dafa69805c458ca"><code>3983d26</code></a> Add <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/66">#66</a> to changelog</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/362d7c6c358d82e19182fb46ebb0b23beeb50713"><code>362d7c6</code></a> Update windows-sys requirement from 0.42 to 0.45 (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/67">#67</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/b8cc39bb8de7194d64f52d762310a113a998048d"><code>b8cc39b</code></a> wasm32-wasi: Use <code>__errno_location</code> instead of <code>feature(thread_local)</code>. (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/66">#66</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/dbd02cf02f6cb81bcf93e1b754167b59c0996b9a"><code>dbd02cf</code></a> Replace deprecated <code>trim_right</code> with <code>trim_end</code> (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/65">#65</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/c999f38356ce5c291296ab2e09ea584df45d2a9b"><code>c999f38</code></a> Add comparison with <code>std::io::Error</code></li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/8a4c62af22f85c7f0214e6e6bdc710edf67d0088"><code>8a4c62a</code></a> Bump actions/checkout from 2 to 3 (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/64">#64</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/04379ae703bc48c4a3fdf51be748cbddbf565b8c"><code>04379ae</code></a> Add Dependabot (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/63">#63</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/18e34d3895840a82a074b41bd0029385fddb6e5c"><code>18e34d3</code></a> Setup caching for CI</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/81c3ba4cba053185cc02f51c12650e86f3bb2fc8"><code>81c3ba4</code></a> Run clippy in CI</li> <li>Additional commits viewable in <a href="https://github.com/lambda-fairy/rust-errno/compare/v0.2.8...v0.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=errno&package-manager=cargo&previous-version=0.2.8&new-version=0.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-22 13:56:31 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "a258e46cdc063eb8519c00b9fc845fc47bcfca4130e2f08e88665ceda8474245"
Bump errno from 0.2.8 to 0.3.0 (#8131) Bumps [errno](https://github.com/lambda-fairy/rust-errno) from 0.2.8 to 0.3.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/lambda-fairy/rust-errno/blob/main/CHANGELOG.md">errno's changelog</a>.</em></p> <blockquote> <h1>[0.3.0] - 2023-02-12</h1> <ul> <li> <p>Add haiku support <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/42">#42</a></p> </li> <li> <p>Add AIX support <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/54">#54</a></p> </li> <li> <p>Add formatting with <code>#![no_std]</code> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/44">#44</a></p> </li> <li> <p>Switch from <code>winapi</code> to <code>windows-sys</code> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/55">#55</a></p> </li> <li> <p>Update minimum Rust version to 1.48 <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/48">#48</a> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/55">#55</a></p> </li> <li> <p>Upgrade to Rust 2018 edition <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/59">#59</a></p> </li> <li> <p>wasm32-wasi: Use <code>__errno_location</code> instead of <code>feature(thread_local)</code>. <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/66">#66</a></p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/e1882701f6d21bd9f45c2941a85416c59fa019ac"><code>e188270</code></a> Release 0.3.0</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/3983d26f982014d083bf58ac9dafa69805c458ca"><code>3983d26</code></a> Add <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/66">#66</a> to changelog</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/362d7c6c358d82e19182fb46ebb0b23beeb50713"><code>362d7c6</code></a> Update windows-sys requirement from 0.42 to 0.45 (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/67">#67</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/b8cc39bb8de7194d64f52d762310a113a998048d"><code>b8cc39b</code></a> wasm32-wasi: Use <code>__errno_location</code> instead of <code>feature(thread_local)</code>. (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/66">#66</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/dbd02cf02f6cb81bcf93e1b754167b59c0996b9a"><code>dbd02cf</code></a> Replace deprecated <code>trim_right</code> with <code>trim_end</code> (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/65">#65</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/c999f38356ce5c291296ab2e09ea584df45d2a9b"><code>c999f38</code></a> Add comparison with <code>std::io::Error</code></li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/8a4c62af22f85c7f0214e6e6bdc710edf67d0088"><code>8a4c62a</code></a> Bump actions/checkout from 2 to 3 (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/64">#64</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/04379ae703bc48c4a3fdf51be748cbddbf565b8c"><code>04379ae</code></a> Add Dependabot (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/63">#63</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/18e34d3895840a82a074b41bd0029385fddb6e5c"><code>18e34d3</code></a> Setup caching for CI</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/81c3ba4cba053185cc02f51c12650e86f3bb2fc8"><code>81c3ba4</code></a> Run clippy in CI</li> <li>Additional commits viewable in <a href="https://github.com/lambda-fairy/rust-errno/compare/v0.2.8...v0.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=errno&package-manager=cargo&previous-version=0.2.8&new-version=0.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-22 13:56:31 +01:00
dependencies = [
"libc",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"windows-sys 0.52.0",
Bump errno from 0.2.8 to 0.3.0 (#8131) Bumps [errno](https://github.com/lambda-fairy/rust-errno) from 0.2.8 to 0.3.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/lambda-fairy/rust-errno/blob/main/CHANGELOG.md">errno's changelog</a>.</em></p> <blockquote> <h1>[0.3.0] - 2023-02-12</h1> <ul> <li> <p>Add haiku support <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/42">#42</a></p> </li> <li> <p>Add AIX support <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/54">#54</a></p> </li> <li> <p>Add formatting with <code>#![no_std]</code> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/44">#44</a></p> </li> <li> <p>Switch from <code>winapi</code> to <code>windows-sys</code> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/55">#55</a></p> </li> <li> <p>Update minimum Rust version to 1.48 <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/48">#48</a> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/55">#55</a></p> </li> <li> <p>Upgrade to Rust 2018 edition <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/59">#59</a></p> </li> <li> <p>wasm32-wasi: Use <code>__errno_location</code> instead of <code>feature(thread_local)</code>. <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/66">#66</a></p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/e1882701f6d21bd9f45c2941a85416c59fa019ac"><code>e188270</code></a> Release 0.3.0</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/3983d26f982014d083bf58ac9dafa69805c458ca"><code>3983d26</code></a> Add <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/66">#66</a> to changelog</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/362d7c6c358d82e19182fb46ebb0b23beeb50713"><code>362d7c6</code></a> Update windows-sys requirement from 0.42 to 0.45 (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/67">#67</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/b8cc39bb8de7194d64f52d762310a113a998048d"><code>b8cc39b</code></a> wasm32-wasi: Use <code>__errno_location</code> instead of <code>feature(thread_local)</code>. (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/66">#66</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/dbd02cf02f6cb81bcf93e1b754167b59c0996b9a"><code>dbd02cf</code></a> Replace deprecated <code>trim_right</code> with <code>trim_end</code> (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/65">#65</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/c999f38356ce5c291296ab2e09ea584df45d2a9b"><code>c999f38</code></a> Add comparison with <code>std::io::Error</code></li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/8a4c62af22f85c7f0214e6e6bdc710edf67d0088"><code>8a4c62a</code></a> Bump actions/checkout from 2 to 3 (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/64">#64</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/04379ae703bc48c4a3fdf51be748cbddbf565b8c"><code>04379ae</code></a> Add Dependabot (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/63">#63</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/18e34d3895840a82a074b41bd0029385fddb6e5c"><code>18e34d3</code></a> Setup caching for CI</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/81c3ba4cba053185cc02f51c12650e86f3bb2fc8"><code>81c3ba4</code></a> Run clippy in CI</li> <li>Additional commits viewable in <a href="https://github.com/lambda-fairy/rust-errno/compare/v0.2.8...v0.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=errno&package-manager=cargo&previous-version=0.2.8&new-version=0.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-22 13:56:31 +01:00
]
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
[[package]]
name = "ethnum"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "1.5.0"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "b90ca2580b73ab6a1f724b76ca11ab632df820fd6040c336200d2c1df7b3c82c"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
Initial SQLite functionality (#5182) * Add SQLite functionality to open * Add in-memory SQLite tests * clippy fixes * Fix up old SQLite-related tests
2022-04-14 05:15:02 +02:00
[[package]]
name = "fallible-iterator"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4443176a9f2c162692bd3d352d745ef9413eec5782a80d8fd6f8a1ac692a07f7"
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
[[package]]
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
name = "fallible-streaming-iterator"
version = "0.1.9"
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
checksum = "7360491ce676a36bf9bb3c56c1aa791658183a54d2744120f27285738d90465a"
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "fancy-regex"
version = "0.12.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7493d4c459da9f84325ad297371a6b2b8a162800873a22e3b6b6512e61d18c05"
dependencies = [
"bit-set",
"regex",
]
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
[[package]]
name = "fast-float"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "95765f67b4b18863968b4a1bd5bb576f732b29a4a28c7cd84c09fa3e2875f33c"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
[[package]]
merge main
2022-02-08 14:28:21 +01:00
name = "fastrand"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "2.0.1"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "25cbce373ec4653f1a01a31e8a5e5ec0c622dc27ff9c4e6606eefef5cbbed4a5"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
[[package]]
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
name = "fd-lock"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "3.0.13"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "ef033ed5e9bad94e55838ca0ca906db0e043f517adda0c8b79c7a8c66c93c1b5"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"rustix 0.38.28",
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
"windows-sys 0.48.0",
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
]
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
[[package]]
name = "file-id"
Bump notify-debouncer-full from 0.2.0 to 0.3.1 (#10129)
2023-09-01 00:07:41 +02:00
version = "0.2.1"
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump notify-debouncer-full from 0.2.0 to 0.3.1 (#10129)
2023-09-01 00:07:41 +02:00
checksum = "6584280525fb2059cba3db2c04abf947a1a29a45ddae89f3870f8281704fafc9"
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
dependencies = [
Bump notify-debouncer-full from 0.2.0 to 0.3.1 (#10129)
2023-09-01 00:07:41 +02:00
"windows-sys 0.48.0",
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
]
imp: bump rustyline to 8.0.0 (#3167) * imp: bump rustyline to 8.0.0 * fix: rustyline 8 keybindings * fix: commands count/length test Co-authored-by: alexhk <alexhk@protonmail.com>
2021-03-14 03:13:31 +01:00
[[package]]
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
name = "filesize"
version = "0.2.0"
Add block size to du (#1341) * Add block size to du * Change blocks to physical size * Use path instead of strings for file/directory names * Why don't I just use paths instead of strings anyway? * shorten physical size and apparent size to physical and apparent resp.
2020-02-10 21:32:18 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump a lot of deps (#1560)
2020-04-07 09:51:17 +02:00
checksum = "12d741e2415d4e2e5bd1c1d00409d1a8865a57892c2d689b504365655d237d43"
Add block size to du (#1341) * Add block size to du * Change blocks to physical size * Use path instead of strings for file/directory names * Why don't I just use paths instead of strings anyway? * shorten physical size and apparent size to physical and apparent resp.
2020-02-10 21:32:18 +01:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"winapi",
Add block size to du (#1341) * Add block size to du * Change blocks to physical size * Use path instead of strings for file/directory names * Why don't I just use paths instead of strings anyway? * shorten physical size and apparent size to physical and apparent resp.
2020-02-10 21:32:18 +01:00
]
Implement rest of `touch` flags (#5119) * Add timestamp flag to `touch` command * Add modify flag to `touch` command * Add date flag to `touch` command * Remove unnecessary `touch` test and fix tests setups * Change `touch` flags descriptions * Update `touch` example * Add reference flag to `touch` command * Add access flag to `touch` command * Add no-create flag to `touch` command * Replace `unwrap` with `expect`
2022-04-07 13:44:05 +02:00
[[package]]
name = "filetime"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.2.23"
Implement rest of `touch` flags (#5119) * Add timestamp flag to `touch` command * Add modify flag to `touch` command * Add date flag to `touch` command * Remove unnecessary `touch` test and fix tests setups * Change `touch` flags descriptions * Update `touch` example * Add reference flag to `touch` command * Add access flag to `touch` command * Add no-create flag to `touch` command * Replace `unwrap` with `expect`
2022-04-07 13:44:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "1ee447700ac8aa0b2f2bd7bc4462ad686ba06baa6727ac149a2d6277f0d240fd"
Implement rest of `touch` flags (#5119) * Add timestamp flag to `touch` command * Add modify flag to `touch` command * Add date flag to `touch` command * Remove unnecessary `touch` test and fix tests setups * Change `touch` flags descriptions * Update `touch` example * Add reference flag to `touch` command * Add access flag to `touch` command * Add no-create flag to `touch` command * Replace `unwrap` with `expect`
2022-04-07 13:44:05 +02:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Implement rest of `touch` flags (#5119) * Add timestamp flag to `touch` command * Add modify flag to `touch` command * Add date flag to `touch` command * Remove unnecessary `touch` test and fix tests setups * Change `touch` flags descriptions * Update `touch` example * Add reference flag to `touch` command * Add access flag to `touch` command * Add no-create flag to `touch` command * Replace `unwrap` with `expect`
2022-04-07 13:44:05 +02:00
"libc",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"redox_syscall",
"windows-sys 0.52.0",
Implement rest of `touch` flags (#5119) * Add timestamp flag to `touch` command * Add modify flag to `touch` command * Add date flag to `touch` command * Remove unnecessary `touch` test and fix tests setups * Change `touch` flags descriptions * Update `touch` example * Add reference flag to `touch` command * Add access flag to `touch` command * Add no-create flag to `touch` command * Replace `unwrap` with `expect`
2022-04-07 13:44:05 +02:00
]
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "flate2"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "1.0.28"
Bat
2019-05-18 03:24:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "46303f565772937ffe1d394a4fac6f411c6013172fadde9dcdb1e147a086940e"
Bat
2019-05-18 03:24:13 +02:00
dependencies = [
`from xlsx` `from ods` and `from toml` (#352) * MathEval Variance and Stddev * Fix tests and linting * Typo * Deal with streams when they are not tables * `from toml` command * From ods * From XLSX
2021-11-19 20:23:35 +01:00
"crc32fast",
cargo update (#5639)
2022-05-25 19:13:14 +02:00
"miniz_oxide",
Bat
2019-05-18 03:24:13 +02:00
]
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
[[package]]
name = "float-cmp"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "98de4bbd547a563b716d8dfa9aad1cb19bfab00f4fa09a6a4ed21dbcf44ce9c4"
dependencies = [
"num-traits",
]
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "fnv"
Evaluation of command arguments (#1801) * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * Finish adding the baseline refactors for argument invocation * Finish cleanup and add test * Add missing plugin references
2020-05-16 05:18:24 +02:00
version = "1.0.7"
Bat
2019-05-18 03:24:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Evaluation of command arguments (#1801) * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * Finish adding the baseline refactors for argument invocation * Finish cleanup and add test * Add missing plugin references
2020-05-16 05:18:24 +02:00
checksum = "3f9eec918d3f24069decb9af1554cad7c880e2da24a9afd88aca000531ab82c1"
Bat
2019-05-18 03:24:13 +02:00
Add a --full mode to ps (#1507) * Add a --full mode to ps * Use a slightly older heim
2020-03-20 08:53:49 +01:00
[[package]]
name = "foreign-types"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f6f339eb8adc052cd2ca78910fda869aefa38d22d5cb648e6485e4d3fc06f3b1"
dependencies = [
"foreign-types-shared",
]
[[package]]
name = "foreign-types-shared"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "00b0228411908ca8685dba7fc2cdd70ec9990a6e753e89b6ac91a84c40fbaf4b"
Polars upgrade 0.23 (#6303) * more lazy expressions * upgrade polars and correct functions * arg-where example * cargo clippy * restore modified filter files * correct string addition with str * correct string addition with str * correct message in test
2022-08-12 14:10:36 +02:00
[[package]]
name = "foreign_vec"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ee1b05cbd864bcaecbd3455d6d967862d446e4ebfc3c2e5e5b9841e53cba6673"
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
[[package]]
name = "form_urlencoded"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "1.2.1"
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "e13624c2627564efccf4934284bdd98cbaa14e79b0b5a141218e507b3a823456"
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
dependencies = [
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"percent-encoding",
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
]
Re-port filesystem commands (#4387) * Re-port the filesystem commands * Remove commented out section
2022-02-09 15:56:27 +01:00
[[package]]
name = "fs_extra"
Bump fs_extra from 1.2.0 to 1.3.0 (#7976)
2023-02-06 10:59:58 +01:00
version = "1.3.0"
Re-port filesystem commands (#4387) * Re-port the filesystem commands * Remove commented out section
2022-02-09 15:56:27 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump fs_extra from 1.2.0 to 1.3.0 (#7976)
2023-02-06 10:59:58 +01:00
checksum = "42703706b716c37f96a77aea830392ad231f44c9e9a67872fa5548707e11b11c"
Re-port filesystem commands (#4387) * Re-port the filesystem commands * Remove commented out section
2022-02-09 15:56:27 +01:00
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
[[package]]
name = "fsevent-sys"
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
version = "4.1.0"
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
checksum = "76ee7a02da4d231650c7cea31349b889be2f45ddb3ef3032d2ec8185f6313fd2"
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
dependencies = [
"libc",
]
use fs_extra to recursively move folders (#2487)
2020-09-04 01:44:53 +02:00
[[package]]
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
name = "futf"
merge main
2022-02-08 14:28:21 +01:00
version = "0.1.5"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
merge main
2022-02-08 14:28:21 +01:00
checksum = "df420e2e84819663797d1ec6544b13c5be84629e7bb00dc960d6917db2987843"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
dependencies = [
"mac",
"new_debug_unreachable",
]
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
[[package]]
name = "futures"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.3.29"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "da0290714b38af9b4a7b094b8a37086d1b4e61f2df9122c3cad2577669145335"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
dependencies = [
"futures-channel",
"futures-core",
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 04:46:48 +01:00
"futures-executor",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
"futures-io",
"futures-sink",
"futures-task",
"futures-util",
]
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
[[package]]
name = "futures-channel"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.3.29"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "ff4dd66668b557604244583e3e1e1eada8c5c2e96a6d0d6653ede395b78bbacb"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
dependencies = [
"futures-core",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
"futures-sink",
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
]
--no-edit
2019-11-04 16:47:03 +01:00
[[package]]
name = "futures-core"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.3.29"
--no-edit
2019-11-04 16:47:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "eb1d22c66e66d9d72e1758f0bd7d4fd0bee04cad842ee34587d68c07e45d088c"
--no-edit
2019-11-04 16:47:03 +01:00
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 04:46:48 +01:00
[[package]]
name = "futures-executor"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.3.29"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 04:46:48 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "0f4fb8693db0cf099eadcca0efe2a5a22e4550f98ed16aba6c48700da29597bc"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 04:46:48 +01:00
dependencies = [
"futures-core",
"futures-task",
"futures-util",
]
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
[[package]]
name = "futures-io"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.3.29"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "8bf34a163b5c4c52d0478a4d757da8fb65cabef42ba90515efee0f6f9fa45aaa"
Data summarize reporting overhaul. (#2299) Refactored out most of internal work for summarizing data opening the door for generating charts from it. A model is introduced to hold information needed for a summary, Histogram command is an example of a partial usage. This is the beginning. Removed implicit arithmetic traits on Value and Primitive to avoid mixed types panics. The std operations traits can't fail and we can't guarantee that. We can handle gracefully now since compute_values was introduced after the parser changes four months ago. The handling logic should be taken care of either explicitly or in compute_values. The zero identity trait was also removed (and implementing this forced us to also implement Add, Mult, etc) Also: the `math` operations now remove in the output if a given column is not computable: ``` > ls | math sum ──────┬────────── size │ 150.9 KB ──────┴────────── ```
2020-08-04 00:47:19 +02:00
--no-edit
2019-11-04 16:47:03 +01:00
[[package]]
name = "futures-macro"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.3.29"
--no-edit
2019-11-04 16:47:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "53b153fd91e4b0147f4aced87be237c98248656bb01050b96bf3ee89220a8ddb"
--no-edit
2019-11-04 16:47:03 +01:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"proc-macro2",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
--no-edit
2019-11-04 16:47:03 +01:00
]
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
[[package]]
name = "futures-sink"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.3.29"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "e36d3378ee38c2a36ad710c5d30c2911d752cb941c00c72dbabfb786a7970817"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
--no-edit
2019-11-04 16:47:03 +01:00
[[package]]
name = "futures-task"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.3.29"
--no-edit
2019-11-04 16:47:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "efd193069b0ddadc69c46389b740bbccdd97203899b48d09c5f7969591d6bae2"
--no-edit
2019-11-04 16:47:03 +01:00
Fix duration type to not report months or years (#9632) <!-- 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! --> This PR should close #8036, #9028 (in the negative) and #9118. Fix for #9118 is a bit pedantic. As reported, the issue is: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 3yr 12month 2day 18hr 9min 33sec ``` with this PR, you now get: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 208wk 1day 18hr 9min 33sec ``` Which is strictly correct, but could still fairly be called "weird date arithmetic". # Description * [x] Abide by constraint that Value::Duration remains a number of nanoseconds with no additional fields. * [x] `to_string()` only displays weeks .. nanoseconds. Duration doesn't have base date to compute months or years from. * [x] `duration | into record` likewise only has fields for weeks .. nanoseconds. * [x] `string | into duration` now accepts compound form of duration to_string() (e.g '2day 3hr`, not just '2day') * [x] `duration | into string` now works (and produces the same representation as to_string(), which may be compound). # User-Facing Changes ## duration -> string -> duration Now you can "round trip" an arbitrary duration value: convert it to a string that may include multiple time units (a "compound" value), then convert that string back into a duration. This required changes to `string | into duration` and the addition of `duration | into string'. ``` > 2day + 3hr 2day 3hr # the "to_string()" representation (in this case, a compound value) > 2day + 3hr | into string 2day 3hr # string value > 2day + 3hr | into string | into duration 2day 3hr # round-trip duration -> string -> duration ``` Note that `to nuon` and `from nuon` already round-tripped durations, but use a different string representation. ## potentially breaking changes * string rendering of a duration no longer has 'yr' or 'month' phrases. * record from `duration | into record` no longer has 'year' or 'month' fields. The excess duration is all lumped into the `week` field, which is the largest time unit you can convert to without knowing the datetime from which the duration was calculated. Scripts that depended on month or year time units on output will need to be changed. ### Examples ``` > 365day 52wk 1day ## Used to be: ## 1yr > 365day | into record ╭──────┬────╮ │ week │ 52 │ │ day │ 1 │ │ sign │ + │ ╰──────┴────╯ ## used to be: ##╭──────┬───╮ ##│ year │ 1 │ ##│ sign │ + │ ##╰──────┴───╯ > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) 56wk 6day 6hr 7min 8sec 9ms 10µs 11ns ## used to be: ## 1yr 1month 3day 6hr 7min 8sec 9ms 10µs 11ns ## which looks reasonable, but was actually only correct in 75% of the years and 25% of the months in the last 4 years. > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) | into record ╭─────────────┬────╮ │ week │ 56 │ │ day │ 6 │ │ hour │ 6 │ │ minute │ 7 │ │ second │ 8 │ │ millisecond │ 9 │ │ microsecond │ 10 │ │ nanosecond │ 11 │ │ sign │ + │ ╰─────────────┴────╯ ``` Strictly speaking, these changes could break an existing user script. Losing years and months as time units is arguably a regression in behavior. Also, the corrected duration calculation could break an existing script that was calibrated using the old algorithm. # Tests + Formatting ``` > toolkit check pr ``` - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib` # 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. --> --------- Co-authored-by: Bob Hyman <bobhy@localhost.localdomain>
2023-08-08 13:24:09 +02:00
[[package]]
name = "futures-timer"
version = "3.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e64b03909df88034c26dc1547e8970b91f98bdb65165d6a4e9110d94263dbb2c"
--no-edit
2019-11-04 16:47:03 +01:00
[[package]]
name = "futures-util"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.3.29"
--no-edit
2019-11-04 16:47:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "a19526d624e703a3179b3d322efec918b6246ea0fa51d41124525f00f1cc8104"
--no-edit
2019-11-04 16:47:03 +01:00
dependencies = [
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
"futures-channel",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"futures-core",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
"futures-io",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"futures-macro",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
"futures-sink",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"futures-task",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
"memchr",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"pin-project-lite",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"pin-utils",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"slab",
--no-edit
2019-11-04 16:47:03 +01:00
]
Fuzzy completion matching (#5320) * Implement fuzzy match algorithm for suggestions * Use MatchingAlgorithm for custom completions
2022-04-24 23:43:18 +02:00
[[package]]
name = "fuzzy-matcher"
version = "0.3.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "54614a3312934d066701a80f20f15fa3b56d67ac7722b39eea5b4c9dd1d66c94"
dependencies = [
"thread_local",
]
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
[[package]]
name = "fxhash"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c31b6d751ae2c7f11320402d34e41349dd1016f8d5d45e48c4312bc8625af50c"
dependencies = [
"byteorder",
]
enable ls_colors for the `ls` command (#340) * enable ls_colors for the `ls` command * added wrapping with ansi-cut so the ansi sequences don't bleed over * clippy
2021-11-15 21:09:17 +01:00
[[package]]
name = "generic-array"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
version = "0.14.7"
enable ls_colors for the `ls` command (#340) * enable ls_colors for the `ls` command * added wrapping with ansi-cut so the ansi sequences don't bleed over * clippy
2021-11-15 21:09:17 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
checksum = "85649ca51fd72272d7821adaf274ad91c288277713d9c18820d8499a7ff69e9a"
enable ls_colors for the `ls` command (#340) * enable ls_colors for the `ls` command * added wrapping with ansi-cut so the ansi sequences don't bleed over * clippy
2021-11-15 21:09:17 +01:00
dependencies = [
"typenum",
Consider space for single `...` column not enough space (#6080) * nu-table: Refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: consider space for single `...` column not enough space Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-19 19:35:25 +02:00
"version_check",
Autoenv rewrite, security and scripting (#2083) * Add args in .nurc file to environment * Working dummy version * Add add_nurc to sync_env command * Parse .nurc file * Delete env vars after leaving directory * Removing vals not working, strangely * Refactoring, add comment * Debugging * Debug by logging to file * Add and remove env var behavior appears correct However, it does not use existing code that well. * Move work to cli.rs * Parse config directories * I am in a state of distress * Rename .nurc to .nu * Some notes for me * Refactoring * Removing vars works, but not done in a very nice fashion * Refactor env_vars_to_delete * Refactor env_vars_to_add() * Move directory environment code to separate file * Refactor from_config * Restore env values * Working? * Working? * Update comments and change var name * Formatting * Remove vars after leaving dir * Remove notes I made * Rename config function * Clippy * Cleanup and handle errors * cargo fmt * Better error messages, remove last (?) unwrap * FORMAT PLZ * Rename whitelisted_directories to allowed_directories * Add comment to clarify how overwritten values are restored. * Change list of allowed dirs to indexmap * Rewrite starting * rewrite everything * Overwritten env values tracks an indexmap instead of vector * Refactor restore function * Untrack removed vars properly * Performance concerns * Performance concerns * Error handling * Clippy * Add type aliases for String and OsString * Deletion almost works * Working? * Error handling and refactoring * nicer errors * Add TODO file * Move outside of loop * Error handling * Reworking adding of vars * Reworking adding of vars * Ready for testing * Refactoring * Restore overwritten vals code * todo.org * Remove overwritten values tracking, as it is not needed * Cleanup, stop tracking overwritten values as nu takes care of it * Init autoenv command * Initialize autoenv and autoenv trust * autoenv trust toml * toml * Use serde for autoenv * Optional directory arg * Add autoenv untrust command * ... actually add autoenv untrust this time * OsString and paths * Revert "OsString and paths" This reverts commit e6eedf882498c1365ecfc899e5ec11bd83cb055c. * Fix path * Fix path * Autoenv trust and untrust * Start using autoenv * Check hashes * Use trust functionality when setting vars * Remove unused code * Clippy * Nicer errors for autoenv commands * Non-working errors * Update error description * Satisfy fmt * Errors * Errors print, but not nicely * Nicer errors * fmt * Delete accidentally added todo.org file * Rename direnv to autoenv * Use ShellError instead of Error * Change tests to pass, danger zone? * Clippy and errors * Clippy... again * Replace match with or_else * Use sha2 crate for hashing * parsing and error msg * Refactoring * Only apply vars once * if parent dir * Delete vars * Rework exit code * Adding works * restore * Fix possibility of infinite loop * Refactoring * Non-working * Revert "Non-working" This reverts commit e231b85570bcb3fc838f950e9f5004c6a7c5a2ac. * Revert "Revert "Non-working"" This reverts commit 804092e46a752266576b044401cc97c317e41f21. * Autoenv trust works without restart * Cargo fix * Script vars * Serde * Serde errors * Entry and exitscripts * Clippy * Support windows and handle errors * Formatting * Fix infinite loop on windows * Debugging windows loop * More windows infinite loop debugging * Windows loop debugging #3 * windows loop #4 * Don't return err * Cleanup unused code * Infinite loop debug * Loop debugging * Check if infinite loop is vars_to_add * env_vars_to_add does not terminate, skip loop as test * Hypothesis: std::env::current_dir() is messing with something * Hypothesis: std::env::current_dir() is messing with something * plz * make clippy happy * debugging in env_vars_to_add * Debbuging env_vars_to_add #2 * clippy * clippy.. * Fool clippy * Fix another infinite loop * Binary search for error location x) * Binary search #3 * fmt * Binary search #4 * more searching... * closing in... maybe * PLZ * Cleanup * Restore commented out functionality * Handle case when user gives the directory "." * fmt * Use fs::canonicalize for paths * Create optional script section * fmt * Add exitscripts even if no entryscripts are defined * All sections in .nu-env are now optional * Re-read config file each directory change * Hot reload after autoenv untrust, don't run exitscripts if untrusted * Debugging * Fix issue with recursive adding of vars * Thank you for finding my issues Mr. Azure * use std::env
2020-07-05 19:34:00 +02:00
]
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
[[package]]
name = "getrandom"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.2.11"
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "fe9006bed769170c11f845cf00c7c1e9092aeb3f268e007c3e760ac68008070f"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"js-sys",
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
"libc",
Don't use `oldtime` feature of chrono (#9577) <!-- 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 `chrono` crate enables `oldtime` feature by default, which has a vulnerability (https://rustsec.org/advisories/RUSTSEC-2020-0071). This PR tries to remove `time` v0.1.45 completely from nu and add an audit CI to check for security vulnerabilities. :hand: Wait for the following PRs: - [x] https://github.com/nushell/reedline/pull/599 - [x] https://github.com/bspeice/dtparse/pull/44 - [x] https://github.com/Byron/trash-rs/pull/75 - [x] https://gitlab.com/imp/chrono-humanize-rs/-/merge_requests/15 # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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. --> --------- Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-25 10:54:01 +02:00
"wasi",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"wasm-bindgen",
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
]
Evaluation of command arguments (#1801) * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * Finish adding the baseline refactors for argument invocation * Finish cleanup and add test * Add missing plugin references
2020-05-16 05:18:24 +02:00
[[package]]
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
name = "gimli"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.28.1"
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "4271d37baee1b8c7e4b708028c57d816cf9d2434acb33a549475f78c181f6253"
Fix VCS markers not showing up in textview (#3530) Changes: * Bug fix - bat adds markers only when a file path is passed and it can use git2 on it. It doesn't add markers when bytes are passed. Hence, the code is adjusted accordingly. The sideeffect is files being opened multiple times and its content being unnecessarily loaded in memory. * Refactoring of the crate - Config is extracted to its struct file. Repetitive blocks of code are dried and nested conditionals are flattened.
2021-06-03 08:25:28 +02:00
introducing `gstat`, a new command to get the git status (#443) * wip - preliminary checking * updated to latest pluging * i think it's all working now, except bare words * clippy
2021-12-06 18:28:11 +01:00
[[package]]
Add git branch to prompt
2019-06-01 23:11:28 +02:00
name = "git2"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.18.1"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "fbf97ba92db08df386e10c8ede66a2a0369bd277090afd8710e19e38de9ec0cd"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
dependencies = [
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"bitflags 2.4.1",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"libc",
"libgit2-sys",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"log",
introducing `gstat`, a new command to get the git status (#443) * wip - preliminary checking * updated to latest pluging * i think it's all working now, except bare words * clippy
2021-12-06 18:28:11 +01:00
"openssl-probe",
"openssl-sys",
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
"url",
Add git branch to prompt
2019-06-01 23:11:28 +02:00
]
add query json plugin for experimentation (#3327) * add query json plugin for experimentation * add some error handling * closer but Kind::Array is still horked * unravel the table so the output looks right * clippy * added the ability to use gjson modifiers
2021-04-19 18:19:06 +02:00
[[package]]
name = "gjson"
updated cargo.lock with cargo update (#5201)
2022-04-15 13:04:15 +02:00
version = "0.8.1"
add query json plugin for experimentation (#3327) * add query json plugin for experimentation * add some error handling * closer but Kind::Array is still horked * unravel the table so the output looks right * clippy * added the ability to use gjson modifiers
2021-04-19 18:19:06 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
updated cargo.lock with cargo update (#5201)
2022-04-15 13:04:15 +02:00
checksum = "43503cc176394dd30a6525f5f36e838339b8b5619be33ed9a7783841580a97b6"
add query json plugin for experimentation (#3327) * add query json plugin for experimentation * add some error handling * closer but Kind::Array is still horked * unravel the table so the output looks right * clippy * added the ability to use gjson modifiers
2021-04-19 18:19:06 +02:00
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
[[package]]
name = "glob"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "0.3.1"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "d2fabcfbdc87f4758337ca535fb41a6d701b65693ce38287d856d1674551ec9b"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
[[package]]
name = "h2"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.3.22"
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "4d6250322ef6e60f93f9a2162799302cd6f68f79f6e5d85c8c16f14d1d958178"
Port fetch (with fixes) (#660) * Port fetch to engine-q * Fix check for path as a string * Add a timeout flag and fix some span issues * Add a temporary fetch command that returns byte streams. Got rid of async stuff as we're using the blocking feature of tokio * More tweaks for the bytestream * Rewrite fetch using ByteStreams * buffer read on bytes directly Co-authored-by: Stefan Stanciulescu <contact@stefanstanciulescu.com>
2022-01-04 03:01:18 +01:00
dependencies = [
"bytes",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"fnv",
"futures-core",
"futures-sink",
"futures-util",
"http",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"indexmap",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"slab",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"tokio",
"tokio-util",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"tracing",
]
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
[[package]]
name = "half"
version = "1.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "eabb4a44450da02c90444cf74558da904edde8fb4e9035a9a6a4e15445af0bd7"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
[[package]]
name = "halfbrown"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.2.4"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "5681137554ddff44396e5f149892c769d45301dd9aa19c51602a89ee214cb0ec"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
dependencies = [
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
"hashbrown 0.13.2",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"serde",
]
Playground infraestructure (tests, etc) additions. (#3179) * Playground infraestructure (tests, etc) additions. A few things to note: * Nu can be started with a custom configuration file (`nu --config-file /path/to/sample_config.toml`). Useful for mocking the configuration on test runs. * When given a custom configuration file Nu will save any changes to the file supplied appropiately. * The `$nu.config-path` variable either shows the default configuration file (or the custom one, if given) * We can now run end to end tests with finer grained control (currently, since this is baseline work, standard out) This will allow to check things like exit status, assert the contents with a format, etc) * Remove (for another PR)
2021-03-15 08:26:30 +01:00
[[package]]
name = "hamcrest2"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "49f837c62de05dc9cc71ff6486cd85de8856a330395ae338a04bfcefe5e91075"
dependencies = [
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
"num 0.2.1",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"regex",
Playground infraestructure (tests, etc) additions. (#3179) * Playground infraestructure (tests, etc) additions. A few things to note: * Nu can be started with a custom configuration file (`nu --config-file /path/to/sample_config.toml`). Useful for mocking the configuration on test runs. * When given a custom configuration file Nu will save any changes to the file supplied appropiately. * The `$nu.config-path` variable either shows the default configuration file (or the custom one, if given) * We can now run end to end tests with finer grained control (currently, since this is baseline work, standard out) This will allow to check things like exit status, assert the contents with a format, etc) * Remove (for another PR)
2021-03-15 08:26:30 +01:00
]
Add string stream and binary stream, add text decoding (#570) * WIP * Add binary/string streams and text decoding * Make string collection fallible * Oops, forgot pretty hex * Oops, forgot pretty hex * clippy
2021-12-24 08:22:11 +01:00
[[package]]
name = "hash32"
Add 'detect columns' command (#4127) * Add 'detect columns' command * Fix warnings
2021-11-15 23:29:54 +01:00
version = "0.2.1"
add nu-pretty-hex, add into binary, update binaryview (#3370) * add nu-pretty-hex, add into binary, update binaryview * updated parameter name, updated examples * fixed nu-pretty-hex test * fixed tests again! and added a no color option to pretty-hex
2021-05-01 18:12:25 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add 'detect columns' command (#4127) * Add 'detect columns' command * Fix warnings
2021-11-15 23:29:54 +01:00
checksum = "b0c35f58762feb77d74ebe43bdbc3210f09be9fe6742234d573bacc26ed92b67"
add nu-pretty-hex, add into binary, update binaryview (#3370) * add nu-pretty-hex, add into binary, update binaryview * updated parameter name, updated examples * fixed nu-pretty-hex test * fixed tests again! and added a no color option to pretty-hex
2021-05-01 18:12:25 +02:00
dependencies = [
"byteorder",
]
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 16:27:37 +01:00
[[package]]
name = "hashbrown"
version = "0.13.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "43a3c133739dddd0d2990f9a4bdf8eb4b21ef50e4851ca85ab661199821d510e"
dependencies = [
Update `unicode-linebreak` to `0.1.5` (#9814) # Description This deduplicates `ahash` as it was previously an outdated build-dependency of `unicode-linebreak` Should provide a small benefit to initial from scratch compile. # User-Facing Changes None
2023-07-30 22:17:36 +02:00
"ahash",
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
]
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
[[package]]
name = "hashbrown"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.14.3"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "290f1a1d9242c78d09ce40a5e87e7554ee637af1351968159f4952f028f75604"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
dependencies = [
Update `unicode-linebreak` to `0.1.5` (#9814) # Description This deduplicates `ahash` as it was previously an outdated build-dependency of `unicode-linebreak` Should provide a small benefit to initial from scratch compile. # User-Facing Changes None
2023-07-30 22:17:36 +02:00
"ahash",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"allocator-api2",
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
"rayon",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
]
Initial SQLite functionality (#5182) * Add SQLite functionality to open * Add in-memory SQLite tests * clippy fixes * Fix up old SQLite-related tests
2022-04-14 05:15:02 +02:00
[[package]]
name = "hashlink"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.8.4"
Initial SQLite functionality (#5182) * Add SQLite functionality to open * Add in-memory SQLite tests * clippy fixes * Fix up old SQLite-related tests
2022-04-14 05:15:02 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "e8094feaf31ff591f651a2664fb9cfd92bba7a60ce3197265e9482ebe753c8f7"
Initial SQLite functionality (#5182) * Add SQLite functionality to open * Add in-memory SQLite tests * clippy fixes * Fix up old SQLite-related tests
2022-04-14 05:15:02 +02:00
dependencies = [
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"hashbrown 0.14.3",
Initial SQLite functionality (#5182) * Add SQLite functionality to open * Add in-memory SQLite tests * clippy fixes * Fix up old SQLite-related tests
2022-04-14 05:15:02 +02:00
]
add nu-pretty-hex, add into binary, update binaryview (#3370) * add nu-pretty-hex, add into binary, update binaryview * updated parameter name, updated examples * fixed nu-pretty-hex test * fixed tests again! and added a no color option to pretty-hex
2021-05-01 18:12:25 +02:00
[[package]]
name = "heapless"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.7.17"
add nu-pretty-hex, add into binary, update binaryview (#3370) * add nu-pretty-hex, add into binary, update binaryview * updated parameter name, updated examples * fixed nu-pretty-hex test * fixed tests again! and added a no color option to pretty-hex
2021-05-01 18:12:25 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "cdc6457c0eb62c71aac4bc17216026d8410337c4126773b9c5daba343f17964f"
Add string stream and binary stream, add text decoding (#570) * WIP * Add binary/string streams and text decoding * Make string collection fallible * Oops, forgot pretty hex * Oops, forgot pretty hex * clippy
2021-12-24 08:22:11 +01:00
dependencies = [
cargo update (#5639)
2022-05-25 19:13:14 +02:00
"atomic-polyfill",
Consider space for single `...` column not enough space (#6080) * nu-table: Refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: consider space for single `...` column not enough space Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-19 19:35:25 +02:00
"hash32",
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
"rustc_version",
Add 'detect columns' command (#4127) * Add 'detect columns' command * Fix warnings
2021-11-15 23:29:54 +01:00
"spin",
add nu-pretty-hex, add into binary, update binaryview (#3370) * add nu-pretty-hex, add into binary, update binaryview * updated parameter name, updated examples * fixed nu-pretty-hex test * fixed tests again! and added a no color option to pretty-hex
2021-05-01 18:12:25 +02:00
"stable_deref_trait",
]
Remove 'arboard' (#4174)
2021-12-01 20:48:03 +01:00
[[package]]
name = "heck"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "0.4.1"
Remove 'arboard' (#4174)
2021-12-01 20:48:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "95505c38b4572b2d910cecb0281560f54b440a19336cbbcb27bf6ce6adc6f5a8"
Remove 'arboard' (#4174)
2021-12-01 20:48:03 +01:00
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
[[package]]
name = "hermit-abi"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.3.3"
Bump miette from 5.5.0 to 5.6.0 (#8531) Bumps [miette](https://github.com/zkat/miette) from 5.5.0 to 5.6.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zkat/miette/blob/main/CHANGELOG.md">miette's changelog</a>.</em></p> <blockquote> <h2>5.6.0 (2023-03-14)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>ci:</strong> configure clippy-specific MSRV (<a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747">b658fc02</a>)</li> <li><strong>graphical:</strong> Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>) (<a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0">3497508a</a>)</li> <li><strong>atty:</strong> Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>) (<a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e">443d240f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>protocol:</strong> implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>) (<a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d">ed486c95</a>)</li> </ul> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/zkat/miette/commit/78fe18e6990feacc8bdaeeb10e1439a12c111e6e"><code>78fe18e</code></a> chore: Release</li> <li><a href="https://github.com/zkat/miette/commit/2335b25ee7d22bd4ef4e1ef1dd9527fe2accd2be"><code>2335b25</code></a> docs: update changelog</li> <li><a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e"><code>443d240</code></a> fix(atty): Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>)</li> <li><a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d"><code>ed486c9</code></a> feat(protocol): implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>)</li> <li><a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0"><code>3497508</code></a> fix(graphical): Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>)</li> <li><a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747"><code>b658fc0</code></a> fix(ci): configure clippy-specific MSRV</li> <li><a href="https://github.com/zkat/miette/commit/ebc61b5cf809e4215ca92c32d892cfc4ffb05fa9"><code>ebc61b5</code></a> docs: Mention miette::miette! macro under &quot;... in application code&quot; (<a href="https://redirect.github.com/zkat/miette/issues/233">#233</a>)</li> <li><a href="https://github.com/zkat/miette/commit/14f952dc91b9f27b7ae1e9e03b89744bcc682fa2"><code>14f952d</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li><a href="https://github.com/zkat/miette/commit/128c0a1fae0b578b2de5c8967b87df0d89cd1c54"><code>128c0a1</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li>See full diff in <a href="https://github.com/zkat/miette/compare/miette-derive-v5.5.0...miette-derive-v5.6.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=miette&package-manager=cargo&previous-version=5.5.0&new-version=5.6.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-24 10:55:25 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "d77f7ec81a6d05a3abb01ab6eb7590f6083d08449fe5a1c8b1e620283546ccb7"
Bump miette from 5.5.0 to 5.6.0 (#8531) Bumps [miette](https://github.com/zkat/miette) from 5.5.0 to 5.6.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zkat/miette/blob/main/CHANGELOG.md">miette's changelog</a>.</em></p> <blockquote> <h2>5.6.0 (2023-03-14)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>ci:</strong> configure clippy-specific MSRV (<a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747">b658fc02</a>)</li> <li><strong>graphical:</strong> Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>) (<a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0">3497508a</a>)</li> <li><strong>atty:</strong> Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>) (<a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e">443d240f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>protocol:</strong> implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>) (<a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d">ed486c95</a>)</li> </ul> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/zkat/miette/commit/78fe18e6990feacc8bdaeeb10e1439a12c111e6e"><code>78fe18e</code></a> chore: Release</li> <li><a href="https://github.com/zkat/miette/commit/2335b25ee7d22bd4ef4e1ef1dd9527fe2accd2be"><code>2335b25</code></a> docs: update changelog</li> <li><a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e"><code>443d240</code></a> fix(atty): Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>)</li> <li><a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d"><code>ed486c9</code></a> feat(protocol): implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>)</li> <li><a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0"><code>3497508</code></a> fix(graphical): Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>)</li> <li><a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747"><code>b658fc0</code></a> fix(ci): configure clippy-specific MSRV</li> <li><a href="https://github.com/zkat/miette/commit/ebc61b5cf809e4215ca92c32d892cfc4ffb05fa9"><code>ebc61b5</code></a> docs: Mention miette::miette! macro under &quot;... in application code&quot; (<a href="https://redirect.github.com/zkat/miette/issues/233">#233</a>)</li> <li><a href="https://github.com/zkat/miette/commit/14f952dc91b9f27b7ae1e9e03b89744bcc682fa2"><code>14f952d</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li><a href="https://github.com/zkat/miette/commit/128c0a1fae0b578b2de5c8967b87df0d89cd1c54"><code>128c0a1</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li>See full diff in <a href="https://github.com/zkat/miette/compare/miette-derive-v5.5.0...miette-derive-v5.6.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=miette&package-manager=cargo&previous-version=5.5.0&new-version=5.6.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-24 10:55:25 +01:00
Add Cargo.lock
2019-09-24 21:02:35 +02:00
[[package]]
name = "hex"
Move script to nu engine (#3092) * Move run_script to engine * Add which dep and feature to engine * Change unwrap to expect * Add wasm specification * Remove which from default, add specification correctly * Add nu-platform-specifics * Move is_external_cmd to platform_specifics * Add is_external_cmd to host and use it instead of nu_platform directly * Clean up if else logic in is_external_cmd * Bump nu-platform-specifics version * Pass context to print_err * Commit cargo.lock * Move print functions to own module inside nu-engine * Hypocratic change to run windows-nightly again * Add import for Ordering * Move printing of error to host * Move platform specific which functionality to basic host * Allow no use of cmd_name * Fix windows compile issue
2021-03-12 06:20:54 +01:00
version = "0.4.3"
Add Cargo.lock
2019-09-24 21:02:35 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Move script to nu engine (#3092) * Move run_script to engine * Add which dep and feature to engine * Change unwrap to expect * Add wasm specification * Remove which from default, add specification correctly * Add nu-platform-specifics * Move is_external_cmd to platform_specifics * Add is_external_cmd to host and use it instead of nu_platform directly * Clean up if else logic in is_external_cmd * Bump nu-platform-specifics version * Pass context to print_err * Commit cargo.lock * Move print functions to own module inside nu-engine * Hypocratic change to run windows-nightly again * Add import for Ordering * Move printing of error to host * Move platform specific which functionality to basic host * Allow no use of cmd_name * Fix windows compile issue
2021-03-12 06:20:54 +01:00
checksum = "7f24254aa9a54b5c858eaee2f5bccdb46aaf0e486a595ed5fd8f86ba55232a70"
Add Cargo.lock
2019-09-24 21:02:35 +02:00
Start to move to polars 0.29 (#9145) This does part of the work of porting to polars 0.29. However, I am not familiar enough with this part of the codebase to finish it. Things to be done: - We match two times over `polars::Expr` but `Expr::Cache` isn't handled. I don't know what should be done here - `ArgExpr:::List` was renamed to `ArgExpr::Implode`. Does that mean that `dfr list` should be renamed to `dfr implode`? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-05-12 14:44:35 +02:00
[[package]]
name = "home"
version = "0.5.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5444c27eef6923071f7ebcc33e3444508466a76f7a2b93da00ed6e19f30c1ddb"
dependencies = [
"windows-sys 0.48.0",
]
updated fetch to surf2.2 and feature h1-client-rustls (#3120)
2021-03-03 19:18:11 +01:00
[[package]]
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
name = "html5ever"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
version = "0.26.0"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
checksum = "bea68cab48b8459f17cf1c944c67ddc572d272d9f2b274140f223ecb1da4a3b7"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
dependencies = [
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"log",
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
"mac",
"markup5ever",
"proc-macro2",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"quote",
Bump miette from 5.6.0 to 5.7.0 (#8720)
2023-04-06 22:39:54 +02:00
"syn 1.0.109",
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
]
Add simple to-html output and bump version (#1487)
2020-03-15 04:04:44 +01:00
[[package]]
name = "htmlescape"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e9025058dae765dee5070ec375f591e2ba14638c63feff74f13805a72e523163"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
[[package]]
name = "http"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.2.11"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "8947b1a6fad4393052c7ba1f4cd97bed3e953a95c79c92ad9b051a04611d9fbb"
Port fetch (with fixes) (#660) * Port fetch to engine-q * Fix check for path as a string * Add a timeout flag and fix some span issues * Add a temporary fetch command that returns byte streams. Got rid of async stuff as we're using the blocking feature of tokio * More tweaks for the bytestream * Rewrite fetch using ByteStreams * buffer read on bytes directly Co-authored-by: Stefan Stanciulescu <contact@stefanstanciulescu.com>
2022-01-04 03:01:18 +01:00
dependencies = [
"bytes",
"fnv",
Bump scraper from 0.14.0 to 0.15.0 (#8331) Bumps [scraper](https://github.com/causal-agent/scraper) from 0.14.0 to 0.15.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/causal-agent/scraper/releases">scraper's releases</a>.</em></p> <blockquote> <h2>0.15.0</h2> <h2>What's Changed</h2> <ul> <li>Bump cssparser to 0.28 and selectors to 0.23. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li>Create dependabot.yml by <a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li>Re-export Element trait from selectors crate by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/98">causal-agent/scraper#98</a></li> <li>build(deps): fix unchecked lock and update deps by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li>Re-export selectors' CaseSensitivity enum as it is part of our public API. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/108">causal-agent/scraper#108</a></li> <li>perf(element): add one sweep element creation by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/109">causal-agent/scraper#109</a></li> <li>Added feature flag <code>atomic</code> to make use of atomic <code>StrTendril</code> type. by <a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li><a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li><a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li><a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/causal-agent/scraper/commit/3cb7e9a3202fc6f8b80820135ad071916bc2908b"><code>3cb7e9a</code></a> Version 0.15.0</li> <li><a href="https://github.com/causal-agent/scraper/commit/06f395efe0fb4e9c31cdbd81a9f9e41802572b33"><code>06f395e</code></a> Apply clippy suggestion</li> <li><a href="https://github.com/causal-agent/scraper/commit/ec91bf1ebc9921ca2adeddf93555081912c33334"><code>ec91bf1</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/102">#102</a> from jaboatman/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/4b7fb13446f5ab4400b1fdfb3092b71b3157af9a"><code>4b7fb13</code></a> Merge remote-tracking branch 'upstream/master'</li> <li><a href="https://github.com/causal-agent/scraper/commit/aa479ea170b7f2b463ccba85de0c802318d19abe"><code>aa479ea</code></a> perf(element): add one sweep element creation (<a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/109">#109</a>)</li> <li><a href="https://github.com/causal-agent/scraper/commit/9a6a638db208682593d83bef53c29052336c0487"><code>9a6a638</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/108">#108</a> from adamreichold/also-re-export-case-sensitivity</li> <li><a href="https://github.com/causal-agent/scraper/commit/794b5eef87aa1009a31d4d29093269a04e7d80fa"><code>794b5ee</code></a> Re-export selectors' CaseSensitivity enum as it is part of our public API.</li> <li><a href="https://github.com/causal-agent/scraper/commit/6abb8cd625af5ea4f5a59530f03436aa448f7c56"><code>6abb8cd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/107">#107</a> from j-mendez/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/c3dd2600dcd4c17424a307c2f82cfcab41943014"><code>c3dd260</code></a> chore(minor): fix element classes map format</li> <li><a href="https://github.com/causal-agent/scraper/commit/b7955b9049ccf5b685f53854d88cca322aa80bac"><code>b7955b9</code></a> perf(selectors): add lazy classes map</li> <li>Additional commits viewable in <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=scraper&package-manager=cargo&previous-version=0.14.0&new-version=0.15.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-06 04:37:22 +01:00
"itoa",
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
]
Revert "Unify use of the `surf` crate (#3855)" (#3871) This reverts commit 7f7af2bbaa90332377a9eea63e4e7e78cb834694.
2021-07-30 23:04:01 +02:00
[[package]]
name = "http-body"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "0.4.6"
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "7ceab25649e9960c0311ea418d17bee82c0dcec1bd053b5f9a66e265a693bed2"
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
dependencies = [
Port fetch (with fixes) (#660) * Port fetch to engine-q * Fix check for path as a string * Add a timeout flag and fix some span issues * Add a temporary fetch command that returns byte streams. Got rid of async stuff as we're using the blocking feature of tokio * More tweaks for the bytestream * Rewrite fetch using ByteStreams * buffer read on bytes directly Co-authored-by: Stefan Stanciulescu <contact@stefanstanciulescu.com>
2022-01-04 03:01:18 +01:00
"bytes",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"http",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"pin-project-lite",
updated fetch to surf2.2 and feature h1-client-rustls (#3120)
2021-03-03 19:18:11 +01:00
]
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
[[package]]
name = "httparse"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
version = "1.8.0"
Revert "Unify use of the `surf` crate (#3855)" (#3871) This reverts commit 7f7af2bbaa90332377a9eea63e4e7e78cb834694.
2021-07-30 23:04:01 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
checksum = "d897f394bad6a705d5f4104762e116a75639e470d80901eed05a860a95cb1904"
Revert "Unify use of the `surf` crate (#3855)" (#3871) This reverts commit 7f7af2bbaa90332377a9eea63e4e7e78cb834694.
2021-07-30 23:04:01 +02:00
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
[[package]]
name = "httpdate"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.0.3"
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "df3b46402a9d5adb4c86a0cf463f42e19994e3ee891101b1841f30a545cb49a9"
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
allow parsing of human readable datetimes (#11051) # Description This PR adds the ability to parse human readable datetime strings as part of the `into datetime` command. I added a new `-n`/`--list-human` parameter that produces this list to give the user an idea of what is supported. ```nushell ❯ into datetime --list-human ╭#─┬parseable human datetime examples┬───result───╮ │0 │Today 18:30 │in 8 hours │ │1 │2022-11-07 13:25:30 │a year ago │ │2 │15:20 Friday │in 3 days │ │3 │This Friday 17:00 │in 3 days │ │4 │13:25, Next Tuesday │in a week │ │5 │Last Friday at 19:45 │3 days ago │ │6 │In 3 days │in 2 days │ │7 │In 2 hours │in 2 hours │ │8 │10 hours and 5 minutes ago │10 hours ago│ │9 │1 years ago │a year ago │ │10│A year ago │a year ago │ │11│A month ago │a month ago │ │12│A week ago │a week ago │ │13│A day ago │a day ago │ │14│An hour ago │an hour ago │ │15│A minute ago │a minute ago│ │16│A second ago │now │ │17│Now │now │ ╰#─┴parseable human datetime examples┴───result───╯ ``` Or with `$env.config.datetime_format.table` set. ```nushell ❯ into datetime --list-human ╭#─┬parseable human datetime examples┬──────result───────╮ │0 │Today 18:30 │11/14/23 06:30:00PM│ │1 │2022-11-07 13:25:30 │11/07/22 01:25:30PM│ │2 │15:20 Friday │11/17/23 03:20:00PM│ │3 │This Friday 17:00 │11/17/23 05:00:00PM│ │4 │13:25, Next Tuesday │11/21/23 01:25:00PM│ │5 │Last Friday at 19:45 │11/10/23 07:45:00PM│ │6 │In 3 days │11/17/23 10:12:54AM│ │7 │In 2 hours │11/14/23 12:12:54PM│ │8 │10 hours and 5 minutes ago │11/14/23 12:07:54AM│ │9 │1 years ago │11/13/22 10:12:54AM│ │10│A year ago │11/13/22 10:12:54AM│ │11│A month ago │10/15/23 11:12:54AM│ │12│A week ago │11/07/23 10:12:54AM│ │13│A day ago │11/13/23 10:12:54AM│ │14│An hour ago │11/14/23 09:12:54AM│ │15│A minute ago │11/14/23 10:11:54AM│ │16│A second ago │11/14/23 10:12:53AM│ │17│Now │11/14/23 10:12:54AM│ ╰#─┴parseable human datetime examples┴──────result───────╯ ``` # 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-11-16 00:43:37 +01:00
[[package]]
name = "human-date-parser"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "92d65b3ad1fdc03306397b6004b4f8f765cf7467194a1080b4530eeed5a2f0bc"
dependencies = [
"chrono",
"pest",
"pest_derive",
"thiserror",
]
Revert "Unify use of the `surf` crate (#3855)" (#3871) This reverts commit 7f7af2bbaa90332377a9eea63e4e7e78cb834694.
2021-07-30 23:04:01 +02:00
[[package]]
name = "hyper"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.14.27"
Revert "Unify use of the `surf` crate (#3855)" (#3871) This reverts commit 7f7af2bbaa90332377a9eea63e4e7e78cb834694.
2021-07-30 23:04:01 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "ffb1cfd654a8219eaef89881fdb3bb3b1cdc5fa75ded05d6933b2b382e395468"
Port fetch (with fixes) (#660) * Port fetch to engine-q * Fix check for path as a string * Add a timeout flag and fix some span issues * Add a temporary fetch command that returns byte streams. Got rid of async stuff as we're using the blocking feature of tokio * More tweaks for the bytestream * Rewrite fetch using ByteStreams * buffer read on bytes directly Co-authored-by: Stefan Stanciulescu <contact@stefanstanciulescu.com>
2022-01-04 03:01:18 +01:00
dependencies = [
"bytes",
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
"futures-channel",
"futures-core",
"futures-util",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"h2",
Update Cargo.lock (#3527)
2021-06-01 10:11:21 +02:00
"http",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"http-body",
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
"httparse",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"httpdate",
Bump scraper from 0.14.0 to 0.15.0 (#8331) Bumps [scraper](https://github.com/causal-agent/scraper) from 0.14.0 to 0.15.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/causal-agent/scraper/releases">scraper's releases</a>.</em></p> <blockquote> <h2>0.15.0</h2> <h2>What's Changed</h2> <ul> <li>Bump cssparser to 0.28 and selectors to 0.23. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li>Create dependabot.yml by <a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li>Re-export Element trait from selectors crate by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/98">causal-agent/scraper#98</a></li> <li>build(deps): fix unchecked lock and update deps by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li>Re-export selectors' CaseSensitivity enum as it is part of our public API. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/108">causal-agent/scraper#108</a></li> <li>perf(element): add one sweep element creation by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/109">causal-agent/scraper#109</a></li> <li>Added feature flag <code>atomic</code> to make use of atomic <code>StrTendril</code> type. by <a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li><a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li><a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li><a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/causal-agent/scraper/commit/3cb7e9a3202fc6f8b80820135ad071916bc2908b"><code>3cb7e9a</code></a> Version 0.15.0</li> <li><a href="https://github.com/causal-agent/scraper/commit/06f395efe0fb4e9c31cdbd81a9f9e41802572b33"><code>06f395e</code></a> Apply clippy suggestion</li> <li><a href="https://github.com/causal-agent/scraper/commit/ec91bf1ebc9921ca2adeddf93555081912c33334"><code>ec91bf1</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/102">#102</a> from jaboatman/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/4b7fb13446f5ab4400b1fdfb3092b71b3157af9a"><code>4b7fb13</code></a> Merge remote-tracking branch 'upstream/master'</li> <li><a href="https://github.com/causal-agent/scraper/commit/aa479ea170b7f2b463ccba85de0c802318d19abe"><code>aa479ea</code></a> perf(element): add one sweep element creation (<a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/109">#109</a>)</li> <li><a href="https://github.com/causal-agent/scraper/commit/9a6a638db208682593d83bef53c29052336c0487"><code>9a6a638</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/108">#108</a> from adamreichold/also-re-export-case-sensitivity</li> <li><a href="https://github.com/causal-agent/scraper/commit/794b5eef87aa1009a31d4d29093269a04e7d80fa"><code>794b5ee</code></a> Re-export selectors' CaseSensitivity enum as it is part of our public API.</li> <li><a href="https://github.com/causal-agent/scraper/commit/6abb8cd625af5ea4f5a59530f03436aa448f7c56"><code>6abb8cd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/107">#107</a> from j-mendez/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/c3dd2600dcd4c17424a307c2f82cfcab41943014"><code>c3dd260</code></a> chore(minor): fix element classes map format</li> <li><a href="https://github.com/causal-agent/scraper/commit/b7955b9049ccf5b685f53854d88cca322aa80bac"><code>b7955b9</code></a> perf(selectors): add lazy classes map</li> <li>Additional commits viewable in <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=scraper&package-manager=cargo&previous-version=0.14.0&new-version=0.15.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-06 04:37:22 +01:00
"itoa",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"pin-project-lite",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"socket2 0.4.10",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"tokio",
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
"tower-service",
"tracing",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"want",
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
]
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
[[package]]
name = "iana-time-zone"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.1.58"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "8326b86b6cff230b97d0d312a6c40a60726df3332e721f72a1b035f451663b20"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
dependencies = [
Bump chrono dependency to fix panic (#6317)
2022-08-13 20:21:28 +02:00
"android_system_properties",
"core-foundation-sys",
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
"iana-time-zone-haiku",
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
"js-sys",
"wasm-bindgen",
Bump windows from 0.48.0 to 0.52.0 (#11325) # Description Bump `windows` to 0.52.0 and fix `is_admin` https://github.com/microsoft/windows-rs/pull/2476 # User-Facing Changes N/A --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-12-21 18:49:15 +01:00
"windows-core 0.51.1",
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
]
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
[[package]]
name = "iana-time-zone-haiku"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
version = "0.1.2"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
checksum = "f31827a206f56af32e590ba56d5d2d085f558508192593743f16b2306495269f"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
dependencies = [
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
"cc",
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
]
WIP: Add vcard/ical support (#1504) * Initial from-ical implementation * Initial from-vcard implementation * Rename from-ics and from-vcf for autoconvert * Remove redundant clones * Add from-vcf and from-ics tests Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2020-03-20 20:35:09 +01:00
[[package]]
name = "ical"
Bump ical from 0.8.0 to 0.9.0 (#11419) Bumps [ical](https://github.com/Peltoche/ical-rs) from 0.8.0 to 0.9.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Peltoche/ical-rs/releases">ical's releases</a>.</em></p> <blockquote> <h2>v0.9.0</h2> <h2>What's Changed</h2> <ul> <li>Add the github actions by <a href="https://github.com/Peltoche"><code>@​Peltoche</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/35">Peltoche/ical-rs#35</a></li> <li>Use thiserror instead of failure by <a href="https://github.com/Peltoche"><code>@​Peltoche</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/36">Peltoche/ical-rs#36</a></li> <li>Accept lowercase vCards by <a href="https://github.com/link2xt"><code>@​link2xt</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/37">Peltoche/ical-rs#37</a></li> <li>Parse multiline attributes with tabs correctly by <a href="https://github.com/FliegendeWurst"><code>@​FliegendeWurst</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/41">Peltoche/ical-rs#41</a></li> <li>Ical serde by <a href="https://github.com/daladim"><code>@​daladim</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/44">Peltoche/ical-rs#44</a></li> <li>Set the license to Apache 2 by <a href="https://github.com/Peltoche"><code>@​Peltoche</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/47">Peltoche/ical-rs#47</a></li> <li>Update README.md by <a href="https://github.com/Zearin"><code>@​Zearin</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/51">Peltoche/ical-rs#51</a></li> <li>Adding ical-output support by <a href="https://github.com/migmedia"><code>@​migmedia</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/49">Peltoche/ical-rs#49</a></li> <li>Improve documentation of builders. by <a href="https://github.com/migmedia"><code>@​migmedia</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/52">Peltoche/ical-rs#52</a></li> <li>Add access functions for properties by <a href="https://github.com/reedts"><code>@​reedts</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/53">Peltoche/ical-rs#53</a></li> <li>Fix README by <a href="https://github.com/westy92"><code>@​westy92</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/55">Peltoche/ical-rs#55</a></li> <li>Handle the case were a line contains non-utf8 characters by <a href="https://github.com/Peltoche"><code>@​Peltoche</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/57">Peltoche/ical-rs#57</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/link2xt"><code>@​link2xt</code></a> made their first contribution in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/37">Peltoche/ical-rs#37</a></li> <li><a href="https://github.com/FliegendeWurst"><code>@​FliegendeWurst</code></a> made their first contribution in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/41">Peltoche/ical-rs#41</a></li> <li><a href="https://github.com/daladim"><code>@​daladim</code></a> made their first contribution in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/44">Peltoche/ical-rs#44</a></li> <li><a href="https://github.com/Zearin"><code>@​Zearin</code></a> made their first contribution in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/51">Peltoche/ical-rs#51</a></li> <li><a href="https://github.com/migmedia"><code>@​migmedia</code></a> made their first contribution in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/49">Peltoche/ical-rs#49</a></li> <li><a href="https://github.com/reedts"><code>@​reedts</code></a> made their first contribution in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/53">Peltoche/ical-rs#53</a></li> <li><a href="https://github.com/westy92"><code>@​westy92</code></a> made their first contribution in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/55">Peltoche/ical-rs#55</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/Peltoche/ical-rs/compare/0.6.0...v0.9.0">https://github.com/Peltoche/ical-rs/compare/0.6.0...v0.9.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/Peltoche/ical-rs/commits/v0.9.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=ical&package-manager=cargo&previous-version=0.8.0&new-version=0.9.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-12-25 02:23:27 +01:00
version = "0.9.0"
WIP: Add vcard/ical support (#1504) * Initial from-ical implementation * Initial from-vcard implementation * Rename from-ics and from-vcf for autoconvert * Remove redundant clones * Add from-vcf and from-ics tests Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2020-03-20 20:35:09 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump ical from 0.8.0 to 0.9.0 (#11419) Bumps [ical](https://github.com/Peltoche/ical-rs) from 0.8.0 to 0.9.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Peltoche/ical-rs/releases">ical's releases</a>.</em></p> <blockquote> <h2>v0.9.0</h2> <h2>What's Changed</h2> <ul> <li>Add the github actions by <a href="https://github.com/Peltoche"><code>@​Peltoche</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/35">Peltoche/ical-rs#35</a></li> <li>Use thiserror instead of failure by <a href="https://github.com/Peltoche"><code>@​Peltoche</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/36">Peltoche/ical-rs#36</a></li> <li>Accept lowercase vCards by <a href="https://github.com/link2xt"><code>@​link2xt</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/37">Peltoche/ical-rs#37</a></li> <li>Parse multiline attributes with tabs correctly by <a href="https://github.com/FliegendeWurst"><code>@​FliegendeWurst</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/41">Peltoche/ical-rs#41</a></li> <li>Ical serde by <a href="https://github.com/daladim"><code>@​daladim</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/44">Peltoche/ical-rs#44</a></li> <li>Set the license to Apache 2 by <a href="https://github.com/Peltoche"><code>@​Peltoche</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/47">Peltoche/ical-rs#47</a></li> <li>Update README.md by <a href="https://github.com/Zearin"><code>@​Zearin</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/51">Peltoche/ical-rs#51</a></li> <li>Adding ical-output support by <a href="https://github.com/migmedia"><code>@​migmedia</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/49">Peltoche/ical-rs#49</a></li> <li>Improve documentation of builders. by <a href="https://github.com/migmedia"><code>@​migmedia</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/52">Peltoche/ical-rs#52</a></li> <li>Add access functions for properties by <a href="https://github.com/reedts"><code>@​reedts</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/53">Peltoche/ical-rs#53</a></li> <li>Fix README by <a href="https://github.com/westy92"><code>@​westy92</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/55">Peltoche/ical-rs#55</a></li> <li>Handle the case were a line contains non-utf8 characters by <a href="https://github.com/Peltoche"><code>@​Peltoche</code></a> in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/57">Peltoche/ical-rs#57</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/link2xt"><code>@​link2xt</code></a> made their first contribution in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/37">Peltoche/ical-rs#37</a></li> <li><a href="https://github.com/FliegendeWurst"><code>@​FliegendeWurst</code></a> made their first contribution in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/41">Peltoche/ical-rs#41</a></li> <li><a href="https://github.com/daladim"><code>@​daladim</code></a> made their first contribution in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/44">Peltoche/ical-rs#44</a></li> <li><a href="https://github.com/Zearin"><code>@​Zearin</code></a> made their first contribution in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/51">Peltoche/ical-rs#51</a></li> <li><a href="https://github.com/migmedia"><code>@​migmedia</code></a> made their first contribution in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/49">Peltoche/ical-rs#49</a></li> <li><a href="https://github.com/reedts"><code>@​reedts</code></a> made their first contribution in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/53">Peltoche/ical-rs#53</a></li> <li><a href="https://github.com/westy92"><code>@​westy92</code></a> made their first contribution in <a href="https://redirect.github.com/Peltoche/ical-rs/pull/55">Peltoche/ical-rs#55</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/Peltoche/ical-rs/compare/0.6.0...v0.9.0">https://github.com/Peltoche/ical-rs/compare/0.6.0...v0.9.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/Peltoche/ical-rs/commits/v0.9.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=ical&package-manager=cargo&previous-version=0.8.0&new-version=0.9.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-12-25 02:23:27 +01:00
checksum = "26393c372d4c4d51616084afe36c0b44e4467febaa6f91f11f789094b4863bf9"
WIP: Add vcard/ical support (#1504) * Initial from-ical implementation * Initial from-vcard implementation * Rename from-ics and from-vcf for autoconvert * Remove redundant clones * Add from-vcf and from-ics tests Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2020-03-20 20:35:09 +01:00
dependencies = [
updated dependencies (#2857) Same as #2786 Co-authored-by: sousajo <sousajo@pop-os.localdomain> Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-07 01:38:22 +01:00
"thiserror",
WIP: Add vcard/ical support (#1504) * Initial from-ical implementation * Initial from-vcard implementation * Rename from-ics and from-vcf for autoconvert * Remove redundant clones * Add from-vcf and from-ics tests Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2020-03-20 20:35:09 +01:00
]
bump deps
2019-07-29 09:46:24 +02:00
[[package]]
name = "idna"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.5.0"
bump deps
2019-07-29 09:46:24 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "634d9b1461af396cad843f47fdba5597a4f9e6ddd4bfb6ff5d85028c25cb12f6"
bump deps
2019-07-29 09:46:24 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"unicode-bidi",
"unicode-normalization",
bump deps
2019-07-29 09:46:24 +02:00
]
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
[[package]]
name = "indexmap"
Bump indexmap from 2.0.2 to 2.1.0 (#10969)
2023-11-07 16:36:34 +01:00
version = "2.1.0"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump indexmap from 2.0.2 to 2.1.0 (#10969)
2023-11-07 16:36:34 +01:00
checksum = "d530e1a18b1cb4c484e6e34556a0d948706958449fca0cab753d649f2bce3d1f"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
dependencies = [
"equivalent",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"hashbrown 0.14.3",
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
"serde",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
]
Progress bar Implementation (#7661) # Description _(Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience.)_ I implemented the status bar we talk about yesterday. The idea was inspired by the progress bar of `wget`. I decided to go for the second suggestion by `@Reilly` > 2. add an Option<usize> or whatever to RawStream (and ListStream?) for situations where you do know the length ahead of time For now only works with the command `save` but after the approve of this PR we can see how we can implement it on commands like `cp` and `mv` When using `fetch` nushell will check if there is any `content-length` attribute in the request header. If so, then `fetch` will send it through the new `Option` variable in the `RawStream` to the `save`. If we know the total size we show the progress bar ![nu_pb01](https://user-images.githubusercontent.com/38369407/210298647-07ee55ea-e751-41b1-a84d-f72ec1f6e9e5.jpg) but if we don't then we just show the stats like: data already saved, bytes per second, and time lapse. ![nu_pb02](https://user-images.githubusercontent.com/38369407/210298698-1ef65f51-40cc-4481-83de-309cbd1049cb.jpg) ![nu_pb03](https://user-images.githubusercontent.com/38369407/210298701-eef2ef13-9206-4a98-8202-e4fe5531d79d.jpg) Please let me know If I need to make any changes and I will be happy to do it. # User-Facing Changes A new flag (`--progress` `-p`) was added to the `save` command Examples: ```nu fetch https://github.com/torvalds/linux/archive/refs/heads/master.zip | save --progress -f main.zip fetch https://releases.ubuntu.com/22.04.1/ubuntu-22.04.1-desktop-amd64.iso | save --progress -f main.zip open main.zip --raw | save --progress main.copy ``` # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - I am getting some errors and its weird because the errors are showing up in files i haven't touch. Is this normal? # 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. Co-authored-by: Reilly Wood <reilly.wood@icloud.com>
2023-01-11 02:57:48 +01:00
[[package]]
name = "indicatif"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.17.7"
Progress bar Implementation (#7661) # Description _(Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience.)_ I implemented the status bar we talk about yesterday. The idea was inspired by the progress bar of `wget`. I decided to go for the second suggestion by `@Reilly` > 2. add an Option<usize> or whatever to RawStream (and ListStream?) for situations where you do know the length ahead of time For now only works with the command `save` but after the approve of this PR we can see how we can implement it on commands like `cp` and `mv` When using `fetch` nushell will check if there is any `content-length` attribute in the request header. If so, then `fetch` will send it through the new `Option` variable in the `RawStream` to the `save`. If we know the total size we show the progress bar ![nu_pb01](https://user-images.githubusercontent.com/38369407/210298647-07ee55ea-e751-41b1-a84d-f72ec1f6e9e5.jpg) but if we don't then we just show the stats like: data already saved, bytes per second, and time lapse. ![nu_pb02](https://user-images.githubusercontent.com/38369407/210298698-1ef65f51-40cc-4481-83de-309cbd1049cb.jpg) ![nu_pb03](https://user-images.githubusercontent.com/38369407/210298701-eef2ef13-9206-4a98-8202-e4fe5531d79d.jpg) Please let me know If I need to make any changes and I will be happy to do it. # User-Facing Changes A new flag (`--progress` `-p`) was added to the `save` command Examples: ```nu fetch https://github.com/torvalds/linux/archive/refs/heads/master.zip | save --progress -f main.zip fetch https://releases.ubuntu.com/22.04.1/ubuntu-22.04.1-desktop-amd64.iso | save --progress -f main.zip open main.zip --raw | save --progress main.copy ``` # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - I am getting some errors and its weird because the errors are showing up in files i haven't touch. Is this normal? # 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. Co-authored-by: Reilly Wood <reilly.wood@icloud.com>
2023-01-11 02:57:48 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "fb28741c9db9a713d93deb3bb9515c20788cef5815265bee4980e87bde7e0f25"
Progress bar Implementation (#7661) # Description _(Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience.)_ I implemented the status bar we talk about yesterday. The idea was inspired by the progress bar of `wget`. I decided to go for the second suggestion by `@Reilly` > 2. add an Option<usize> or whatever to RawStream (and ListStream?) for situations where you do know the length ahead of time For now only works with the command `save` but after the approve of this PR we can see how we can implement it on commands like `cp` and `mv` When using `fetch` nushell will check if there is any `content-length` attribute in the request header. If so, then `fetch` will send it through the new `Option` variable in the `RawStream` to the `save`. If we know the total size we show the progress bar ![nu_pb01](https://user-images.githubusercontent.com/38369407/210298647-07ee55ea-e751-41b1-a84d-f72ec1f6e9e5.jpg) but if we don't then we just show the stats like: data already saved, bytes per second, and time lapse. ![nu_pb02](https://user-images.githubusercontent.com/38369407/210298698-1ef65f51-40cc-4481-83de-309cbd1049cb.jpg) ![nu_pb03](https://user-images.githubusercontent.com/38369407/210298701-eef2ef13-9206-4a98-8202-e4fe5531d79d.jpg) Please let me know If I need to make any changes and I will be happy to do it. # User-Facing Changes A new flag (`--progress` `-p`) was added to the `save` command Examples: ```nu fetch https://github.com/torvalds/linux/archive/refs/heads/master.zip | save --progress -f main.zip fetch https://releases.ubuntu.com/22.04.1/ubuntu-22.04.1-desktop-amd64.iso | save --progress -f main.zip open main.zip --raw | save --progress main.copy ``` # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - I am getting some errors and its weird because the errors are showing up in files i haven't touch. Is this normal? # 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. Co-authored-by: Reilly Wood <reilly.wood@icloud.com>
2023-01-11 02:57:48 +01:00
dependencies = [
"console",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"instant",
Progress bar Implementation (#7661) # Description _(Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience.)_ I implemented the status bar we talk about yesterday. The idea was inspired by the progress bar of `wget`. I decided to go for the second suggestion by `@Reilly` > 2. add an Option<usize> or whatever to RawStream (and ListStream?) for situations where you do know the length ahead of time For now only works with the command `save` but after the approve of this PR we can see how we can implement it on commands like `cp` and `mv` When using `fetch` nushell will check if there is any `content-length` attribute in the request header. If so, then `fetch` will send it through the new `Option` variable in the `RawStream` to the `save`. If we know the total size we show the progress bar ![nu_pb01](https://user-images.githubusercontent.com/38369407/210298647-07ee55ea-e751-41b1-a84d-f72ec1f6e9e5.jpg) but if we don't then we just show the stats like: data already saved, bytes per second, and time lapse. ![nu_pb02](https://user-images.githubusercontent.com/38369407/210298698-1ef65f51-40cc-4481-83de-309cbd1049cb.jpg) ![nu_pb03](https://user-images.githubusercontent.com/38369407/210298701-eef2ef13-9206-4a98-8202-e4fe5531d79d.jpg) Please let me know If I need to make any changes and I will be happy to do it. # User-Facing Changes A new flag (`--progress` `-p`) was added to the `save` command Examples: ```nu fetch https://github.com/torvalds/linux/archive/refs/heads/master.zip | save --progress -f main.zip fetch https://releases.ubuntu.com/22.04.1/ubuntu-22.04.1-desktop-amd64.iso | save --progress -f main.zip open main.zip --raw | save --progress main.copy ``` # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - I am getting some errors and its weird because the errors are showing up in files i haven't touch. Is this normal? # 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. Co-authored-by: Reilly Wood <reilly.wood@icloud.com>
2023-01-11 02:57:48 +01:00
"number_prefix",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"portable-atomic",
Progress bar Implementation (#7661) # Description _(Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience.)_ I implemented the status bar we talk about yesterday. The idea was inspired by the progress bar of `wget`. I decided to go for the second suggestion by `@Reilly` > 2. add an Option<usize> or whatever to RawStream (and ListStream?) for situations where you do know the length ahead of time For now only works with the command `save` but after the approve of this PR we can see how we can implement it on commands like `cp` and `mv` When using `fetch` nushell will check if there is any `content-length` attribute in the request header. If so, then `fetch` will send it through the new `Option` variable in the `RawStream` to the `save`. If we know the total size we show the progress bar ![nu_pb01](https://user-images.githubusercontent.com/38369407/210298647-07ee55ea-e751-41b1-a84d-f72ec1f6e9e5.jpg) but if we don't then we just show the stats like: data already saved, bytes per second, and time lapse. ![nu_pb02](https://user-images.githubusercontent.com/38369407/210298698-1ef65f51-40cc-4481-83de-309cbd1049cb.jpg) ![nu_pb03](https://user-images.githubusercontent.com/38369407/210298701-eef2ef13-9206-4a98-8202-e4fe5531d79d.jpg) Please let me know If I need to make any changes and I will be happy to do it. # User-Facing Changes A new flag (`--progress` `-p`) was added to the `save` command Examples: ```nu fetch https://github.com/torvalds/linux/archive/refs/heads/master.zip | save --progress -f main.zip fetch https://releases.ubuntu.com/22.04.1/ubuntu-22.04.1-desktop-amd64.iso | save --progress -f main.zip open main.zip --raw | save --progress main.copy ``` # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - I am getting some errors and its weird because the errors are showing up in files i haven't touch. Is this normal? # 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. Co-authored-by: Reilly Wood <reilly.wood@icloud.com>
2023-01-11 02:57:48 +01:00
"unicode-width",
]
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 02:22:25 +02:00
[[package]]
name = "indoc"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "2.0.4"
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 02:22:25 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "1e186cfbae8084e513daff4240b4797e342f988cecda4fb6c939150f96315fd8"
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 02:22:25 +02:00
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
[[package]]
name = "inotify"
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
version = "0.9.6"
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
checksum = "f8069d3ec154eb856955c1c0fbffefbf5f3c40a104ec912d4797314c1801abff"
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
dependencies = [
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
"bitflags 1.3.2",
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
"inotify-sys",
"libc",
]
[[package]]
name = "inotify-sys"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e05c02b5e89bff3b946cedeca278abc628fe811e604f027c45a8aa3cf793d0eb"
dependencies = [
"libc",
]
Add the nu-serde crate (#3878) * Add the nu-serde crate nu-serde is a crate that can be used to turn a value implementing `serde::Serialize` into a `nu-protocol::Value`. This has the potential to significantly simplify plugin authorship. This crate was the previously independent [serde-nu](https://github.com/lily-mara/serde-nu) but the nushell maintainers expressed an interest in having it added to the mainline nushell repository. * fixup! Add the nu-serde crate
2021-08-01 05:03:13 +02:00
[[package]]
Bump deps and touchup (#2066)
2020-06-27 09:54:31 +02:00
name = "instant"
Fix clippy warnings (#4176)
2021-12-02 19:05:38 +01:00
version = "0.1.12"
Bump deps and touchup (#2066)
2020-06-27 09:54:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Fix clippy warnings (#4176)
2021-12-02 19:05:38 +01:00
checksum = "7a5bbe824c507c5da5956355e86a746d82e0e1464f65d862cc5e71da70e94b2c"
Begin adding wasi support (#2643) * Begin adding wasi support * Now it builds and runs but needs more help
2020-10-07 00:21:24 +02:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Begin adding wasi support (#2643) * Begin adding wasi support * Now it builds and runs but needs more help
2020-10-07 00:21:24 +02:00
]
Bump deps and touchup (#2066)
2020-06-27 09:54:31 +02:00
Pipe external to internal Each line is a string object
2019-05-24 20:48:33 +02:00
[[package]]
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
name = "inventory"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.3.13"
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "0508c56cfe9bfd5dfeb0c22ab9a6abfda2f27bdca422132e494266351ed8d83c"
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
[[package]]
name = "io-lifetimes"
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
version = "1.0.11"
Bump procfs from 0.14.1 to 0.15.1 (#8233) Bumps [procfs](https://github.com/eminence/procfs) from 0.14.1 to 0.15.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/eminence/procfs/releases">procfs's releases</a>.</em></p> <blockquote> <h2>v0.15.1</h2> <h2>New features</h2> <ul> <li>Change Stat::comm documentation by <a href="https://github.com/rust1248"><code>@​rust1248</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/251">eminence/procfs#251</a></li> <li>Add docs and a as_str method to MMPermission by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/252">eminence/procfs#252</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/rust1248"><code>@​rust1248</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/251">eminence/procfs#251</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/eminence/procfs/compare/v0.15.0...v0.15.1">https://github.com/eminence/procfs/compare/v0.15.0...v0.15.1</a></p> <h2>v0.15.0</h2> <h2>New Features</h2> <ul> <li>Add /proc/iomem by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/216">eminence/procfs#216</a></li> <li>Add new functions to read various net files for a specific process by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/226">eminence/procfs#226</a></li> <li>add /proc/kpageflags by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/233">eminence/procfs#233</a></li> <li>Enable oppportunistic fd counting fast path by <a href="https://github.com/bobrik"><code>@​bobrik</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/234">eminence/procfs#234</a></li> <li>add /proc/kpagecount by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/232">eminence/procfs#232</a></li> <li>Add new <code>/proc/meminfo</code> fields. by <a href="https://github.com/afranchuk"><code>@​afranchuk</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/238">eminence/procfs#238</a></li> <li>impl Hash for kernel version by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/240">eminence/procfs#240</a></li> </ul> <h2>Bug fixes</h2> <ul> <li>fix chrono::Local::timestamp deprecated in chrono 0.4.23 by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/220">eminence/procfs#220</a></li> <li>Fix some minor documentation issues by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/225">eminence/procfs#225</a></li> <li>Fixes the reported path when a task's function returns an error by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/230">eminence/procfs#230</a></li> <li>fix shm size type by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/243">eminence/procfs#243</a></li> </ul> <h2>Breaking changes</h2> <ul> <li>ticks_per_second and page_size are infallible by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/235">eminence/procfs#235</a></li> <li>parse uid for /proc/net/{tcp,udp} by <a href="https://github.com/trinity-1686a"><code>@​trinity-1686a</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/231">eminence/procfs#231</a></li> <li>Refactor and expose memory map processing. by <a href="https://github.com/afranchuk"><code>@​afranchuk</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/237">eminence/procfs#237</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/trinity-1686a"><code>@​trinity-1686a</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/231">eminence/procfs#231</a></li> <li><a href="https://github.com/afranchuk"><code>@​afranchuk</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/238">eminence/procfs#238</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/eminence/procfs/compare/v0.14.2...v0.15.0">https://github.com/eminence/procfs/compare/v0.14.2...v0.15.0</a></p> <h2>MSRV Note</h2> <p>This <code>v0.15</code> release is only tested against the latest stable rust compiler, but is known to work with older versions (down to rust 1.48). Support for these older compilers may break in <code>procfs</code> patch releases. See also <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/223">#223</a></p> <h2>v0.14.2</h2> <h2>New Features</h2> <ul> <li>Process: Namespace: Use openat instead of building a path by <a href="https://github.com/arilou"><code>@​arilou</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/192">eminence/procfs#192</a></li> <li>add serde serialize/deserialize derives for public types by <a href="https://github.com/eliad-wiz"><code>@​eliad-wiz</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/193">eminence/procfs#193</a></li> <li>Disabling default features on the <code>chrono</code> crate by <a href="https://github.com/Will-Low"><code>@​Will-Low</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/210">eminence/procfs#210</a></li> <li>Implement smaps_rollup by <a href="https://github.com/TaborKelly"><code>@​TaborKelly</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/214">eminence/procfs#214</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/eminence/procfs/commit/16ccc15aa13d502379d9d55b779ddd969325eb26"><code>16ccc15</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/253">#253</a> from eminence/v0_15_1</li> <li><a href="https://github.com/eminence/procfs/commit/4b5b61a89d1720497202af0df4fe3fbee213c3ef"><code>4b5b61a</code></a> Version 0.15.1</li> <li><a href="https://github.com/eminence/procfs/commit/b7f66d5a8c7676054fa5aa58dd04351e5d5a7fc5"><code>b7f66d5</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/252">#252</a> from eminence/mmperms</li> <li><a href="https://github.com/eminence/procfs/commit/af961235ff6399aaeedf0c8504f55a114c36eed4"><code>af96123</code></a> Add docs and a as_str method to MMPermission</li> <li><a href="https://github.com/eminence/procfs/commit/6c6ddbd42e71748157d29062ac4d721fa5176b2a"><code>6c6ddbd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/251">#251</a> from rust1248/task/fix-comm-docs</li> <li><a href="https://github.com/eminence/procfs/commit/7e7afab4f89fc905240f44e0e740cec5344f52b9"><code>7e7afab</code></a> Change Stat::comm documentation</li> <li><a href="https://github.com/eminence/procfs/commit/391bd13a0ae5d4266d073b0c5540563f6034555e"><code>391bd13</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/247">#247</a> from eminence/statat_nofollow</li> <li><a href="https://github.com/eminence/procfs/commit/d0a7c09304eca6fb99f7b298e8c3f28a198f9af8"><code>d0a7c09</code></a> Don't use SYMLINK_NOFOLLOW in a statat call</li> <li><a href="https://github.com/eminence/procfs/commit/940c16324250bd5110572f51b91ac2b028af7a19"><code>940c163</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/248">#248</a> from eminence/criterion_update</li> <li><a href="https://github.com/eminence/procfs/commit/0e31f6c8ee34a93375edbc0ea970eea3b137cccd"><code>0e31f6c</code></a> Update criterion dev-depencency</li> <li>Additional commits viewable in <a href="https://github.com/eminence/procfs/compare/v0.14.1...v0.15.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=procfs&package-manager=cargo&previous-version=0.14.1&new-version=0.15.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2023-02-27 08:53:01 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
checksum = "eae7b9aee968036d54dce06cebaefd919e4472e753296daccd6d344e3e2df0c2"
Bump procfs from 0.14.1 to 0.15.1 (#8233) Bumps [procfs](https://github.com/eminence/procfs) from 0.14.1 to 0.15.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/eminence/procfs/releases">procfs's releases</a>.</em></p> <blockquote> <h2>v0.15.1</h2> <h2>New features</h2> <ul> <li>Change Stat::comm documentation by <a href="https://github.com/rust1248"><code>@​rust1248</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/251">eminence/procfs#251</a></li> <li>Add docs and a as_str method to MMPermission by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/252">eminence/procfs#252</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/rust1248"><code>@​rust1248</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/251">eminence/procfs#251</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/eminence/procfs/compare/v0.15.0...v0.15.1">https://github.com/eminence/procfs/compare/v0.15.0...v0.15.1</a></p> <h2>v0.15.0</h2> <h2>New Features</h2> <ul> <li>Add /proc/iomem by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/216">eminence/procfs#216</a></li> <li>Add new functions to read various net files for a specific process by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/226">eminence/procfs#226</a></li> <li>add /proc/kpageflags by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/233">eminence/procfs#233</a></li> <li>Enable oppportunistic fd counting fast path by <a href="https://github.com/bobrik"><code>@​bobrik</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/234">eminence/procfs#234</a></li> <li>add /proc/kpagecount by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/232">eminence/procfs#232</a></li> <li>Add new <code>/proc/meminfo</code> fields. by <a href="https://github.com/afranchuk"><code>@​afranchuk</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/238">eminence/procfs#238</a></li> <li>impl Hash for kernel version by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/240">eminence/procfs#240</a></li> </ul> <h2>Bug fixes</h2> <ul> <li>fix chrono::Local::timestamp deprecated in chrono 0.4.23 by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/220">eminence/procfs#220</a></li> <li>Fix some minor documentation issues by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/225">eminence/procfs#225</a></li> <li>Fixes the reported path when a task's function returns an error by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/230">eminence/procfs#230</a></li> <li>fix shm size type by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/243">eminence/procfs#243</a></li> </ul> <h2>Breaking changes</h2> <ul> <li>ticks_per_second and page_size are infallible by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/235">eminence/procfs#235</a></li> <li>parse uid for /proc/net/{tcp,udp} by <a href="https://github.com/trinity-1686a"><code>@​trinity-1686a</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/231">eminence/procfs#231</a></li> <li>Refactor and expose memory map processing. by <a href="https://github.com/afranchuk"><code>@​afranchuk</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/237">eminence/procfs#237</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/trinity-1686a"><code>@​trinity-1686a</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/231">eminence/procfs#231</a></li> <li><a href="https://github.com/afranchuk"><code>@​afranchuk</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/238">eminence/procfs#238</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/eminence/procfs/compare/v0.14.2...v0.15.0">https://github.com/eminence/procfs/compare/v0.14.2...v0.15.0</a></p> <h2>MSRV Note</h2> <p>This <code>v0.15</code> release is only tested against the latest stable rust compiler, but is known to work with older versions (down to rust 1.48). Support for these older compilers may break in <code>procfs</code> patch releases. See also <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/223">#223</a></p> <h2>v0.14.2</h2> <h2>New Features</h2> <ul> <li>Process: Namespace: Use openat instead of building a path by <a href="https://github.com/arilou"><code>@​arilou</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/192">eminence/procfs#192</a></li> <li>add serde serialize/deserialize derives for public types by <a href="https://github.com/eliad-wiz"><code>@​eliad-wiz</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/193">eminence/procfs#193</a></li> <li>Disabling default features on the <code>chrono</code> crate by <a href="https://github.com/Will-Low"><code>@​Will-Low</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/210">eminence/procfs#210</a></li> <li>Implement smaps_rollup by <a href="https://github.com/TaborKelly"><code>@​TaborKelly</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/214">eminence/procfs#214</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/eminence/procfs/commit/16ccc15aa13d502379d9d55b779ddd969325eb26"><code>16ccc15</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/253">#253</a> from eminence/v0_15_1</li> <li><a href="https://github.com/eminence/procfs/commit/4b5b61a89d1720497202af0df4fe3fbee213c3ef"><code>4b5b61a</code></a> Version 0.15.1</li> <li><a href="https://github.com/eminence/procfs/commit/b7f66d5a8c7676054fa5aa58dd04351e5d5a7fc5"><code>b7f66d5</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/252">#252</a> from eminence/mmperms</li> <li><a href="https://github.com/eminence/procfs/commit/af961235ff6399aaeedf0c8504f55a114c36eed4"><code>af96123</code></a> Add docs and a as_str method to MMPermission</li> <li><a href="https://github.com/eminence/procfs/commit/6c6ddbd42e71748157d29062ac4d721fa5176b2a"><code>6c6ddbd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/251">#251</a> from rust1248/task/fix-comm-docs</li> <li><a href="https://github.com/eminence/procfs/commit/7e7afab4f89fc905240f44e0e740cec5344f52b9"><code>7e7afab</code></a> Change Stat::comm documentation</li> <li><a href="https://github.com/eminence/procfs/commit/391bd13a0ae5d4266d073b0c5540563f6034555e"><code>391bd13</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/247">#247</a> from eminence/statat_nofollow</li> <li><a href="https://github.com/eminence/procfs/commit/d0a7c09304eca6fb99f7b298e8c3f28a198f9af8"><code>d0a7c09</code></a> Don't use SYMLINK_NOFOLLOW in a statat call</li> <li><a href="https://github.com/eminence/procfs/commit/940c16324250bd5110572f51b91ac2b028af7a19"><code>940c163</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/248">#248</a> from eminence/criterion_update</li> <li><a href="https://github.com/eminence/procfs/commit/0e31f6c8ee34a93375edbc0ea970eea3b137cccd"><code>0e31f6c</code></a> Update criterion dev-depencency</li> <li>Additional commits viewable in <a href="https://github.com/eminence/procfs/compare/v0.14.1...v0.15.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=procfs&package-manager=cargo&previous-version=0.14.1&new-version=0.15.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2023-02-27 08:53:01 +01:00
dependencies = [
Use `is-terminal` crate for now (#9670) # Description Until we bump our minimal Rust version to `1.70.0` we can't use `std::io::IsTerminal`. The crate `is-terminal` (depending on `rustix` or `windows-sys`) can provide the same. Get's rid of the dependency on the outdated `atty` crate. We already transitively depend on it (e.g. through `miette`) As soon as we reach the new Rust version we can supersede this with @nibon7's #9550 Co-authored-by: nibon7 <nibon7@163.com>
2023-07-12 18:15:54 +02:00
"hermit-abi",
Bump procfs from 0.14.1 to 0.15.1 (#8233) Bumps [procfs](https://github.com/eminence/procfs) from 0.14.1 to 0.15.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/eminence/procfs/releases">procfs's releases</a>.</em></p> <blockquote> <h2>v0.15.1</h2> <h2>New features</h2> <ul> <li>Change Stat::comm documentation by <a href="https://github.com/rust1248"><code>@​rust1248</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/251">eminence/procfs#251</a></li> <li>Add docs and a as_str method to MMPermission by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/252">eminence/procfs#252</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/rust1248"><code>@​rust1248</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/251">eminence/procfs#251</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/eminence/procfs/compare/v0.15.0...v0.15.1">https://github.com/eminence/procfs/compare/v0.15.0...v0.15.1</a></p> <h2>v0.15.0</h2> <h2>New Features</h2> <ul> <li>Add /proc/iomem by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/216">eminence/procfs#216</a></li> <li>Add new functions to read various net files for a specific process by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/226">eminence/procfs#226</a></li> <li>add /proc/kpageflags by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/233">eminence/procfs#233</a></li> <li>Enable oppportunistic fd counting fast path by <a href="https://github.com/bobrik"><code>@​bobrik</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/234">eminence/procfs#234</a></li> <li>add /proc/kpagecount by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/232">eminence/procfs#232</a></li> <li>Add new <code>/proc/meminfo</code> fields. by <a href="https://github.com/afranchuk"><code>@​afranchuk</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/238">eminence/procfs#238</a></li> <li>impl Hash for kernel version by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/240">eminence/procfs#240</a></li> </ul> <h2>Bug fixes</h2> <ul> <li>fix chrono::Local::timestamp deprecated in chrono 0.4.23 by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/220">eminence/procfs#220</a></li> <li>Fix some minor documentation issues by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/225">eminence/procfs#225</a></li> <li>Fixes the reported path when a task's function returns an error by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/230">eminence/procfs#230</a></li> <li>fix shm size type by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/243">eminence/procfs#243</a></li> </ul> <h2>Breaking changes</h2> <ul> <li>ticks_per_second and page_size are infallible by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/235">eminence/procfs#235</a></li> <li>parse uid for /proc/net/{tcp,udp} by <a href="https://github.com/trinity-1686a"><code>@​trinity-1686a</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/231">eminence/procfs#231</a></li> <li>Refactor and expose memory map processing. by <a href="https://github.com/afranchuk"><code>@​afranchuk</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/237">eminence/procfs#237</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/trinity-1686a"><code>@​trinity-1686a</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/231">eminence/procfs#231</a></li> <li><a href="https://github.com/afranchuk"><code>@​afranchuk</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/238">eminence/procfs#238</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/eminence/procfs/compare/v0.14.2...v0.15.0">https://github.com/eminence/procfs/compare/v0.14.2...v0.15.0</a></p> <h2>MSRV Note</h2> <p>This <code>v0.15</code> release is only tested against the latest stable rust compiler, but is known to work with older versions (down to rust 1.48). Support for these older compilers may break in <code>procfs</code> patch releases. See also <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/223">#223</a></p> <h2>v0.14.2</h2> <h2>New Features</h2> <ul> <li>Process: Namespace: Use openat instead of building a path by <a href="https://github.com/arilou"><code>@​arilou</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/192">eminence/procfs#192</a></li> <li>add serde serialize/deserialize derives for public types by <a href="https://github.com/eliad-wiz"><code>@​eliad-wiz</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/193">eminence/procfs#193</a></li> <li>Disabling default features on the <code>chrono</code> crate by <a href="https://github.com/Will-Low"><code>@​Will-Low</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/210">eminence/procfs#210</a></li> <li>Implement smaps_rollup by <a href="https://github.com/TaborKelly"><code>@​TaborKelly</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/214">eminence/procfs#214</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/eminence/procfs/commit/16ccc15aa13d502379d9d55b779ddd969325eb26"><code>16ccc15</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/253">#253</a> from eminence/v0_15_1</li> <li><a href="https://github.com/eminence/procfs/commit/4b5b61a89d1720497202af0df4fe3fbee213c3ef"><code>4b5b61a</code></a> Version 0.15.1</li> <li><a href="https://github.com/eminence/procfs/commit/b7f66d5a8c7676054fa5aa58dd04351e5d5a7fc5"><code>b7f66d5</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/252">#252</a> from eminence/mmperms</li> <li><a href="https://github.com/eminence/procfs/commit/af961235ff6399aaeedf0c8504f55a114c36eed4"><code>af96123</code></a> Add docs and a as_str method to MMPermission</li> <li><a href="https://github.com/eminence/procfs/commit/6c6ddbd42e71748157d29062ac4d721fa5176b2a"><code>6c6ddbd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/251">#251</a> from rust1248/task/fix-comm-docs</li> <li><a href="https://github.com/eminence/procfs/commit/7e7afab4f89fc905240f44e0e740cec5344f52b9"><code>7e7afab</code></a> Change Stat::comm documentation</li> <li><a href="https://github.com/eminence/procfs/commit/391bd13a0ae5d4266d073b0c5540563f6034555e"><code>391bd13</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/247">#247</a> from eminence/statat_nofollow</li> <li><a href="https://github.com/eminence/procfs/commit/d0a7c09304eca6fb99f7b298e8c3f28a198f9af8"><code>d0a7c09</code></a> Don't use SYMLINK_NOFOLLOW in a statat call</li> <li><a href="https://github.com/eminence/procfs/commit/940c16324250bd5110572f51b91ac2b028af7a19"><code>940c163</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/248">#248</a> from eminence/criterion_update</li> <li><a href="https://github.com/eminence/procfs/commit/0e31f6c8ee34a93375edbc0ea970eea3b137cccd"><code>0e31f6c</code></a> Update criterion dev-depencency</li> <li>Additional commits viewable in <a href="https://github.com/eminence/procfs/compare/v0.14.1...v0.15.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=procfs&package-manager=cargo&previous-version=0.14.1&new-version=0.15.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2023-02-27 08:53:01 +01:00
"libc",
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
"windows-sys 0.48.0",
Bump procfs from 0.14.1 to 0.15.1 (#8233) Bumps [procfs](https://github.com/eminence/procfs) from 0.14.1 to 0.15.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/eminence/procfs/releases">procfs's releases</a>.</em></p> <blockquote> <h2>v0.15.1</h2> <h2>New features</h2> <ul> <li>Change Stat::comm documentation by <a href="https://github.com/rust1248"><code>@​rust1248</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/251">eminence/procfs#251</a></li> <li>Add docs and a as_str method to MMPermission by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/252">eminence/procfs#252</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/rust1248"><code>@​rust1248</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/251">eminence/procfs#251</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/eminence/procfs/compare/v0.15.0...v0.15.1">https://github.com/eminence/procfs/compare/v0.15.0...v0.15.1</a></p> <h2>v0.15.0</h2> <h2>New Features</h2> <ul> <li>Add /proc/iomem by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/216">eminence/procfs#216</a></li> <li>Add new functions to read various net files for a specific process by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/226">eminence/procfs#226</a></li> <li>add /proc/kpageflags by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/233">eminence/procfs#233</a></li> <li>Enable oppportunistic fd counting fast path by <a href="https://github.com/bobrik"><code>@​bobrik</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/234">eminence/procfs#234</a></li> <li>add /proc/kpagecount by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/232">eminence/procfs#232</a></li> <li>Add new <code>/proc/meminfo</code> fields. by <a href="https://github.com/afranchuk"><code>@​afranchuk</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/238">eminence/procfs#238</a></li> <li>impl Hash for kernel version by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/240">eminence/procfs#240</a></li> </ul> <h2>Bug fixes</h2> <ul> <li>fix chrono::Local::timestamp deprecated in chrono 0.4.23 by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/220">eminence/procfs#220</a></li> <li>Fix some minor documentation issues by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/225">eminence/procfs#225</a></li> <li>Fixes the reported path when a task's function returns an error by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/230">eminence/procfs#230</a></li> <li>fix shm size type by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/243">eminence/procfs#243</a></li> </ul> <h2>Breaking changes</h2> <ul> <li>ticks_per_second and page_size are infallible by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/235">eminence/procfs#235</a></li> <li>parse uid for /proc/net/{tcp,udp} by <a href="https://github.com/trinity-1686a"><code>@​trinity-1686a</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/231">eminence/procfs#231</a></li> <li>Refactor and expose memory map processing. by <a href="https://github.com/afranchuk"><code>@​afranchuk</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/237">eminence/procfs#237</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/trinity-1686a"><code>@​trinity-1686a</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/231">eminence/procfs#231</a></li> <li><a href="https://github.com/afranchuk"><code>@​afranchuk</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/238">eminence/procfs#238</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/eminence/procfs/compare/v0.14.2...v0.15.0">https://github.com/eminence/procfs/compare/v0.14.2...v0.15.0</a></p> <h2>MSRV Note</h2> <p>This <code>v0.15</code> release is only tested against the latest stable rust compiler, but is known to work with older versions (down to rust 1.48). Support for these older compilers may break in <code>procfs</code> patch releases. See also <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/223">#223</a></p> <h2>v0.14.2</h2> <h2>New Features</h2> <ul> <li>Process: Namespace: Use openat instead of building a path by <a href="https://github.com/arilou"><code>@​arilou</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/192">eminence/procfs#192</a></li> <li>add serde serialize/deserialize derives for public types by <a href="https://github.com/eliad-wiz"><code>@​eliad-wiz</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/193">eminence/procfs#193</a></li> <li>Disabling default features on the <code>chrono</code> crate by <a href="https://github.com/Will-Low"><code>@​Will-Low</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/210">eminence/procfs#210</a></li> <li>Implement smaps_rollup by <a href="https://github.com/TaborKelly"><code>@​TaborKelly</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/214">eminence/procfs#214</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/eminence/procfs/commit/16ccc15aa13d502379d9d55b779ddd969325eb26"><code>16ccc15</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/253">#253</a> from eminence/v0_15_1</li> <li><a href="https://github.com/eminence/procfs/commit/4b5b61a89d1720497202af0df4fe3fbee213c3ef"><code>4b5b61a</code></a> Version 0.15.1</li> <li><a href="https://github.com/eminence/procfs/commit/b7f66d5a8c7676054fa5aa58dd04351e5d5a7fc5"><code>b7f66d5</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/252">#252</a> from eminence/mmperms</li> <li><a href="https://github.com/eminence/procfs/commit/af961235ff6399aaeedf0c8504f55a114c36eed4"><code>af96123</code></a> Add docs and a as_str method to MMPermission</li> <li><a href="https://github.com/eminence/procfs/commit/6c6ddbd42e71748157d29062ac4d721fa5176b2a"><code>6c6ddbd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/251">#251</a> from rust1248/task/fix-comm-docs</li> <li><a href="https://github.com/eminence/procfs/commit/7e7afab4f89fc905240f44e0e740cec5344f52b9"><code>7e7afab</code></a> Change Stat::comm documentation</li> <li><a href="https://github.com/eminence/procfs/commit/391bd13a0ae5d4266d073b0c5540563f6034555e"><code>391bd13</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/247">#247</a> from eminence/statat_nofollow</li> <li><a href="https://github.com/eminence/procfs/commit/d0a7c09304eca6fb99f7b298e8c3f28a198f9af8"><code>d0a7c09</code></a> Don't use SYMLINK_NOFOLLOW in a statat call</li> <li><a href="https://github.com/eminence/procfs/commit/940c16324250bd5110572f51b91ac2b028af7a19"><code>940c163</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/248">#248</a> from eminence/criterion_update</li> <li><a href="https://github.com/eminence/procfs/commit/0e31f6c8ee34a93375edbc0ea970eea3b137cccd"><code>0e31f6c</code></a> Update criterion dev-depencency</li> <li>Additional commits viewable in <a href="https://github.com/eminence/procfs/compare/v0.14.1...v0.15.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=procfs&package-manager=cargo&previous-version=0.14.1&new-version=0.15.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2023-02-27 08:53:01 +01:00
]
Upgrade `open` crate to fix WSL bug (#8905) This PR upgrades the [`open`](https://github.com/Byron/open-rs) crate (used in the `start` command) from 4.0.1 to 4.0.2. This fixes a bug where `open` doesn't always work properly on WSL: https://github.com/Byron/open-rs/pull/71
2023-04-17 07:05:40 +02:00
[[package]]
name = "is-docker"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "928bae27f42bc99b60d9ac7334e3a21d10ad8f1835a4e12ec3ec0464765ed1b3"
dependencies = [
"once_cell",
]
Bump miette from 5.5.0 to 5.6.0 (#8531) Bumps [miette](https://github.com/zkat/miette) from 5.5.0 to 5.6.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zkat/miette/blob/main/CHANGELOG.md">miette's changelog</a>.</em></p> <blockquote> <h2>5.6.0 (2023-03-14)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>ci:</strong> configure clippy-specific MSRV (<a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747">b658fc02</a>)</li> <li><strong>graphical:</strong> Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>) (<a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0">3497508a</a>)</li> <li><strong>atty:</strong> Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>) (<a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e">443d240f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>protocol:</strong> implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>) (<a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d">ed486c95</a>)</li> </ul> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/zkat/miette/commit/78fe18e6990feacc8bdaeeb10e1439a12c111e6e"><code>78fe18e</code></a> chore: Release</li> <li><a href="https://github.com/zkat/miette/commit/2335b25ee7d22bd4ef4e1ef1dd9527fe2accd2be"><code>2335b25</code></a> docs: update changelog</li> <li><a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e"><code>443d240</code></a> fix(atty): Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>)</li> <li><a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d"><code>ed486c9</code></a> feat(protocol): implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>)</li> <li><a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0"><code>3497508</code></a> fix(graphical): Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>)</li> <li><a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747"><code>b658fc0</code></a> fix(ci): configure clippy-specific MSRV</li> <li><a href="https://github.com/zkat/miette/commit/ebc61b5cf809e4215ca92c32d892cfc4ffb05fa9"><code>ebc61b5</code></a> docs: Mention miette::miette! macro under &quot;... in application code&quot; (<a href="https://redirect.github.com/zkat/miette/issues/233">#233</a>)</li> <li><a href="https://github.com/zkat/miette/commit/14f952dc91b9f27b7ae1e9e03b89744bcc682fa2"><code>14f952d</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li><a href="https://github.com/zkat/miette/commit/128c0a1fae0b578b2de5c8967b87df0d89cd1c54"><code>128c0a1</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li>See full diff in <a href="https://github.com/zkat/miette/compare/miette-derive-v5.5.0...miette-derive-v5.6.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=miette&package-manager=cargo&previous-version=5.5.0&new-version=5.6.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-24 10:55:25 +01:00
[[package]]
name = "is-terminal"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.4.9"
Bump miette from 5.5.0 to 5.6.0 (#8531) Bumps [miette](https://github.com/zkat/miette) from 5.5.0 to 5.6.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zkat/miette/blob/main/CHANGELOG.md">miette's changelog</a>.</em></p> <blockquote> <h2>5.6.0 (2023-03-14)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>ci:</strong> configure clippy-specific MSRV (<a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747">b658fc02</a>)</li> <li><strong>graphical:</strong> Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>) (<a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0">3497508a</a>)</li> <li><strong>atty:</strong> Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>) (<a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e">443d240f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>protocol:</strong> implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>) (<a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d">ed486c95</a>)</li> </ul> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/zkat/miette/commit/78fe18e6990feacc8bdaeeb10e1439a12c111e6e"><code>78fe18e</code></a> chore: Release</li> <li><a href="https://github.com/zkat/miette/commit/2335b25ee7d22bd4ef4e1ef1dd9527fe2accd2be"><code>2335b25</code></a> docs: update changelog</li> <li><a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e"><code>443d240</code></a> fix(atty): Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>)</li> <li><a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d"><code>ed486c9</code></a> feat(protocol): implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>)</li> <li><a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0"><code>3497508</code></a> fix(graphical): Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>)</li> <li><a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747"><code>b658fc0</code></a> fix(ci): configure clippy-specific MSRV</li> <li><a href="https://github.com/zkat/miette/commit/ebc61b5cf809e4215ca92c32d892cfc4ffb05fa9"><code>ebc61b5</code></a> docs: Mention miette::miette! macro under &quot;... in application code&quot; (<a href="https://redirect.github.com/zkat/miette/issues/233">#233</a>)</li> <li><a href="https://github.com/zkat/miette/commit/14f952dc91b9f27b7ae1e9e03b89744bcc682fa2"><code>14f952d</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li><a href="https://github.com/zkat/miette/commit/128c0a1fae0b578b2de5c8967b87df0d89cd1c54"><code>128c0a1</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li>See full diff in <a href="https://github.com/zkat/miette/compare/miette-derive-v5.5.0...miette-derive-v5.6.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=miette&package-manager=cargo&previous-version=5.5.0&new-version=5.6.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-24 10:55:25 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "cb0889898416213fab133e1d33a0e5858a48177452750691bde3666d0fdbaf8b"
Bump miette from 5.5.0 to 5.6.0 (#8531) Bumps [miette](https://github.com/zkat/miette) from 5.5.0 to 5.6.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zkat/miette/blob/main/CHANGELOG.md">miette's changelog</a>.</em></p> <blockquote> <h2>5.6.0 (2023-03-14)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>ci:</strong> configure clippy-specific MSRV (<a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747">b658fc02</a>)</li> <li><strong>graphical:</strong> Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>) (<a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0">3497508a</a>)</li> <li><strong>atty:</strong> Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>) (<a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e">443d240f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>protocol:</strong> implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>) (<a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d">ed486c95</a>)</li> </ul> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/zkat/miette/commit/78fe18e6990feacc8bdaeeb10e1439a12c111e6e"><code>78fe18e</code></a> chore: Release</li> <li><a href="https://github.com/zkat/miette/commit/2335b25ee7d22bd4ef4e1ef1dd9527fe2accd2be"><code>2335b25</code></a> docs: update changelog</li> <li><a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e"><code>443d240</code></a> fix(atty): Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>)</li> <li><a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d"><code>ed486c9</code></a> feat(protocol): implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>)</li> <li><a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0"><code>3497508</code></a> fix(graphical): Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>)</li> <li><a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747"><code>b658fc0</code></a> fix(ci): configure clippy-specific MSRV</li> <li><a href="https://github.com/zkat/miette/commit/ebc61b5cf809e4215ca92c32d892cfc4ffb05fa9"><code>ebc61b5</code></a> docs: Mention miette::miette! macro under &quot;... in application code&quot; (<a href="https://redirect.github.com/zkat/miette/issues/233">#233</a>)</li> <li><a href="https://github.com/zkat/miette/commit/14f952dc91b9f27b7ae1e9e03b89744bcc682fa2"><code>14f952d</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li><a href="https://github.com/zkat/miette/commit/128c0a1fae0b578b2de5c8967b87df0d89cd1c54"><code>128c0a1</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li>See full diff in <a href="https://github.com/zkat/miette/compare/miette-derive-v5.5.0...miette-derive-v5.6.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=miette&package-manager=cargo&previous-version=5.5.0&new-version=5.6.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-24 10:55:25 +01:00
dependencies = [
Use `is-terminal` crate for now (#9670) # Description Until we bump our minimal Rust version to `1.70.0` we can't use `std::io::IsTerminal`. The crate `is-terminal` (depending on `rustix` or `windows-sys`) can provide the same. Get's rid of the dependency on the outdated `atty` crate. We already transitively depend on it (e.g. through `miette`) As soon as we reach the new Rust version we can supersede this with @nibon7's #9550 Co-authored-by: nibon7 <nibon7@163.com>
2023-07-12 18:15:54 +02:00
"hermit-abi",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"rustix 0.38.28",
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
"windows-sys 0.48.0",
Bump miette from 5.5.0 to 5.6.0 (#8531) Bumps [miette](https://github.com/zkat/miette) from 5.5.0 to 5.6.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zkat/miette/blob/main/CHANGELOG.md">miette's changelog</a>.</em></p> <blockquote> <h2>5.6.0 (2023-03-14)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>ci:</strong> configure clippy-specific MSRV (<a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747">b658fc02</a>)</li> <li><strong>graphical:</strong> Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>) (<a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0">3497508a</a>)</li> <li><strong>atty:</strong> Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>) (<a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e">443d240f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>protocol:</strong> implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>) (<a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d">ed486c95</a>)</li> </ul> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/zkat/miette/commit/78fe18e6990feacc8bdaeeb10e1439a12c111e6e"><code>78fe18e</code></a> chore: Release</li> <li><a href="https://github.com/zkat/miette/commit/2335b25ee7d22bd4ef4e1ef1dd9527fe2accd2be"><code>2335b25</code></a> docs: update changelog</li> <li><a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e"><code>443d240</code></a> fix(atty): Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>)</li> <li><a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d"><code>ed486c9</code></a> feat(protocol): implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>)</li> <li><a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0"><code>3497508</code></a> fix(graphical): Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>)</li> <li><a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747"><code>b658fc0</code></a> fix(ci): configure clippy-specific MSRV</li> <li><a href="https://github.com/zkat/miette/commit/ebc61b5cf809e4215ca92c32d892cfc4ffb05fa9"><code>ebc61b5</code></a> docs: Mention miette::miette! macro under &quot;... in application code&quot; (<a href="https://redirect.github.com/zkat/miette/issues/233">#233</a>)</li> <li><a href="https://github.com/zkat/miette/commit/14f952dc91b9f27b7ae1e9e03b89744bcc682fa2"><code>14f952d</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li><a href="https://github.com/zkat/miette/commit/128c0a1fae0b578b2de5c8967b87df0d89cd1c54"><code>128c0a1</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li>See full diff in <a href="https://github.com/zkat/miette/compare/miette-derive-v5.5.0...miette-derive-v5.6.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=miette&package-manager=cargo&previous-version=5.5.0&new-version=5.6.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-24 10:55:25 +01:00
]
Upgrade `open` crate to fix WSL bug (#8905) This PR upgrades the [`open`](https://github.com/Byron/open-rs) crate (used in the `start` command) from 4.0.1 to 4.0.2. This fixes a bug where `open` doesn't always work properly on WSL: https://github.com/Byron/open-rs/pull/71
2023-04-17 07:05:40 +02:00
[[package]]
name = "is-wsl"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "173609498df190136aa7dea1a91db051746d339e18476eed5ca40521f02d7aa5"
dependencies = [
"is-docker",
"once_cell",
]
Remove 'arboard' (#4174)
2021-12-01 20:48:03 +01:00
[[package]]
deps: bump to miette 3.0 mainline
2021-09-23 01:49:39 +02:00
name = "is_ci"
version = "1.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "616cde7c720bb2bb5824a224687d8f77bfd38922027f01d825cd7453be5099fb"
tweak version output as a list vs table (#472)
2021-12-11 21:40:16 +01:00
[[package]]
Remove 'arboard' (#4174)
2021-12-01 20:48:03 +01:00
name = "is_debug"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "06d198e9919d9822d5f7083ba8530e04de87841eaf21ead9af8f2304efd57c89"
speed up windows completions (#3665) * speed up windows completions * fix CI failures * make crate optional * one more fix for CI * allow unused
2021-06-21 23:39:21 +02:00
[[package]]
name = "is_executable"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fa9acdc6d67b75e626ad644734e8bc6df893d9cd2a834129065d3dd6158ea9c8"
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"winapi",
speed up windows completions (#3665) * speed up windows completions * fix CI failures * make crate optional * one more fix for CI * allow unused
2021-06-21 23:39:21 +02:00
]
Bump some deps (#1467)
2020-03-08 20:18:44 +01:00
[[package]]
name = "itertools"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
version = "0.10.5"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
checksum = "b0fd2260e829bddf4cb6ea802289de2f86d6a7a690192fbe91b3f46e0f2c8473"
Bump some deps (#1467)
2020-03-08 20:18:44 +01:00
dependencies = [
"either",
]
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 02:22:25 +02:00
[[package]]
name = "itertools"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b1c173a5686ce8bfa551b3563d0c2170bf24ca44da99c7ca4bfdab5418c3fe57"
dependencies = [
"either",
]
Bump itertools from 0.11.0 to 0.12.0 (#11360) Bumps [itertools](https://github.com/rust-itertools/itertools) from 0.11.0 to 0.12.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rust-itertools/itertools/blob/master/CHANGELOG.md">itertools's changelog</a>.</em></p> <blockquote> <h2>0.12.0</h2> <h3>Breaking</h3> <ul> <li>Made <code>take_while_inclusive</code> consume iterator by value (<a href="https://redirect.github.com/rust-itertools/itertools/issues/709">#709</a>)</li> <li>Added <code>Clone</code> bound to <code>Unique</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/777">#777</a>)</li> </ul> <h3>Added</h3> <ul> <li>Added <code>Itertools::try_len</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/723">#723</a>)</li> <li>Added free function <code>sort_unstable</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/796">#796</a>)</li> <li>Added <code>GroupMap::fold_with</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/778">#778</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/785">#785</a>)</li> <li>Added <code>PeekNth::{peek_mut, peek_nth_mut}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/716">#716</a>)</li> <li>Added <code>PeekNth::{next_if, next_if_eq}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/734">#734</a>)</li> <li>Added conversion into <code>(Option&lt;A&gt;,Option&lt;B&gt;)</code> to <code>EitherOrBoth</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/713">#713</a>)</li> <li>Added conversion from <code>Either&lt;A, B&gt;</code> to <code>EitherOrBoth&lt;A, B&gt;</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/715">#715</a>)</li> <li>Implemented <code>ExactSizeIterator</code> for <code>Tuples</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/761">#761</a>)</li> <li>Implemented <code>ExactSizeIterator</code> for <code>(Circular)TupleWindows</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/752">#752</a>)</li> <li>Made <code>EitherOrBoth&lt;T&gt;</code> a shorthand for <code>EitherOrBoth&lt;T, T&gt;</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/719">#719</a>)</li> </ul> <h3>Changed</h3> <ul> <li>Added missing <code>#[must_use]</code> annotations on iterator adaptors (<a href="https://redirect.github.com/rust-itertools/itertools/issues/794">#794</a>)</li> <li>Made <code>Combinations</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/795">#795</a>)</li> <li>Made <code>Intersperse(With)</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/797">#797</a>)</li> <li>Made <code>Permutations</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/793">#793</a>)</li> <li>Made <code>Product</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/800">#800</a>)</li> <li>Made <code>TupleWindows</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/602">#602</a>)</li> <li>Specialized <code>Combinations::{count, size_hint}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/729">#729</a>)</li> <li>Specialized <code>CombinationsWithReplacement::{count, size_hint}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/737">#737</a>)</li> <li>Specialized <code>Powerset::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/765">#765</a>)</li> <li>Specialized <code>Powerset::count</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/735">#735</a>)</li> <li>Specialized <code>TupleCombinations::{count, size_hint}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/763">#763</a>)</li> <li>Specialized <code>TupleCombinations::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/775">#775</a>)</li> <li>Specialized <code>WhileSome::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/780">#780</a>)</li> <li>Specialized <code>WithPosition::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/772">#772</a>)</li> <li>Specialized <code>ZipLongest::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/774">#774</a>)</li> <li>Changed <code>{min, max}_set*</code> operations require <code>alloc</code> feature, instead of <code>std</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/760">#760</a>)</li> <li>Improved documentation of <code>tree_fold1</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/787">#787</a>)</li> <li>Improved documentation of <code>permutations</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/724">#724</a>)</li> <li>Fixed typo in documentation of <code>multiunzip</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/770">#770</a>)</li> </ul> <h3>Notable Internal Changes</h3> <ul> <li>Improved specialization tests (<a href="https://redirect.github.com/rust-itertools/itertools/issues/799">#799</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/786">#786</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/782">#782</a>)</li> <li>Simplified implementation of <code>Permutations</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/739">#739</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/748">#748</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/790">#790</a>)</li> <li>Combined <code>Merge</code>/<code>MergeBy</code>/<code>MergeJoinBy</code> implementations (<a href="https://redirect.github.com/rust-itertools/itertools/issues/736">#736</a>)</li> <li>Simplified <code>Permutations::size_hint</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/739">#739</a>)</li> <li>Fix wrapping arithmetic in benchmarks (<a href="https://redirect.github.com/rust-itertools/itertools/issues/770">#770</a>)</li> <li>Enforced <code>rustfmt</code> in CI (<a href="https://redirect.github.com/rust-itertools/itertools/issues/751">#751</a>)</li> <li>Disallowed compile warnings in CI (<a href="https://redirect.github.com/rust-itertools/itertools/issues/720">#720</a>)</li> <li>Used <code>cargo hack</code> to check MSRV (<a href="https://redirect.github.com/rust-itertools/itertools/issues/754">#754</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rust-itertools/itertools/commit/98ecabb47d7147dae06fc3fa400ec758947194f3"><code>98ecabb</code></a> chore: Release itertools version 0.12.0</li> <li><a href="https://github.com/rust-itertools/itertools/commit/22fc427ac5282cbdafccfe38a686ec1d3b720120"><code>22fc427</code></a> prepare v0.12.0 release</li> <li><a href="https://github.com/rust-itertools/itertools/commit/6d291786a9c9686a3997d93c513bd18326611fe5"><code>6d29178</code></a> Document the field <code>a_cur</code> of <code>Product</code></li> <li><a href="https://github.com/rust-itertools/itertools/commit/bf2b0129d1d3cc1ffa733059f3088adb6d745fe6"><code>bf2b012</code></a> Better <code>Product::size_hint</code></li> <li><a href="https://github.com/rust-itertools/itertools/commit/8d07f6b8566a515118ca8b119f358b73d483152b"><code>8d07f6b</code></a> Make <code>Product</code> lazy</li> <li><a href="https://github.com/rust-itertools/itertools/commit/d7e6bab9fd0ad79130692f8e48e21375362a7614"><code>d7e6bab</code></a> Document the field <code>peek</code> of <code>IntersperseWith</code></li> <li><a href="https://github.com/rust-itertools/itertools/commit/9b01a118919f0d1f7c3327d1a15a5eb660f3912e"><code>9b01a11</code></a> Make <code>IntersperseWith</code> lazy</li> <li><a href="https://github.com/rust-itertools/itertools/commit/4f22173b93a2eb58da16b7da6d08e6c3f1c56544"><code>4f22173</code></a> Refactor <code>IntersperseWith::next</code></li> <li><a href="https://github.com/rust-itertools/itertools/commit/b76172b412116356ebef05b884a6e4def63a4d17"><code>b76172b</code></a> chore: adjust docs to reflect discussion in the PR</li> <li><a href="https://github.com/rust-itertools/itertools/commit/955927f6c424f895ad7519d413bc5718e6ad26bf"><code>955927f</code></a> chore: fixup docs of tree_fold1</li> <li>Additional commits viewable in <a href="https://github.com/rust-itertools/itertools/compare/v0.11.0...v0.12.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=itertools&package-manager=cargo&previous-version=0.11.0&new-version=0.12.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-12-20 15:58:07 +01:00
[[package]]
name = "itertools"
version = "0.12.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "25db6b064527c5d482d0423354fcd07a89a2dfe07b67892e62411946db7f07b0"
dependencies = [
"either",
]
merge main
2022-02-08 14:28:21 +01:00
[[package]]
name = "itoa"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "1.0.10"
merge main
2022-02-08 14:28:21 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "b1a46d1a171d865aa5f83f92695765caa047a9b4cbae2cbf37dbd613a793fd4c"
merge main
2022-02-08 14:28:21 +01:00
Add basic 'did you mean' support
2019-09-13 05:44:21 +02:00
[[package]]
name = "jobserver"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.1.27"
Add basic 'did you mean' support
2019-09-13 05:44:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "8c37f63953c4c63420ed5fd3d6d398c719489b9f872b9fa683262f8edd363c7d"
Add basic 'did you mean' support
2019-09-13 05:44:21 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"libc",
Add basic 'did you mean' support
2019-09-13 05:44:21 +02:00
]
new `glob` command (#5087)
2022-04-04 22:45:01 +02:00
[[package]]
name = "joinery"
version = "2.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "72167d68f5fce3b8655487b8038691a3c9984ee769590f93f2a631f4ad64e4f5"
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
[[package]]
name = "js-sys"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.3.66"
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "cee9c64da59eae3b50095c18d3e74f8b73c0b86d2792824ff01bbce68ba229ca"
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"wasm-bindgen",
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
]
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
[[package]]
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
name = "kqueue"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.0.8"
Dependency update: update notify version to v5 (#8114) # Description Relative: #8060 While investigating, I found we need to update notify, which is a good step to remove some duplicate dependencies. As title, here are some goods and bads after updating: ## Good keep dependency up to date, and remove duplidate dependency(cfg-if, winapi) in Cargo.lock. ## Bad Introduce some breaking changes: After updating to notify v5, I found that we have to remove `Rename` events. But I've testing under notify v4, and it doesn't work good if we running the following command on MacOS: ``` touch a mv a b ``` It fires file create event, but no file rename event. So `rename` event is not really reliable, so I think it's ok for us to remove `Rename` events. The reason to remove `--debounce-ms` flag: It's not provided by defualt file watcher, we can use [PollWatcher](https://docs.rs/notify/latest/notify/poll/struct.PollWatcher.html), but it scans filesystem, which is really expensive. So I just remove the flag. # User-Facing Changes 1. `--debounce-ms` flag is removed 2. no longer watch `Rename` event. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-02-22 22:35:09 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "7447f1ca1b7b563588a205fe93dea8df60fd981423a768bc1c0ded35ed147d0c"
Dependency update: update notify version to v5 (#8114) # Description Relative: #8060 While investigating, I found we need to update notify, which is a good step to remove some duplicate dependencies. As title, here are some goods and bads after updating: ## Good keep dependency up to date, and remove duplidate dependency(cfg-if, winapi) in Cargo.lock. ## Bad Introduce some breaking changes: After updating to notify v5, I found that we have to remove `Rename` events. But I've testing under notify v4, and it doesn't work good if we running the following command on MacOS: ``` touch a mv a b ``` It fires file create event, but no file rename event. So `rename` event is not really reliable, so I think it's ok for us to remove `Rename` events. The reason to remove `--debounce-ms` flag: It's not provided by defualt file watcher, we can use [PollWatcher](https://docs.rs/notify/latest/notify/poll/struct.PollWatcher.html), but it scans filesystem, which is really expensive. So I just remove the flag. # User-Facing Changes 1. `--debounce-ms` flag is removed 2. no longer watch `Rename` event. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-02-22 22:35:09 +01:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"kqueue-sys",
"libc",
]
[[package]]
name = "kqueue-sys"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.0.4"
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "ed9625ffda8729b85e45cf04090035ac368927b8cebc34898e7c120f52e4838b"
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
dependencies = [
"bitflags 1.3.2",
"libc",
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "lazy_static"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "1.4.0"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
[[package]]
name = "lazycell"
version = "1.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "830d08ce1d1d941e6b30645f1a0eb5643013d835ce3779a5fc208261dbe10f55"
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
[[package]]
name = "lexical-core"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
version = "0.8.5"
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
checksum = "2cde5de06e8d4c2faabc400238f9ae1c74d5412d03a7bd067645ccbc47070e46"
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
dependencies = [
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
"lexical-parse-float",
"lexical-parse-integer",
"lexical-util",
"lexical-write-float",
"lexical-write-integer",
]
[[package]]
name = "lexical-parse-float"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
version = "0.8.5"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
checksum = "683b3a5ebd0130b8fb52ba0bdc718cc56815b6a097e28ae5a6997d0ad17dc05f"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
dependencies = [
"lexical-parse-integer",
"lexical-util",
"static_assertions",
]
[[package]]
name = "lexical-parse-integer"
SQLite History MVP with timestamp, duration, working directory, exit status metadata (#5721) This PR adds support for an SQLite history via nushell/reedline#401 The SQLite history is enabled by setting history_file_format: "sqlite" in config.nu. * somewhat working sqlite history * Hook up history command * Fix error in SQlitebacked with empty lines When entering an empty line there previously was the "No command run" error with `SqliteBackedHistory` during addition of the metadata May be considered a temporary fix Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2022-06-14 22:53:33 +02:00
version = "0.8.6"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
SQLite History MVP with timestamp, duration, working directory, exit status metadata (#5721) This PR adds support for an SQLite history via nushell/reedline#401 The SQLite history is enabled by setting history_file_format: "sqlite" in config.nu. * somewhat working sqlite history * Hook up history command * Fix error in SQlitebacked with empty lines When entering an empty line there previously was the "No command run" error with `SqliteBackedHistory` during addition of the metadata May be considered a temporary fix Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2022-06-14 22:53:33 +02:00
checksum = "6d0994485ed0c312f6d965766754ea177d07f9c00c9b82a5ee62ed5b47945ee9"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
dependencies = [
"lexical-util",
"static_assertions",
]
[[package]]
name = "lexical-util"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
version = "0.8.5"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
checksum = "5255b9ff16ff898710eb9eb63cb39248ea8a5bb036bea8085b1a767ff6c4e3fc"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
dependencies = [
"static_assertions",
]
[[package]]
name = "lexical-write-float"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
version = "0.8.5"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
checksum = "accabaa1c4581f05a3923d1b4cfd124c329352288b7b9da09e766b0668116862"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
dependencies = [
"lexical-util",
"lexical-write-integer",
"static_assertions",
]
[[package]]
name = "lexical-write-integer"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
version = "0.8.5"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
checksum = "e1b6f3d1f4422866b68192d62f77bc5c700bee84f3069f2469d7bc8c77852446"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
dependencies = [
"lexical-util",
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
"static_assertions",
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "libc"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "0.2.151"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "302d7ab3130588088d277783b1e2d2e10c9e9e4a16dd9050e6ec93fb3e7048f4"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Expose polars avro support (#10019) # Description Exposes polars avro support via dfr open and dfr to-avro --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-08-16 03:31:49 +02:00
[[package]]
name = "libflate"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5ff4ae71b685bbad2f2f391fe74f6b7659a34871c08b210fdc039e43bee07d18"
dependencies = [
"adler32",
"crc32fast",
"libflate_lz77",
]
[[package]]
name = "libflate_lz77"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a52d3a8bfc85f250440e4424db7d857e241a3aebbbe301f3eb606ab15c39acbf"
dependencies = [
"rle-decode-fast",
]
Add git branch to prompt
2019-06-01 23:11:28 +02:00
[[package]]
name = "libgit2-sys"
Bump git2 from 0.17.2 to 0.18.0 (#10207)
2023-09-04 23:10:25 +02:00
version = "0.16.1+1.7.1"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump git2 from 0.17.2 to 0.18.0 (#10207)
2023-09-04 23:10:25 +02:00
checksum = "f2a2bb3680b094add03bb3732ec520ece34da31a8cd2d633d1389d0f0fb60d0c"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"cc",
"libc",
introducing `gstat`, a new command to get the git status (#443) * wip - preliminary checking * updated to latest pluging * i think it's all working now, except bare words * clippy
2021-12-06 18:28:11 +01:00
"libssh2-sys",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"libz-sys",
introducing `gstat`, a new command to get the git status (#443) * wip - preliminary checking * updated to latest pluging * i think it's all working now, except bare words * clippy
2021-12-06 18:28:11 +01:00
"openssl-sys",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"pkg-config",
Add git branch to prompt
2019-06-01 23:11:28 +02:00
]
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
[[package]]
name = "libloading"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "0.7.4"
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "b67380fd3b2fbe7527a606e18729d21c6f3951633d0500574c4dc22d2d638b9f"
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
"winapi",
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
]
Dataframe commands (#3498) * Sample command * Join command with checks * More dataframes commands * Groupby and aggregate commands * Missing feature dataframe flag * Renamed file
2021-05-27 07:09:48 +02:00
[[package]]
name = "libm"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.2.8"
Dataframe commands (#3498) * Sample command * Join command with checks * More dataframes commands * Groupby and aggregate commands * Missing feature dataframe flag * Renamed file
2021-05-27 07:09:48 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "4ec2a862134d2a7d32d7983ddcdd1c4923530833c9f2ea1a44fc5fa473989058"
Dataframe commands (#3498) * Sample command * Join command with checks * More dataframes commands * Groupby and aggregate commands * Missing feature dataframe flag * Renamed file
2021-05-27 07:09:48 +02:00
Changes global allocator to mimalloc, improving performance. (#9415) # 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. --> this PR makes nushell use mimalloc as the default allocator, this has the benefit of reducing startup time on my machine. `17%` on linux and `22%` on windows, when testing using hyperfine. the overhead to compile seem to be quite small, aswell as the increase of binary size quite small on linux the binary went from `33.1mb` to `33.2mb` linux ![image](https://github.com/nushell/nushell/assets/17986183/ba5379b4-2c08-483a-a9ff-a9d8524d2943) windows ![image](https://github.com/nushell/nushell/assets/17986183/fda5090f-96a9-48d1-ada4-617694b9d880) # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-15 00:27:12 +02:00
[[package]]
name = "libmimalloc-sys"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.1.35"
Changes global allocator to mimalloc, improving performance. (#9415) # 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. --> this PR makes nushell use mimalloc as the default allocator, this has the benefit of reducing startup time on my machine. `17%` on linux and `22%` on windows, when testing using hyperfine. the overhead to compile seem to be quite small, aswell as the increase of binary size quite small on linux the binary went from `33.1mb` to `33.2mb` linux ![image](https://github.com/nushell/nushell/assets/17986183/ba5379b4-2c08-483a-a9ff-a9d8524d2943) windows ![image](https://github.com/nushell/nushell/assets/17986183/fda5090f-96a9-48d1-ada4-617694b9d880) # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-15 00:27:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "3979b5c37ece694f1f5e51e7ecc871fdb0f517ed04ee45f88d15d6d553cb9664"
Changes global allocator to mimalloc, improving performance. (#9415) # 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. --> this PR makes nushell use mimalloc as the default allocator, this has the benefit of reducing startup time on my machine. `17%` on linux and `22%` on windows, when testing using hyperfine. the overhead to compile seem to be quite small, aswell as the increase of binary size quite small on linux the binary went from `33.1mb` to `33.2mb` linux ![image](https://github.com/nushell/nushell/assets/17986183/ba5379b4-2c08-483a-a9ff-a9d8524d2943) windows ![image](https://github.com/nushell/nushell/assets/17986183/fda5090f-96a9-48d1-ada4-617694b9d880) # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-15 00:27:12 +02:00
dependencies = [
"cc",
"libc",
]
Add SQLite support
2019-08-27 23:45:18 +02:00
[[package]]
Add nu-system and rewrite ps command (#734) * Add nu-system and rewrite ps command * Add more deps * Add more deps * clippy * clippy * clippy * clippy * clippy * clippy
2022-01-14 07:20:53 +01:00
name = "libproc"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.14.2"
Add nu-system and rewrite ps command (#734) * Add nu-system and rewrite ps command * Add more deps * Add more deps * clippy * clippy * clippy * clippy * clippy * clippy
2022-01-14 07:20:53 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "229004ebba9d1d5caf41623f1523b6d52abb47d9f6ab87f7e6fc992e3b854aef"
Add nu-system and rewrite ps command (#734) * Add nu-system and rewrite ps command * Add more deps * Add more deps * clippy * clippy * clippy * clippy * clippy * clippy
2022-01-14 07:20:53 +01:00
dependencies = [
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
"bindgen",
Bump libproc from 0.13.0 to 0.14.0 (#9640)
2023-07-10 07:10:36 +02:00
"errno",
Add nu-system and rewrite ps command (#734) * Add nu-system and rewrite ps command * Add more deps * Add more deps * clippy * clippy * clippy * clippy * clippy * clippy
2022-01-14 07:20:53 +01:00
"libc",
]
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
[[package]]
name = "libredox"
version = "0.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "85c833ca1e66078851dba29046874e38f08b2c883700aa29a03ddd3b23814ee8"
dependencies = [
"bitflags 2.4.1",
"libc",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"redox_syscall",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
]
Initial SQLite functionality (#5182) * Add SQLite functionality to open * Add in-memory SQLite tests * clippy fixes * Fix up old SQLite-related tests
2022-04-14 05:15:02 +02:00
[[package]]
name = "libsqlite3-sys"
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
version = "0.26.0"
Initial SQLite functionality (#5182) * Add SQLite functionality to open * Add in-memory SQLite tests * clippy fixes * Fix up old SQLite-related tests
2022-04-14 05:15:02 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
checksum = "afc22eff61b133b115c6e8c74e818c628d6d5e7a502afea6f64dee076dd94326"
Initial SQLite functionality (#5182) * Add SQLite functionality to open * Add in-memory SQLite tests * clippy fixes * Fix up old SQLite-related tests
2022-04-14 05:15:02 +02:00
dependencies = [
"cc",
"pkg-config",
"vcpkg",
]
introducing `gstat`, a new command to get the git status (#443) * wip - preliminary checking * updated to latest pluging * i think it's all working now, except bare words * clippy
2021-12-06 18:28:11 +01:00
[[package]]
name = "libssh2-sys"
Bump git2 from 0.16.1 to 0.17.0 (#8722)
2023-04-05 21:20:58 +02:00
version = "0.3.0"
introducing `gstat`, a new command to get the git status (#443) * wip - preliminary checking * updated to latest pluging * i think it's all working now, except bare words * clippy
2021-12-06 18:28:11 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump git2 from 0.16.1 to 0.17.0 (#8722)
2023-04-05 21:20:58 +02:00
checksum = "2dc8a030b787e2119a731f1951d6a773e2280c660f8ec4b0f5e1505a386e71ee"
introducing `gstat`, a new command to get the git status (#443) * wip - preliminary checking * updated to latest pluging * i think it's all working now, except bare words * clippy
2021-12-06 18:28:11 +01:00
dependencies = [
"cc",
"libc",
"libz-sys",
"openssl-sys",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"pkg-config",
"vcpkg",
Add SQLite support
2019-08-27 23:45:18 +02:00
]
Add git branch to prompt
2019-06-01 23:11:28 +02:00
[[package]]
name = "libz-sys"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.1.12"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "d97137b25e321a73eef1418d1d5d2eda4d77e12813f8e6dead84bc52c5870a7b"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"cc",
"libc",
"pkg-config",
"vcpkg",
Add git branch to prompt
2019-06-01 23:11:28 +02:00
]
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "linked-hash-map"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
version = "0.5.6"
Bat
2019-05-18 03:24:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
checksum = "0717cef1bc8b636c6e1c1bbdefc09e6322da8a9321966e8928ef80d20f7f770f"
Preserve order when serializing/deserialize json by default. (#3126)
2021-03-04 07:35:13 +01:00
dependencies = [
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"serde",
Preserve order when serializing/deserialize json by default. (#3126)
2021-03-04 07:35:13 +01:00
]
Bat
2019-05-18 03:24:13 +02:00
Bump tempfile from 3.4.0 to 3.5.0 (#8719) Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.4.0 to 3.5.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Stebalien/tempfile/blob/master/NEWS">tempfile's changelog</a>.</em></p> <blockquote> <h1>3.5.0</h1> <ul> <li>Update rustix from 0.36 to 0.37.1. This makes wasi work on rust stable</li> <li>Update <code>windows-sys</code>, <code>redox_syscall</code></li> <li>BREAKING: Remove the implementation of <code>Write for &amp;NamedTempFile&lt;F&gt; where &amp;F: Write</code>. Unfortunately, this can cause compile issues in unrelated code (<a href="https://redirect.github.com/Stebalien/tempfile/issues/224">Stebalien/tempfile#224</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/Stebalien/tempfile/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tempfile&package-manager=cargo&previous-version=3.4.0&new-version=3.5.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-06 22:39:31 +02:00
[[package]]
name = "linux-raw-sys"
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
version = "0.3.8"
Bump tempfile from 3.4.0 to 3.5.0 (#8719) Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.4.0 to 3.5.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Stebalien/tempfile/blob/master/NEWS">tempfile's changelog</a>.</em></p> <blockquote> <h1>3.5.0</h1> <ul> <li>Update rustix from 0.36 to 0.37.1. This makes wasi work on rust stable</li> <li>Update <code>windows-sys</code>, <code>redox_syscall</code></li> <li>BREAKING: Remove the implementation of <code>Write for &amp;NamedTempFile&lt;F&gt; where &amp;F: Write</code>. Unfortunately, this can cause compile issues in unrelated code (<a href="https://redirect.github.com/Stebalien/tempfile/issues/224">Stebalien/tempfile#224</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/Stebalien/tempfile/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tempfile&package-manager=cargo&previous-version=3.4.0&new-version=3.5.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-06 22:39:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
checksum = "ef53942eb7bf7ff43a617b3e2c1c4a5ecf5944a7c1bc12d7ee39bbb15e5c1519"
Bump tempfile from 3.4.0 to 3.5.0 (#8719) Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.4.0 to 3.5.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Stebalien/tempfile/blob/master/NEWS">tempfile's changelog</a>.</em></p> <blockquote> <h1>3.5.0</h1> <ul> <li>Update rustix from 0.36 to 0.37.1. This makes wasi work on rust stable</li> <li>Update <code>windows-sys</code>, <code>redox_syscall</code></li> <li>BREAKING: Remove the implementation of <code>Write for &amp;NamedTempFile&lt;F&gt; where &amp;F: Write</code>. Unfortunately, this can cause compile issues in unrelated code (<a href="https://redirect.github.com/Stebalien/tempfile/issues/224">Stebalien/tempfile#224</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/Stebalien/tempfile/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tempfile&package-manager=cargo&previous-version=3.4.0&new-version=3.5.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-06 22:39:31 +02:00
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
[[package]]
name = "linux-raw-sys"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.4.12"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "c4cd1a83af159aa67994778be9070f0ae1bd732942279cabb14f86f986a21456"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
[[package]]
name = "lock_api"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.4.11"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "3c168f8615b12bc01f9c17e2eb0cc07dcae1940121185446edc3744920e8ef45"
Bump deps and touchup (#2066)
2020-06-27 09:54:31 +02:00
dependencies = [
updated cargo.lock with cargo update (#5201)
2022-04-15 13:04:15 +02:00
"autocfg",
Bump deps and touchup (#2066)
2020-06-27 09:54:31 +02:00
"scopeguard",
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "log"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.4.20"
Make mode subcommand: math mode (#2043) * Update calculate to return a table when Value is a table * impl mode subcommand for math * add tests for math mode subcommand * add table/row tests for math mode subcommand * fix formatting
2020-06-24 19:57:27 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "b5e6163cb8c49088c2c36f57875e58ccd8c87c7427f7fbd50ea6710b2f3f2e8f"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
Add LRU regex cache (#7587) Closes #7572 by adding a cache for compiled regexes of type `Arc<Mutex<LruCache<String, Regex>>>` to `EngineState` . The cache is limited to 100 entries (limit chosen arbitrarily) and evicts least-recently-used items first. This PR makes a noticeable difference when using regexes for `color_config`, e.g.: ```bash #first set string formatting in config.nu like: string: { if $in =~ '^#\w{6}$' { $in } else { 'white' } }` # then try displaying and exploring a table with many strings # this is instant after the PR, but takes hundreds of milliseconds before ['#ff0033', '#0025ee', '#0087aa', 'string', '#4101ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff'] ``` ## New dependency (`lru`) This uses [the popular `lru` crate](https://lib.rs/crates/lru). The new dependency adds 19.8KB to a Linux release build of Nushell. I think this is OK, especially since the crate can be useful elsewhere in Nu.
2022-12-23 23:30:04 +01:00
[[package]]
name = "lru"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.12.1"
Add LRU regex cache (#7587) Closes #7572 by adding a cache for compiled regexes of type `Arc<Mutex<LruCache<String, Regex>>>` to `EngineState` . The cache is limited to 100 entries (limit chosen arbitrarily) and evicts least-recently-used items first. This PR makes a noticeable difference when using regexes for `color_config`, e.g.: ```bash #first set string formatting in config.nu like: string: { if $in =~ '^#\w{6}$' { $in } else { 'white' } }` # then try displaying and exploring a table with many strings # this is instant after the PR, but takes hundreds of milliseconds before ['#ff0033', '#0025ee', '#0087aa', 'string', '#4101ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff'] ``` ## New dependency (`lru`) This uses [the popular `lru` crate](https://lib.rs/crates/lru). The new dependency adds 19.8KB to a Linux release build of Nushell. I think this is OK, especially since the crate can be useful elsewhere in Nu.
2022-12-23 23:30:04 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "2994eeba8ed550fd9b47a0b38f0242bc3344e496483c6180b69139cc2fa5d1d7"
Add LRU regex cache (#7587) Closes #7572 by adding a cache for compiled regexes of type `Arc<Mutex<LruCache<String, Regex>>>` to `EngineState` . The cache is limited to 100 entries (limit chosen arbitrarily) and evicts least-recently-used items first. This PR makes a noticeable difference when using regexes for `color_config`, e.g.: ```bash #first set string formatting in config.nu like: string: { if $in =~ '^#\w{6}$' { $in } else { 'white' } }` # then try displaying and exploring a table with many strings # this is instant after the PR, but takes hundreds of milliseconds before ['#ff0033', '#0025ee', '#0087aa', 'string', '#4101ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff'] ``` ## New dependency (`lru`) This uses [the popular `lru` crate](https://lib.rs/crates/lru). The new dependency adds 19.8KB to a Linux release build of Nushell. I think this is OK, especially since the crate can be useful elsewhere in Nu.
2022-12-23 23:30:04 +01:00
dependencies = [
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"hashbrown 0.14.3",
Add LRU regex cache (#7587) Closes #7572 by adding a cache for compiled regexes of type `Arc<Mutex<LruCache<String, Regex>>>` to `EngineState` . The cache is limited to 100 entries (limit chosen arbitrarily) and evicts least-recently-used items first. This PR makes a noticeable difference when using regexes for `color_config`, e.g.: ```bash #first set string formatting in config.nu like: string: { if $in =~ '^#\w{6}$' { $in } else { 'white' } }` # then try displaying and exploring a table with many strings # this is instant after the PR, but takes hundreds of milliseconds before ['#ff0033', '#0025ee', '#0087aa', 'string', '#4101ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff'] ``` ## New dependency (`lru`) This uses [the popular `lru` crate](https://lib.rs/crates/lru). The new dependency adds 19.8KB to a Linux release build of Nushell. I think this is OK, especially since the crate can be useful elsewhere in Nu.
2022-12-23 23:30:04 +01:00
]
respect lscolors env var; measure width minus ansi
2021-10-08 16:40:20 +02:00
[[package]]
name = "lscolors"
Bump lscolors from 0.15.0 to 0.16.0 (#11359)
2023-12-21 17:08:19 +01:00
version = "0.16.0"
update a few nushell dependencies (#6291) * update a few nushell dependencies * update a test
2022-08-10 21:56:15 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump lscolors from 0.15.0 to 0.16.0 (#11359)
2023-12-21 17:08:19 +01:00
checksum = "ab0b209ec3976527806024406fe765474b9a1750a0ed4b8f0372364741f50e7b"
respect lscolors env var; measure width minus ansi
2021-10-08 16:40:20 +02:00
dependencies = [
Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787) # Description Now use `nu-ansi-term` 0.49 Small adjustments to accommodate breaking changes. # User-Facing Changes None
2023-07-24 13:16:18 +02:00
"nu-ansi-term",
Add SQLite support
2019-08-27 23:45:18 +02:00
]
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
[[package]]
name = "lsp-server"
Upgrade lsp-server Dependency (#11252) The lsp-server crate has been released and thus it is now possible to depend on this version rather on the git dependency of the crate.
2023-12-07 00:19:03 +01:00
version = "0.7.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fb69ba934913ebf0ef3b3dd762f0149bf993decd571d094b646de09c2e456732"
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
dependencies = [
"crossbeam-channel",
"log",
"serde",
"serde_json",
]
[[package]]
name = "lsp-types"
Bump lsp-types from 0.94.1 to 0.95.0 (#11457) Bumps [lsp-types](https://github.com/gluon-lang/lsp-types) from 0.94.1 to 0.95.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/gluon-lang/lsp-types/blob/master/CHANGELOG.md">lsp-types's changelog</a>.</em></p> <blockquote> <h2>v0.95.0 (2023-12-12)</h2> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> <h3>v0.94.2 (2023-12-12)</h3> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/gluon-lang/lsp-types/commit/ccf64e2fb62b6e6430140b88f7bbc0b25b4f5864"><code>ccf64e2</code></a> chore: Release lsp-types version 0.95.0</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/bccf50c1c685fb3fe112551bccb3ff58668429ff"><code>bccf50c</code></a> Update changelog</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/75cea03884def635054db135e84ff22b3e6905f2"><code>75cea03</code></a> chore: Release lsp-types version 0.94.2</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/4084a00cd10df3f4a59811295e3dce2f36a842b6"><code>4084a00</code></a> Update changelog</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/b588e166be1140e1177e6ce6b20cb3cbb567128f"><code>b588e16</code></a> Merge pull request <a href="https://redirect.github.com/gluon-lang/lsp-types/issues/274">#274</a> from lapce/inline-completion</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/3031a76c4452f46ed265eb0154d6bb1d10ddb9f6"><code>3031a76</code></a> Add support for textDocument/inlineCompletion</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/038577b0b51abdbcdfad2598e25160c7e5802550"><code>038577b</code></a> doc: Update readme to request links to the spec for PRs</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/f106ccb584d8054e04a7496dd7e87eea4af58066"><code>f106ccb</code></a> Merge pull request <a href="https://redirect.github.com/gluon-lang/lsp-types/issues/257">#257</a> from ahlinc/init-work-done-token</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/730924021a9f5e54b9a7c9c25b3b05d130a2309d"><code>7309240</code></a> Merge pull request <a href="https://redirect.github.com/gluon-lang/lsp-types/issues/259">#259</a> from ebkalderon/fix-telemetry-event-params</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/a15daede51647b08e0ae77248f22463b8c1391a6"><code>a15daed</code></a> Merge pull request <a href="https://redirect.github.com/gluon-lang/lsp-types/issues/264">#264</a> from tage64/master</li> <li>Additional commits viewable in <a href="https://github.com/gluon-lang/lsp-types/compare/v0.94.1...v0.95.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=lsp-types&package-manager=cargo&previous-version=0.94.1&new-version=0.95.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-01-02 00:22:38 +01:00
version = "0.95.0"
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump lsp-types from 0.94.1 to 0.95.0 (#11457) Bumps [lsp-types](https://github.com/gluon-lang/lsp-types) from 0.94.1 to 0.95.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/gluon-lang/lsp-types/blob/master/CHANGELOG.md">lsp-types's changelog</a>.</em></p> <blockquote> <h2>v0.95.0 (2023-12-12)</h2> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> <h3>v0.94.2 (2023-12-12)</h3> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/gluon-lang/lsp-types/commit/ccf64e2fb62b6e6430140b88f7bbc0b25b4f5864"><code>ccf64e2</code></a> chore: Release lsp-types version 0.95.0</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/bccf50c1c685fb3fe112551bccb3ff58668429ff"><code>bccf50c</code></a> Update changelog</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/75cea03884def635054db135e84ff22b3e6905f2"><code>75cea03</code></a> chore: Release lsp-types version 0.94.2</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/4084a00cd10df3f4a59811295e3dce2f36a842b6"><code>4084a00</code></a> Update changelog</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/b588e166be1140e1177e6ce6b20cb3cbb567128f"><code>b588e16</code></a> Merge pull request <a href="https://redirect.github.com/gluon-lang/lsp-types/issues/274">#274</a> from lapce/inline-completion</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/3031a76c4452f46ed265eb0154d6bb1d10ddb9f6"><code>3031a76</code></a> Add support for textDocument/inlineCompletion</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/038577b0b51abdbcdfad2598e25160c7e5802550"><code>038577b</code></a> doc: Update readme to request links to the spec for PRs</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/f106ccb584d8054e04a7496dd7e87eea4af58066"><code>f106ccb</code></a> Merge pull request <a href="https://redirect.github.com/gluon-lang/lsp-types/issues/257">#257</a> from ahlinc/init-work-done-token</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/730924021a9f5e54b9a7c9c25b3b05d130a2309d"><code>7309240</code></a> Merge pull request <a href="https://redirect.github.com/gluon-lang/lsp-types/issues/259">#259</a> from ebkalderon/fix-telemetry-event-params</li> <li><a href="https://github.com/gluon-lang/lsp-types/commit/a15daede51647b08e0ae77248f22463b8c1391a6"><code>a15daed</code></a> Merge pull request <a href="https://redirect.github.com/gluon-lang/lsp-types/issues/264">#264</a> from tage64/master</li> <li>Additional commits viewable in <a href="https://github.com/gluon-lang/lsp-types/compare/v0.94.1...v0.95.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=lsp-types&package-manager=cargo&previous-version=0.94.1&new-version=0.95.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-01-02 00:22:38 +01:00
checksum = "158c1911354ef73e8fe42da6b10c0484cb65c7f1007f28022e847706c1ab6984"
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
dependencies = [
"bitflags 1.3.2",
"serde",
"serde_json",
"serde_repr",
"url",
]
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
[[package]]
name = "lz4"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
version = "1.24.0"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
checksum = "7e9e2dd86df36ce760a60f6ff6ad526f7ba1f14ba0356f8254fb6905e6494df1"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
dependencies = [
"libc",
"lz4-sys",
]
[[package]]
name = "lz4-sys"
Bump lz4-sys from 1.9.3 to 1.9.4 (#6462) Bumps [lz4-sys](https://github.com/10xGenomics/lz4-rs) from 1.9.3 to 1.9.4. - [Release notes](https://github.com/10xGenomics/lz4-rs/releases) - [Changelog](https://github.com/10XGenomics/lz4-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/10xGenomics/lz4-rs/commits) --- updated-dependencies: - dependency-name: lz4-sys dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-09-03 14:32:12 +02:00
version = "1.9.4"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump lz4-sys from 1.9.3 to 1.9.4 (#6462) Bumps [lz4-sys](https://github.com/10xGenomics/lz4-rs) from 1.9.3 to 1.9.4. - [Release notes](https://github.com/10xGenomics/lz4-rs/releases) - [Changelog](https://github.com/10XGenomics/lz4-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/10xGenomics/lz4-rs/commits) --- updated-dependencies: - dependency-name: lz4-sys dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-09-03 14:32:12 +02:00
checksum = "57d27b317e207b10f69f5e75494119e391a96f48861ae870d1da6edac98ca900"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
dependencies = [
"cc",
"libc",
]
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
[[package]]
name = "mac"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c41e0c4fef86961ac6d6f8a82609f55f31b05e4fce149ac5710e439df7619ba4"
Fix ps command CPU usage on Apple Silicon M1 macs. #4142 (#6457) * Fix ps command CPU usage on Apple Silicon M1 macs. #4142 The cpu user and system times returned my libproc are not in nanoseconds; they are in mach ticks units. This is not documented very well. The convert from mach ticks to ns, the kernel provides a timebase info function and datatype: https://developer.apple.com/documentation/driverkit/3433733-mach_timebase_info The commit makes the PS command work for me. * Cargo fmt of previous commit. * Clippy format suggestion Co-authored-by: Ondrej Baudys <ondrej.baudys@nextgen.net>
2022-09-01 08:09:52 +02:00
[[package]]
name = "mach2"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6d0d1830bcd151a6fc4aea1369af235b36c1528fe976b8ff678683c9995eade8"
dependencies = [
"libc",
]
Add clipboard support
2019-06-07 18:30:50 +02:00
[[package]]
name = "malloc_buf"
version = "0.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
checksum = "62bb907fe88d54d8d9ce32a3cceab4218ed2f6b7d35617cafe9adf84e43919cb"
Add clipboard support
2019-06-07 18:30:50 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"libc",
Add clipboard support
2019-06-07 18:30:50 +02:00
]
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
[[package]]
name = "markup5ever"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
version = "0.11.0"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
checksum = "7a2629bb1404f3d34c2e921f21fd34ba00b206124c81f65c50b43b6aaefeb016"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
dependencies = [
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"log",
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
"phf 0.10.1",
"phf_codegen 0.10.0",
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
"string_cache",
"string_cache_codegen",
"tendril",
]
Add sha256 to the hash command (#3836) Hashers now uses on Rust Crypto Digest trait which makes it trivial to implement additional hash functions. The original `md5` crate does not implement the Digest trait and was replaced by `md-5` crate which does. Sha256 uses already included `sha2` crate.
2021-07-25 21:08:08 +02:00
[[package]]
name = "md-5"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.10.6"
Port `hash`, `hash md5` and `hash sha256` commands (#464) `hash` by itself is only printing the help message. The other two are simply using the same generic implementation.
2021-12-11 00:14:28 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "d89e7ee0cfbedfc4da3340218492196241d89eefb6dab27de5df917a6d2e78cf"
Port `hash`, `hash md5` and `hash sha256` commands (#464) `hash` by itself is only printing the help message. The other two are simply using the same generic implementation.
2021-12-11 00:14:28 +01:00
dependencies = [
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
"cfg-if",
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
"digest",
Port `hash`, `hash md5` and `hash sha256` commands (#464) `hash` by itself is only printing the help message. The other two are simply using the same generic implementation.
2021-12-11 00:14:28 +01:00
]
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
[[package]]
objectshell initial commit
2019-05-10 18:59:12 +02:00
name = "memchr"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "2.6.4"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "f665ee40bc4a3c5590afb1e9677db74a508659dfd71e126420da8274909a0167"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
[[package]]
name = "memmap2"
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
version = "0.7.1"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
checksum = "f49388d20533534cd19360ad3d6a7dadc885944aa802ba3995040c5ec11288c6"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
dependencies = [
"libc",
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
Add hash command with base64 subcommand (#2769) * WIP try testing hash command Ensure test worked fmt WIP get it working for other types of base64 Use optional named arg WIP * rebased and refactored a little with encoding and decoding Fix some typos Add some more charactersets refactor several args into the encoding config struct and fix character_set arg. It needs to match the field Add main hash command so it can be found via help Added tests for running the whole pipeline * add test case to cover invalid character sets * clippy and fmt
2020-11-30 18:47:35 +01:00
[[package]]
name = "memoffset"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.9.0"
Add hash command with base64 subcommand (#2769) * WIP try testing hash command Ensure test worked fmt WIP get it working for other types of base64 Use optional named arg WIP * rebased and refactored a little with encoding and decoding Fix some typos Add some more charactersets refactor several args into the encoding config struct and fix character_set arg. It needs to match the field Add main hash command so it can be found via help Added tests for running the whole pipeline * add test case to cover invalid character sets * clippy and fmt
2020-11-30 18:47:35 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "5a634b1c61a95585bd15607c6ab0c4e5b226e695ff2800ba0cdccddf208c406c"
Add hash command with base64 subcommand (#2769) * WIP try testing hash command Ensure test worked fmt WIP get it working for other types of base64 Use optional named arg WIP * rebased and refactored a little with encoding and decoding Fix some typos Add some more charactersets refactor several args into the encoding config struct and fix character_set arg. It needs to match the field Add main hash command so it can be found via help Added tests for running the whole pipeline * add test case to cover invalid character sets * clippy and fmt
2020-11-30 18:47:35 +01:00
dependencies = [
"autocfg",
]
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
[[package]]
name = "miette"
Bump miette from 5.9.0 to 5.10.0 (#9713)
2023-07-17 08:25:04 +02:00
version = "5.10.0"
deps: bump to miette 3.0 mainline
2021-09-23 01:49:39 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump miette from 5.9.0 to 5.10.0 (#9713)
2023-07-17 08:25:04 +02:00
checksum = "59bb584eaeeab6bd0226ccf3509a69d7936d148cf3d036ad350abe35e8c6856e"
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
dependencies = [
Bump miette from 5.5.0 to 5.6.0 (#8531) Bumps [miette](https://github.com/zkat/miette) from 5.5.0 to 5.6.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zkat/miette/blob/main/CHANGELOG.md">miette's changelog</a>.</em></p> <blockquote> <h2>5.6.0 (2023-03-14)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>ci:</strong> configure clippy-specific MSRV (<a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747">b658fc02</a>)</li> <li><strong>graphical:</strong> Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>) (<a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0">3497508a</a>)</li> <li><strong>atty:</strong> Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>) (<a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e">443d240f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>protocol:</strong> implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>) (<a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d">ed486c95</a>)</li> </ul> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/zkat/miette/commit/78fe18e6990feacc8bdaeeb10e1439a12c111e6e"><code>78fe18e</code></a> chore: Release</li> <li><a href="https://github.com/zkat/miette/commit/2335b25ee7d22bd4ef4e1ef1dd9527fe2accd2be"><code>2335b25</code></a> docs: update changelog</li> <li><a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e"><code>443d240</code></a> fix(atty): Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>)</li> <li><a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d"><code>ed486c9</code></a> feat(protocol): implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>)</li> <li><a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0"><code>3497508</code></a> fix(graphical): Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>)</li> <li><a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747"><code>b658fc0</code></a> fix(ci): configure clippy-specific MSRV</li> <li><a href="https://github.com/zkat/miette/commit/ebc61b5cf809e4215ca92c32d892cfc4ffb05fa9"><code>ebc61b5</code></a> docs: Mention miette::miette! macro under &quot;... in application code&quot; (<a href="https://redirect.github.com/zkat/miette/issues/233">#233</a>)</li> <li><a href="https://github.com/zkat/miette/commit/14f952dc91b9f27b7ae1e9e03b89744bcc682fa2"><code>14f952d</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li><a href="https://github.com/zkat/miette/commit/128c0a1fae0b578b2de5c8967b87df0d89cd1c54"><code>128c0a1</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li>See full diff in <a href="https://github.com/zkat/miette/compare/miette-derive-v5.5.0...miette-derive-v5.6.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=miette&package-manager=cargo&previous-version=5.5.0&new-version=5.6.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-24 10:55:25 +01:00
"is-terminal",
Reduce required dependencies for diagnostics (#6648) Disable backtrace on miette - gimli crate requires several seconds Disable diagnostics on wax - depends on an outdated miette version Builds fine, no observable loss in diagnostics quality of life Removes 10 crates that have to be compiled.
2022-10-24 21:42:32 +02:00
"miette-derive",
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
"once_cell",
"owo-colors",
"supports-color",
"supports-hyperlinks",
"supports-unicode",
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
"terminal_size 0.1.17",
Bump criterion from 0.4.0 to 0.5.1 (#9361)
2023-06-07 15:29:54 +02:00
"textwrap",
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
"thiserror",
more strict nuon handling, better nuon errors (#4576) * more strict nuon handling, better nuon errors * Improve errors a bit more
2022-02-21 04:31:50 +01:00
"unicode-width",
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
]
[[package]]
name = "miette-derive"
Bump miette from 5.9.0 to 5.10.0 (#9713)
2023-07-17 08:25:04 +02:00
version = "5.10.0"
deps: bump to miette 3.0 mainline
2021-09-23 01:49:39 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump miette from 5.9.0 to 5.10.0 (#9713)
2023-07-17 08:25:04 +02:00
checksum = "49e7bc1560b95a3c4a25d03de42fe76ca718ab92d1a22a55b9b4cf67b3ae635c"
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
dependencies = [
"proc-macro2",
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
]
Changes global allocator to mimalloc, improving performance. (#9415) # 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. --> this PR makes nushell use mimalloc as the default allocator, this has the benefit of reducing startup time on my machine. `17%` on linux and `22%` on windows, when testing using hyperfine. the overhead to compile seem to be quite small, aswell as the increase of binary size quite small on linux the binary went from `33.1mb` to `33.2mb` linux ![image](https://github.com/nushell/nushell/assets/17986183/ba5379b4-2c08-483a-a9ff-a9d8524d2943) windows ![image](https://github.com/nushell/nushell/assets/17986183/fda5090f-96a9-48d1-ada4-617694b9d880) # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-15 00:27:12 +02:00
[[package]]
name = "mimalloc"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.1.39"
Changes global allocator to mimalloc, improving performance. (#9415) # 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. --> this PR makes nushell use mimalloc as the default allocator, this has the benefit of reducing startup time on my machine. `17%` on linux and `22%` on windows, when testing using hyperfine. the overhead to compile seem to be quite small, aswell as the increase of binary size quite small on linux the binary went from `33.1mb` to `33.2mb` linux ![image](https://github.com/nushell/nushell/assets/17986183/ba5379b4-2c08-483a-a9ff-a9d8524d2943) windows ![image](https://github.com/nushell/nushell/assets/17986183/fda5090f-96a9-48d1-ada4-617694b9d880) # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-15 00:27:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "fa01922b5ea280a911e323e4d2fd24b7fe5cc4042e0d2cda3c40775cdc4bdc9c"
Changes global allocator to mimalloc, improving performance. (#9415) # 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. --> this PR makes nushell use mimalloc as the default allocator, this has the benefit of reducing startup time on my machine. `17%` on linux and `22%` on windows, when testing using hyperfine. the overhead to compile seem to be quite small, aswell as the increase of binary size quite small on linux the binary went from `33.1mb` to `33.2mb` linux ![image](https://github.com/nushell/nushell/assets/17986183/ba5379b4-2c08-483a-a9ff-a9d8524d2943) windows ![image](https://github.com/nushell/nushell/assets/17986183/fda5090f-96a9-48d1-ada4-617694b9d880) # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-15 00:27:12 +02:00
dependencies = [
"libmimalloc-sys",
]
Port fetch (with fixes) (#660) * Port fetch to engine-q * Fix check for path as a string * Add a timeout flag and fix some span issues * Add a temporary fetch command that returns byte streams. Got rid of async stuff as we're using the blocking feature of tokio * More tweaks for the bytestream * Rewrite fetch using ByteStreams * buffer read on bytes directly Co-authored-by: Stefan Stanciulescu <contact@stefanstanciulescu.com>
2022-01-04 03:01:18 +01:00
[[package]]
name = "mime"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
version = "0.3.17"
Port fetch (with fixes) (#660) * Port fetch to engine-q * Fix check for path as a string * Add a timeout flag and fix some span issues * Add a temporary fetch command that returns byte streams. Got rid of async stuff as we're using the blocking feature of tokio * More tweaks for the bytestream * Rewrite fetch using ByteStreams * buffer read on bytes directly Co-authored-by: Stefan Stanciulescu <contact@stefanstanciulescu.com>
2022-01-04 03:01:18 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
checksum = "6877bb514081ee2a7ff5ef9de3281f14a4dd4bceac4c09388074a6b5df8a139a"
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
add `--mime-type(-m)` to `ls` in the `type` column (#7616) # Description This PR adds the `mime-type` to the `type` column if you add the `--mime-type(-m)` flag to `ls`. <img width="853" alt="Screenshot 2022-12-27 at 11 43 20 AM" src="https://user-images.githubusercontent.com/343840/209705499-27fe40fe-0356-4d9d-97f2-4b2dc52e0963.png"> <img width="781" alt="Screenshot 2022-12-27 at 11 45 53 AM" src="https://user-images.githubusercontent.com/343840/209705509-4d677389-fd68-401e-a7af-3fc6052743b6.png"> # User-Facing Changes If you specify the `-m` flag, you get the "guessed at" mime type. The guess is based on the file name and uses this crate https://docs.rs/mime_guess/latest/mime_guess/ for the guessing. Part of issue #7612 and and #7524 There's some debate on if the `mime-type` should be added to the `type` column or if there should be a separate `mime` column. I tend to lean on the side of `type` since it's technically a type and it's only in that column if you ask it to be there. Also, I'd prefer to reuse a column rather than having a list of sprawling columns. Also, as @KodiCraft suggested, there is precedence as with `ls -d` where the summed size is in the size column. I could go either way and if someone wants to create a `mime` column, we'd probably accept it. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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.
2022-12-27 19:46:23 +01:00
[[package]]
name = "mime_guess"
version = "2.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4192263c238a5f0d0c6bfd21f336a313a4ce1c450542449ca191bb657b4642ef"
dependencies = [
"mime",
"unicase",
]
new `glob` command (#5087)
2022-04-04 22:45:01 +02:00
[[package]]
name = "minimal-lexical"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "68354c5c6bd36d73ff3feceb05efa59b6acb7626617f4962be322a825e61f79a"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
[[package]]
updated cargo.lock with cargo update (#5201)
2022-04-15 13:04:15 +02:00
name = "miniz_oxide"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
version = "0.7.1"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
checksum = "e7810e0be55b428ada41041c41f32c9f1a42817901b4ccf45fa3d4b6561e74c7"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
dependencies = [
updated cargo.lock with cargo update (#5201)
2022-04-15 13:04:15 +02:00
"adler",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
]
corrected history menu (#4814)
2022-03-10 21:58:11 +01:00
[[package]]
name = "mio"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "0.8.10"
corrected history menu (#4814)
2022-03-10 21:58:11 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "8f3d0b296e374a4e6f3c7b0a1f5a51d748a0d34c85e7dc48fc3fa9a87657fe09"
corrected history menu (#4814)
2022-03-10 21:58:11 +01:00
dependencies = [
"libc",
"log",
Don't use `oldtime` feature of chrono (#9577) <!-- 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 `chrono` crate enables `oldtime` feature by default, which has a vulnerability (https://rustsec.org/advisories/RUSTSEC-2020-0071). This PR tries to remove `time` v0.1.45 completely from nu and add an audit CI to check for security vulnerabilities. :hand: Wait for the following PRs: - [x] https://github.com/nushell/reedline/pull/599 - [x] https://github.com/bspeice/dtparse/pull/44 - [x] https://github.com/Byron/trash-rs/pull/75 - [x] https://gitlab.com/imp/chrono-humanize-rs/-/merge_requests/15 # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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. --> --------- Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-25 10:54:01 +02:00
"wasi",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"windows-sys 0.48.0",
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
]
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
[[package]]
name = "mockito"
Bump mockito from 1.1.0 to 1.2.0 (#10407) Bumps [mockito](https://github.com/lipanski/mockito) from 1.1.0 to 1.2.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/lipanski/mockito/releases">mockito's releases</a>.</em></p> <blockquote> <h2>1.2.0</h2> <ul> <li><strong>[Breaking]</strong> The minimum supported Rust version was bumped to 1.68.0</li> <li>The server pool was limited to 20 servers for <code>mac_os</code> targets to prevent hitting the file descriptor limit</li> </ul> <p>Thanks to <a href="https://github.com/kornelski"><code>@​kornelski</code></a></p> <h2>1.1.1</h2> <ul> <li><a href="https://redirect.github.com/lipanski/mockito/pull/176">Ensure</a> <code>with_chunked_body</code> supports streaming responses (as opposed to writing the entire buffer in one go)</li> </ul> <p>Thanks to <a href="https://github.com/kornelski"><code>@​kornelski</code></a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lipanski/mockito/commit/7514e385249b5a71b08b4cdb2fd68638f9e8600a"><code>7514e38</code></a> Bump to 1.2.0</li> <li><a href="https://github.com/lipanski/mockito/commit/be00de417e82f1331632b29acf815fc204cf8302"><code>be00de4</code></a> Merge pull request <a href="https://redirect.github.com/lipanski/mockito/issues/177">#177</a> from kornelski/pool</li> <li><a href="https://github.com/lipanski/mockito/commit/6b4073e911f74a0ec658ad60bb1f92685f34b544"><code>6b4073e</code></a> MSRV</li> <li><a href="https://github.com/lipanski/mockito/commit/9faa8251106b7cadbb5bd5dbc3cc0c5d754cebf6"><code>9faa825</code></a> Test exhausting server pool</li> <li><a href="https://github.com/lipanski/mockito/commit/3099e94471a158c5a8bdf32731db8acc8129d04a"><code>3099e94</code></a> Simplify server pool</li> <li><a href="https://github.com/lipanski/mockito/commit/99735e7c41e279e97cde75f4ccb0a983b015a61c"><code>99735e7</code></a> Bump to 1.1.1</li> <li><a href="https://github.com/lipanski/mockito/commit/3b63970619cc7638e524c3b2e61016f9c931d268"><code>3b63970</code></a> Merge pull request <a href="https://redirect.github.com/lipanski/mockito/issues/176">#176</a> from kornelski/stream</li> <li><a href="https://github.com/lipanski/mockito/commit/339bffc983260162ce371b2d14f9c23c6b21e19d"><code>339bffc</code></a> Support streaming body</li> <li><a href="https://github.com/lipanski/mockito/commit/8b7575cd3842e2dc1b227453ecd99370866dc2c4"><code>8b7575c</code></a> Simplify server pool test</li> <li>See full diff in <a href="https://github.com/lipanski/mockito/compare/1.1.0...1.2.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=mockito&package-manager=cargo&previous-version=1.1.0&new-version=1.2.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-09-18 07:50:08 +02:00
version = "1.2.0"
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump mockito from 1.1.0 to 1.2.0 (#10407) Bumps [mockito](https://github.com/lipanski/mockito) from 1.1.0 to 1.2.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/lipanski/mockito/releases">mockito's releases</a>.</em></p> <blockquote> <h2>1.2.0</h2> <ul> <li><strong>[Breaking]</strong> The minimum supported Rust version was bumped to 1.68.0</li> <li>The server pool was limited to 20 servers for <code>mac_os</code> targets to prevent hitting the file descriptor limit</li> </ul> <p>Thanks to <a href="https://github.com/kornelski"><code>@​kornelski</code></a></p> <h2>1.1.1</h2> <ul> <li><a href="https://redirect.github.com/lipanski/mockito/pull/176">Ensure</a> <code>with_chunked_body</code> supports streaming responses (as opposed to writing the entire buffer in one go)</li> </ul> <p>Thanks to <a href="https://github.com/kornelski"><code>@​kornelski</code></a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lipanski/mockito/commit/7514e385249b5a71b08b4cdb2fd68638f9e8600a"><code>7514e38</code></a> Bump to 1.2.0</li> <li><a href="https://github.com/lipanski/mockito/commit/be00de417e82f1331632b29acf815fc204cf8302"><code>be00de4</code></a> Merge pull request <a href="https://redirect.github.com/lipanski/mockito/issues/177">#177</a> from kornelski/pool</li> <li><a href="https://github.com/lipanski/mockito/commit/6b4073e911f74a0ec658ad60bb1f92685f34b544"><code>6b4073e</code></a> MSRV</li> <li><a href="https://github.com/lipanski/mockito/commit/9faa8251106b7cadbb5bd5dbc3cc0c5d754cebf6"><code>9faa825</code></a> Test exhausting server pool</li> <li><a href="https://github.com/lipanski/mockito/commit/3099e94471a158c5a8bdf32731db8acc8129d04a"><code>3099e94</code></a> Simplify server pool</li> <li><a href="https://github.com/lipanski/mockito/commit/99735e7c41e279e97cde75f4ccb0a983b015a61c"><code>99735e7</code></a> Bump to 1.1.1</li> <li><a href="https://github.com/lipanski/mockito/commit/3b63970619cc7638e524c3b2e61016f9c931d268"><code>3b63970</code></a> Merge pull request <a href="https://redirect.github.com/lipanski/mockito/issues/176">#176</a> from kornelski/stream</li> <li><a href="https://github.com/lipanski/mockito/commit/339bffc983260162ce371b2d14f9c23c6b21e19d"><code>339bffc</code></a> Support streaming body</li> <li><a href="https://github.com/lipanski/mockito/commit/8b7575cd3842e2dc1b227453ecd99370866dc2c4"><code>8b7575c</code></a> Simplify server pool test</li> <li>See full diff in <a href="https://github.com/lipanski/mockito/compare/1.1.0...1.2.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=mockito&package-manager=cargo&previous-version=1.1.0&new-version=1.2.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-09-18 07:50:08 +02:00
checksum = "f8d3038e23466858569c2d30a537f691fa0d53b51626630ae08262943e3bbb8b"
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
dependencies = [
"assert-json-diff",
"futures",
"hyper",
"log",
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"rand",
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
"regex",
"serde_json",
"serde_urlencoded",
"similar",
"tokio",
]
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
[[package]]
name = "multiversion"
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
version = "0.7.3"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
checksum = "b2c7b9d7fe61760ce5ea19532ead98541f6b4c495d87247aff9826445cf6872a"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
dependencies = [
"multiversion-macros",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"target-features",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
]
[[package]]
name = "multiversion-macros"
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
version = "0.7.3"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
checksum = "26a83d8500ed06d68877e9de1dde76c1dbb83885dcdbda4ef44ccbc3fbda2ac8"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
dependencies = [
"proc-macro2",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"quote",
Bump miette from 5.6.0 to 5.7.0 (#8720)
2023-04-06 22:39:54 +02:00
"syn 1.0.109",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"target-features",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
]
Add a --full mode to ps (#1507) * Add a --full mode to ps * Use a slightly older heim
2020-03-20 08:53:49 +01:00
[[package]]
name = "native-tls"
changes Reqwest to Ureq. (#8320) # Description _(Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes.)_ This pull request removes `Reqwest` and replaces it with `Ureq` to remove some of our dependencies, giving us faster compile times as well as smaller binaries. `Ureq` does not have an async runtime included so we do not need build heavy dependencies such as `Tokio`. From older tests I had the number of build units be reduced from `430 -> 392`. The default of `Ureq` uses `Rustls` but it has been configured to instead use `native_tls` which should work exactly the same as the `tls` works now. I removed `content-length` from the http commands as after refactoring i did not see a reason to have it available, correct me if this is something we should preserve. In the medium, to long term, we should maybe consider changing to `rustls` to have the same `tls` on all platforms. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-05 23:48:13 +01:00
version = "0.2.11"
Add a --full mode to ps (#1507) * Add a --full mode to ps * Use a slightly older heim
2020-03-20 08:53:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
changes Reqwest to Ureq. (#8320) # Description _(Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes.)_ This pull request removes `Reqwest` and replaces it with `Ureq` to remove some of our dependencies, giving us faster compile times as well as smaller binaries. `Ureq` does not have an async runtime included so we do not need build heavy dependencies such as `Tokio`. From older tests I had the number of build units be reduced from `430 -> 392`. The default of `Ureq` uses `Rustls` but it has been configured to instead use `native_tls` which should work exactly the same as the `tls` works now. I removed `content-length` from the http commands as after refactoring i did not see a reason to have it available, correct me if this is something we should preserve. In the medium, to long term, we should maybe consider changing to `rustls` to have the same `tls` on all platforms. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-05 23:48:13 +01:00
checksum = "07226173c32f2926027b63cce4bcd8076c3552846cbe7925f3aaffeac0a3b92e"
Add a --full mode to ps (#1507) * Add a --full mode to ps * Use a slightly older heim
2020-03-20 08:53:49 +01:00
dependencies = [
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"lazy_static",
Add a --full mode to ps (#1507) * Add a --full mode to ps * Use a slightly older heim
2020-03-20 08:53:49 +01:00
"libc",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"log",
Add a --full mode to ps (#1507) * Add a --full mode to ps * Use a slightly older heim
2020-03-20 08:53:49 +01:00
"openssl",
"openssl-probe",
"openssl-sys",
"schannel",
"security-framework",
"security-framework-sys",
"tempfile",
]
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
[[package]]
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
name = "new_debug_unreachable"
version = "1.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e4a24736216ec316047a1fc4252e27dabb04218aa4a3f37c6e7ddbf1f9782b54"
upgrade nix to 0.27 (#10223) This fixes a segfault on Android when fetching the user group. See: https://github.com/nix-rust/nix/issues/2084
2023-09-04 22:41:28 +02:00
[[package]]
name = "nix"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.27.1"
upgrade nix to 0.27 (#10223) This fixes a segfault on Android when fetching the user group. See: https://github.com/nix-rust/nix/issues/2084
2023-09-04 22:41:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "2eb04e9c688eff1c89d72b407f168cf79bb9e867a9d3323ed6c01519eb9cc053"
upgrade nix to 0.27 (#10223) This fixes a segfault on Android when fetching the user group. See: https://github.com/nix-rust/nix/issues/2084
2023-09-04 22:41:28 +02:00
dependencies = [
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"bitflags 2.4.1",
upgrade nix to 0.27 (#10223) This fixes a segfault on Android when fetching the user group. See: https://github.com/nix-rust/nix/issues/2084
2023-09-04 22:41:28 +02:00
"cfg-if",
"libc",
]
new `glob` command (#5087)
2022-04-04 22:45:01 +02:00
[[package]]
name = "nom"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "7.1.3"
new `glob` command (#5087)
2022-04-04 22:45:01 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "d273983c5a657a70a3e8f2a01329822f3b8c8172b73826411a55751e404a0a4a"
new `glob` command (#5087)
2022-04-04 22:45:01 +02:00
dependencies = [
"memchr",
"minimal-lexical",
]
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
[[package]]
name = "notify"
Bump notify-debouncer-full from 0.2.0 to 0.3.1 (#10129)
2023-09-01 00:07:41 +02:00
version = "6.1.1"
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump notify-debouncer-full from 0.2.0 to 0.3.1 (#10129)
2023-09-01 00:07:41 +02:00
checksum = "6205bd8bb1e454ad2e27422015fb5e4f2bcc7e08fa8f27058670d208324a4d2d"
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
dependencies = [
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"bitflags 2.4.1",
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"crossbeam-channel",
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
"filetime",
"fsevent-sys",
"inotify",
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"kqueue",
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
"libc",
Bump notify-debouncer-full from 0.2.0 to 0.3.1 (#10129)
2023-09-01 00:07:41 +02:00
"log",
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"mio",
"walkdir",
Bump notify-debouncer-full from 0.2.0 to 0.3.1 (#10129)
2023-09-01 00:07:41 +02:00
"windows-sys 0.48.0",
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
]
[[package]]
name = "notify-debouncer-full"
Bump notify-debouncer-full from 0.2.0 to 0.3.1 (#10129)
2023-09-01 00:07:41 +02:00
version = "0.3.1"
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump notify-debouncer-full from 0.2.0 to 0.3.1 (#10129)
2023-09-01 00:07:41 +02:00
checksum = "49f5dab59c348b9b50cf7f261960a20e389feb2713636399cd9082cd4b536154"
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
dependencies = [
"file-id",
Bump notify-debouncer-full from 0.2.0 to 0.3.1 (#10129)
2023-09-01 00:07:41 +02:00
"log",
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"notify",
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
"parking_lot",
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
"walkdir",
]
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 16:27:37 +01:00
[[package]]
name = "now"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6d89e9874397a1f0a52fc1f197a8effd9735223cb2390e9dcc83ac6cd02923d0"
dependencies = [
"chrono",
]
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
[[package]]
name = "ntapi"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
version = "0.4.1"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
checksum = "e8a3895c6391c39d7fe7ebc444a87eb2991b2a0bc718fdabd071eec617fc68e4"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"winapi",
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
]
Update name
2019-05-17 01:39:58 +02:00
[[package]]
name = "nu"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Add initial nu-test-support port (#913) * Add initial nu-test-support port * finish changing binary name * Oops, these aren't Windows-safe tests
2022-02-02 21:59:01 +01:00
dependencies = [
"assert_cmd",
Add Criterion benchmarks for parser (#7686) This PR sets up [Criterion](https://github.com/bheisler/criterion.rs) for benchmarking in the main `nu` crate, and adds some simple parser benchmarks. To run the benchmarks, just do `cargo bench` or `cargo bench -- <regex matching benchmark names>` in the repo root: ```bash 〉cargo bench -- parse ... Running benches/parser_benchmark.rs (target/release/deps/parser_benchmark-75d224bac82d5b0b) parse_default_env_file time: [221.17 µs 222.34 µs 223.61 µs] Found 8 outliers among 100 measurements (8.00%) 5 (5.00%) high mild 3 (3.00%) high severe parse_default_config_file time: [1.4935 ms 1.4993 ms 1.5059 ms] Found 11 outliers among 100 measurements (11.00%) 7 (7.00%) high mild 4 (4.00%) high severe ``` Existing benchmarks from `nu-plugin` have been moved into the main `nu` crate to keep all our benchmarks in one place.
2023-01-05 20:39:54 +01:00
"criterion",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"crossterm",
Add initial nu-test-support port (#913) * Add initial nu-test-support port * finish changing binary name * Oops, these aren't Windows-safe tests
2022-02-02 21:59:01 +01:00
"ctrlc",
"log",
Reduce required dependencies for diagnostics (#6648) Disable backtrace on miette - gimli crate requires several seconds Disable diagnostics on wax - depends on an outdated miette version Builds fine, no observable loss in diagnostics quality of life Removes 10 crates that have to be compiled.
2022-10-24 21:42:32 +02:00
"miette",
Changes global allocator to mimalloc, improving performance. (#9415) # 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. --> this PR makes nushell use mimalloc as the default allocator, this has the benefit of reducing startup time on my machine. `17%` on linux and `22%` on windows, when testing using hyperfine. the overhead to compile seem to be quite small, aswell as the increase of binary size quite small on linux the binary went from `33.1mb` to `33.2mb` linux ![image](https://github.com/nushell/nushell/assets/17986183/ba5379b4-2c08-483a-a9ff-a9d8524d2943) windows ![image](https://github.com/nushell/nushell/assets/17986183/fda5090f-96a9-48d1-ada4-617694b9d880) # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-15 00:27:12 +02:00
"mimalloc",
rename nushell's cp command to cp-old making coreutils the default cp (#10678) # Description This PR renames nushell's `cp` command to `cp-old` to make room for `ucp` to be renamed to `cp`, making the coreutils version of `cp` the default for nushell. After some period of time, we should remove `cp-old` entirely. # 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-10-11 01:13:28 +02:00
"nix",
Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787) # Description Now use `nu-ansi-term` 0.49 Small adjustments to accommodate breaking changes. # User-Facing Changes None
2023-07-24 13:16:18 +02:00
"nu-ansi-term",
Add initial nu-test-support port (#913) * Add initial nu-test-support port * finish changing binary name * Oops, these aren't Windows-safe tests
2022-02-02 21:59:01 +01:00
"nu-cli",
cratification: move the bytes command to nu-cmd-extra (#9509) now that #9455 has landed we can move the bytes command to nu-cmd-extra in concert with moving nu_command::util to nu-cmd-base
2023-06-23 21:23:08 +02:00
"nu-cmd-base",
move dataframe commands to nu-cmd-dataframe (#9241) All of the dataframe commands ported over with no issues... ### 11 tests are commented out (for now) So 100 of the original 111 tests are passing with only 11 tests being ignored for now.. As per our conversation in the core team meeting on Wednesday I took @jntrnr suggestion and just commented out the tests dealing with [IntoDatetime](https://github.com/nushell/nushell/blob/main/crates/nu-command/src/conversions/into/mod.rs) Later on we can move this functionality out of nu-command if we decide it makes sense... ### The following tests were ignored... ```rust modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_day.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_hour.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_minute.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_month.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_nanosecond.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_ordinal.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_second.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_week.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_weekday.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_year.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/string/strftime.rs ```
2023-05-19 19:56:08 +02:00
"nu-cmd-dataframe",
Break up interdependencies of command crates (#9429) # Description Make sure that our different crates that contain commands can be compiled in parallel. This can under certain circumstances accelerate the compilation with sufficient multithreading available. ## Details - Move `help` commands from `nu-cmd-lang` back to `nu-command` - This also makes sense as the commands are implemented in an ANSI-terminal specific way - Make `nu-cmd-lang` only a dev dependency for `nu-command` - Change context creation helpers for `nu-cmd-extra` and `nu-cmd-dataframe` to have a consistent api used in `src/main.rs`:`get_engine_state()` - `nu-command` now indepedent from `nu-cmd-extra` and `nu-cmd-dataframe` that are now dependencies of `nu` directly. (change to internal features) - Fix tests that previously used `nu-command::create_default_context()` with replacement functions ## From scratch compilation times: just debug (dev) build and default features ``` cargo clean --profile dev && cargo build --timings ``` ### before ![grafik](https://github.com/nushell/nushell/assets/15833959/e49f1f42-2e53-4a6c-bc23-625b686af1bc) ### after ![grafik](https://github.com/nushell/nushell/assets/15833959/8dec4723-e625-4a86-b91e-e6e808f64726) # User-Facing Changes None direct, only change to compilation on multithreaded jobs expected. # Tests + Formatting Tests that previously chose to use `nu-command` for their scope will still use `nu-cmd-lang` + `nu-command` (command list in the granularity at the time)
2023-06-14 23:12:55 +02:00
"nu-cmd-extra",
Cratification: Break out nu_cmd_lang into a separate crate (#8181) # Description This breaks out the core_commands into a separate crate called nu_cmd_lang _(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.)_ # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-02-24 16:54:42 +01:00
"nu-cmd-lang",
Add initial nu-test-support port (#913) * Add initial nu-test-support port * finish changing binary name * Oops, these aren't Windows-safe tests
2022-02-02 21:59:01 +01:00
"nu-color-config",
"nu-command",
"nu-engine",
Move `explore` command out of `nu-command` deps (#9421) # Description For better parallel compilation, make sure that `nu-command` doesn't depend on `nu-explore`. Moves the `nu_protocol::Command` implementation into `nu-explore`. Adds `nu_explore::add_explore_context()` which is used in `main.rs` to add the `explore` command. Minor improvement in compile time ~0.5 sec observed as `nu-command` still blocks on `nu-cmd-lang` as well. ## `cargo build --timings` before ![grafik](https://github.com/nushell/nushell/assets/15833959/583aa56e-6a1e-47b9-ba00-6a86293a38db) ## `cargo build --timings` after ![grafik](https://github.com/nushell/nushell/assets/15833959/30687575-c1c8-4635-bcdd-7ce9488fcfff) # User-Facing Changes None
2023-06-14 01:18:36 +02:00
"nu-explore",
Add initial nu-test-support port (#913) * Add initial nu-test-support port * finish changing binary name * Oops, these aren't Windows-safe tests
2022-02-02 21:59:01 +01:00
"nu-json",
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
"nu-lsp",
Add initial nu-test-support port (#913) * Add initial nu-test-support port * finish changing binary name * Oops, these aren't Windows-safe tests
2022-02-02 21:59:01 +01:00
"nu-parser",
"nu-path",
"nu-plugin",
"nu-pretty-hex",
"nu-protocol",
stdlib: make the library a standalone crate (#8770) # Description as we now have a prelude thanks to #8627, i'd like to work on the structure of the library :yum: and i think the first step is to make it a true standalone crate :smirk: this PR - moves all the library from `crates/nu-utils/standard_library/` to `crates/nu-std/` - moves the `rust` loading code from `src/run.rs` to `crates/nu-std/src/lib.rs`
2023-04-07 22:12:27 +02:00
"nu-std",
Add initial nu-test-support port (#913) * Add initial nu-test-support port * finish changing binary name * Oops, these aren't Windows-safe tests
2022-02-02 21:59:01 +01:00
"nu-system",
"nu-table",
"nu-term-grid",
"nu-test-support",
refactor all write_alls to ensure flushing (#5567)
2022-05-17 20:28:18 +02:00
"nu-utils",
Statically link OpenSSL (#5349)
2022-04-28 02:25:09 +02:00
"openssl",
Add initial nu-test-support port (#913) * Add initial nu-test-support port * finish changing binary name * Oops, these aren't Windows-safe tests
2022-02-02 21:59:01 +01:00
"pretty_assertions",
"reedline",
Bump rstest from 0.17.0 to 0.18.1 (#9782)
2023-08-08 19:11:05 +02:00
"rstest",
Add IDE support (#8745) # Description This adds a set of new flags on the `nu` binary intended for use in IDEs. Here is the set of supported functionality so far: * goto-def - go to the definition of a variable or custom command * type hints - see the inferred type of variables * check - see the errors in the document (currently only one error is supported) * hover - get information about the variable or custom command * complete - get a completion list at the current position # User-Facing Changes No changes to the REPL experience. This only impacts the IDE scenario. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-utils/standard_library/tests.nu` 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. --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-04-05 21:34:47 +02:00
"serde_json",
Add initial nu-test-support port (#913) * Add initial nu-test-support port * finish changing binary name * Oops, these aren't Windows-safe tests
2022-02-02 21:59:01 +01:00
"serial_test",
handle SIGQUIT (#5744) * handle sigquit * fix clippy
2022-06-09 14:08:15 +02:00
"signal-hook",
Replace pretty_env_logger with simplelog (#6274) Fixes #5963 Signed-off-by: nibon7 <nibon7@163.com>
2022-08-09 18:44:37 +02:00
"simplelog",
Add initial nu-test-support port (#913) * Add initial nu-test-support port * finish changing binary name * Oops, these aren't Windows-safe tests
2022-02-02 21:59:01 +01:00
"tempfile",
Don't use `oldtime` feature of chrono (#9577) <!-- 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 `chrono` crate enables `oldtime` feature by default, which has a vulnerability (https://rustsec.org/advisories/RUSTSEC-2020-0071). This PR tries to remove `time` v0.1.45 completely from nu and add an audit CI to check for security vulnerabilities. :hand: Wait for the following PRs: - [x] https://github.com/nushell/reedline/pull/599 - [x] https://github.com/bspeice/dtparse/pull/44 - [x] https://github.com/Byron/trash-rs/pull/75 - [x] https://gitlab.com/imp/chrono-humanize-rs/-/merge_requests/15 # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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. --> --------- Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-25 10:54:01 +02:00
"time",
Move from `winres` to better-maintained `winresource` fork (#9001) This MR closes #8986; big thanks to @WindSoilder for investigating this and making the MR very easy. I did manual testing to confirm that the icon etc. are still being set correctly after this change. Also skimmed the `winresource` code, no issues jumped out at me.
2023-04-26 14:14:55 +02:00
"winresource",
Move most of the root package into a subcrate. (#1445) This improves incremental build time when working on what was previously the root package. For example, previously all plugins would be rebuilt with a change to `src/commands/classified/external.rs`, but now only `nu-cli` will have to be rebuilt (and anything that depends on it).
2020-03-04 19:58:20 +01:00
]
add nu-ansi-term (#3089)
2021-02-22 19:33:34 +01:00
[[package]]
name = "nu-ansi-term"
Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787) # Description Now use `nu-ansi-term` 0.49 Small adjustments to accommodate breaking changes. # User-Facing Changes None
2023-07-24 13:16:18 +02:00
version = "0.49.0"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787) # Description Now use `nu-ansi-term` 0.49 Small adjustments to accommodate breaking changes. # User-Facing Changes None
2023-07-24 13:16:18 +02:00
checksum = "c073d3c1930d0751774acf49e66653acecb416c3a54c6ec095a9b11caddb5a68"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
dependencies = [
"windows-sys 0.48.0",
]
Move most of the root package into a subcrate. (#1445) This improves incremental build time when working on what was previously the root package. For example, previously all plugins would be rebuilt with a change to `src/commands/classified/external.rs`, but now only `nu-cli` will have to be rebuilt (and anything that depends on it).
2020-03-04 19:58:20 +01:00
[[package]]
name = "nu-cli"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
dependencies = [
SQLite History MVP with timestamp, duration, working directory, exit status metadata (#5721) This PR adds support for an SQLite history via nushell/reedline#401 The SQLite history is enabled by setting history_file_format: "sqlite" in config.nu. * somewhat working sqlite history * Hook up history command * Fix error in SQlitebacked with empty lines When entering an empty line there previously was the "No command run" error with `SqliteBackedHistory` during addition of the metadata May be considered a temporary fix Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2022-06-14 22:53:33 +02:00
"chrono",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"crossterm",
Bump `fancy-regex` to single `0.12.0` version (#11389) Supersedes #11039 that was broken due to dependabot not correctly taking the workspace into account (this bug has been worked around in #11387)
2023-12-21 17:10:33 +01:00
"fancy-regex",
Fuzzy completion matching (#5320) * Implement fuzzy match algorithm for suggestions * Use MatchingAlgorithm for custom completions
2022-04-24 23:43:18 +02:00
"fuzzy-matcher",
Add `which` command, add external completions, and builtin var completions (#782) * Add which and external completions * WIP * Finish up external and var completions * fix windows
2022-01-20 19:02:53 +01:00
"is_executable",
Add parser tracing, fix 629 (#638)
2022-01-01 22:42:50 +01:00
"log",
Reduce required dependencies for diagnostics (#6648) Disable backtrace on miette - gimli crate requires several seconds Disable diagnostics on wax - depends on an outdated miette version Builds fine, no observable loss in diagnostics quality of life Removes 10 crates that have to be compiled.
2022-10-24 21:42:32 +02:00
"miette",
Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787) # Description Now use `nu-ansi-term` 0.49 Small adjustments to accommodate breaking changes. # User-Facing Changes None
2023-07-24 13:16:18 +02:00
"nu-ansi-term",
cratification: move the bytes command to nu-cmd-extra (#9509) now that #9455 has landed we can move the bytes command to nu-cmd-extra in concert with moving nu_command::util to nu-cmd-base
2023-06-23 21:23:08 +02:00
"nu-cmd-base",
Break up interdependencies of command crates (#9429) # Description Make sure that our different crates that contain commands can be compiled in parallel. This can under certain circumstances accelerate the compilation with sufficient multithreading available. ## Details - Move `help` commands from `nu-cmd-lang` back to `nu-command` - This also makes sense as the commands are implemented in an ANSI-terminal specific way - Make `nu-cmd-lang` only a dev dependency for `nu-command` - Change context creation helpers for `nu-cmd-extra` and `nu-cmd-dataframe` to have a consistent api used in `src/main.rs`:`get_engine_state()` - `nu-command` now indepedent from `nu-cmd-extra` and `nu-cmd-dataframe` that are now dependencies of `nu` directly. (change to internal features) - Fix tests that previously used `nu-command::create_default_context()` with replacement functions ## From scratch compilation times: just debug (dev) build and default features ``` cargo clean --profile dev && cargo build --timings ``` ### before ![grafik](https://github.com/nushell/nushell/assets/15833959/e49f1f42-2e53-4a6c-bc23-625b686af1bc) ### after ![grafik](https://github.com/nushell/nushell/assets/15833959/8dec4723-e625-4a86-b91e-e6e808f64726) # User-Facing Changes None direct, only change to compilation on multithreaded jobs expected. # Tests + Formatting Tests that previously chose to use `nu-command` for their scope will still use `nu-cmd-lang` + `nu-command` (command list in the granularity at the time)
2023-06-14 23:12:55 +02:00
"nu-cmd-lang",
allow flatshape (command line syntax) theming (#502) * allow flatshape (command line syntax) theming * renamed crate, organized
2021-12-16 13:17:29 +01:00
"nu-color-config",
nu-cli: added tests for file completions (#5232) * nu-cli: added tests for file completions * test adding extra sort * Feature/refactor completion options (#5228) * Copy completion filter to custom completions * Remove filter function from completer This function was a no-op for FileCompletion and CommandCompletion. Flag- and VariableCompletion just filters with `starts_with` which happens in both completers anyway and should therefore also be a no-op. The remaining use case in CustomCompletion was moved into the CustomCompletion source file. Filtering should probably happen immediately while fetching completions to avoid unnecessary memory allocations. * Add get_sort_by() to Completer trait * Remove CompletionOptions from Completer::fetch() * Fix clippy lints * Apply Completer changes to DotNuCompletion * add os to $nu based on rust's understanding (#5243) * add os to $nu based on rust's understanding * add a few more constants Co-authored-by: Richard <Tropid@users.noreply.github.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-04-20 06:54:00 +02:00
"nu-command",
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
"nu-engine",
"nu-parser",
Add path completions
2021-10-04 21:21:31 +02:00
"nu-path",
Add nu-protocol
2021-09-02 03:29:43 +02:00
"nu-protocol",
nu-cli: added tests for file completions (#5232) * nu-cli: added tests for file completions * test adding extra sort * Feature/refactor completion options (#5228) * Copy completion filter to custom completions * Remove filter function from completer This function was a no-op for FileCompletion and CommandCompletion. Flag- and VariableCompletion just filters with `starts_with` which happens in both completers anyway and should therefore also be a no-op. The remaining use case in CustomCompletion was moved into the CustomCompletion source file. Filtering should probably happen immediately while fetching completions to avoid unnecessary memory allocations. * Add get_sort_by() to Completer trait * Remove CompletionOptions from Completer::fetch() * Fix clippy lints * Apply Completer changes to DotNuCompletion * add os to $nu based on rust's understanding (#5243) * add os to $nu based on rust's understanding * add a few more constants Co-authored-by: Richard <Tropid@users.noreply.github.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-04-20 06:54:00 +02:00
"nu-test-support",
added `nu-utils` crate, fixed issue where externals turn off vt processing (#4857) * added `nu-utils` crate, fixed issue where externals turn off vt processing * hopefully make work in non-windows environments * clippy
2022-03-16 23:21:06 +01:00
"nu-utils",
replace lazy_static with once_cell (#7502) replacing the dependence on `lazy_static` with `once_cell`, this will ensure that variables are initialized when needed instead of startup time.
2022-12-17 19:30:04 +01:00
"once_cell",
Fish-like completions for nested directories (#10543) <!-- 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 #5683 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. --> This PR allows tab completion for nested directories while only specifying a part of the directory names. To illustrate this, if I type `tar/de/inc` and hit tab, it autocompletes to `./target/debug/incremental`. # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> Nested paths can be tab completed by typing lesser characters. # 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 > ``` --> Tests cases are added. # 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-10-02 19:44:51 +02:00
"pathdiff",
shell_integration: Report current working directory as OSC 7 (#6481) This is a de-facto standard supported by many terminals, originally added to macOS Terminal.app, now also supported by VTE (GNOME), Konsole (KDE), WezTerm, and more.
2022-09-13 14:36:53 +02:00
"percent-encoding",
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
"reedline",
Bump rstest from 0.17.0 to 0.18.1 (#9782)
2023-08-08 19:11:05 +02:00
"rstest",
update dfr to polars 0.30.0 (#9424) # Description Update the polars dependency for dataframes to stay on-version. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 19:05:45 +02:00
"sysinfo",
Move CLI related commands to `nu-cli` (#8832) # Description Part of the larger cratification effort. Moves all `reedline` or shell line editor specific commands to `nu-cli`. ## From `nu-cmd-lang`: - `commandline` - This shouldn't have moved there. Doesn't directly depend on reedline but assumes parts in the engine state that are specific to the use of reedline or a REPL ## From `nu-command`: - `keybindings` and subcommands - `keybindings default` - `keybindings list` - `keybindings listen` - very `reedline` specific - `history` - needs `reedline` - `history session` ## internal use Instead of having a separate `create_default_context()` that calls `nu-command`'s `create_default_context()`, I added a `add_cli_context()` that updates an `EngineState` # User-Facing Changes None ## Build time comparison `cargo build --timings` from a `cargo clean --profile dev` ### total main: 64 secs this: 59 secs ### `nu-command` build time branch | total| codegen | fraction ---|---|---|--- main | 14.0s | 6.2s | (44%) this | 12.5s | 5.5s | (44%) `nu-cli` depends on `nu-command` at the moment. Thus it is built during the code-gen phase of `nu-command` (on 16 virtual cores) # Tests + Formatting I removed the `test_example()` facilities for now as we had not run any of the commands in an `Example` test and importing the right context for those tests seemed more of a hassle than the duplicated `test_examples()` implementations in `nu-cmd-lang` and `nu-command`
2023-04-10 00:56:47 +02:00
"unicode-segmentation",
Fix editor config for reedline and `config nu/env` (#10535) # Description This merges @horasal 's changes from #10246 and #10269 Closes #10205 Closes #8714 Fixes the bug that editor paths with spaces are unusable Closes #10210 Closes #10269 # User-Facing Changes You can now either pass a string with the name of the executable or a list with the executable and any flags to `$env.config.buffer_editor`/`$env.EDITOR`/`$env.VISUAL` Both the external buffer editor of reedline (by default bound to `Ctrl-o`) and the commands `config nu` and `config env` will respect those variables in the following order: 1. `$env.config.buffer_editor` 2. `$env.EDITOR` 3. `$env.VISUAL` Example: ``` $env.EDITOR = "nvim" # The system-wide EDITOR is neovim $env.config.buffer_editor = ["vim" "-p2"] # Force vim to open two tabs (not particularly useful) $env.config.buffer_editor = null # Unset `buffer_editor` -> Uses `$env.EDITOR` ergo nvim ``` # Tests + Formatting None --------- Co-authored-by: Horasal <1991933+horasal@users.noreply.github.com>
2023-09-29 16:36:03 +02:00
"uuid",
add shape `ExternalResolved` to show found externals via syntax highlighting in the repl (#11135) # Description This PR enables a new feature that shows which externals are found in your path via the syntax highlighter as you type. ![external_resolved](https://github.com/nushell/nushell/assets/343840/e5fa91f0-6fac-485c-8afc-5711fc0ed9bc) This idea could use some improvement where it caches the items in your path and on some trigger, expires that cache and creates a new on. Right now, all it does is call the `which` crate on every character you type. This could be problematic if you have hundreds of paths in your PATH or if some of your paths in your Path point to extraordinarily slow file systems. WSL pointing to Windows comes to mind. Either way, I've thrown it up here for people to try and provide feedback. I think the novelty of showing what is valid and what isn't is pretty cool. I believe fish-shell also does this, IIRC. # 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-11-25 16:42:05 +01:00
"which 5.0.0",
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
]
move common tools from `nu-command` to `nu-cmd-base` (#9455) related to - https://github.com/nushell/nushell/pull/9404 # Description to support our cratification effort and moving non-1.0 commands outside of the main focus, this PR - creates a new `nu-cmd-base` crate to hold the common structs, traits and functions used by all command-related crates - to start the transition, moves the `input_handler` module from `nu-command` to `nu-cmd-base` # User-Facing Changes ``` $nothing ``` # Tests + Formatting - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # After Submitting ``` $nothing ```
2023-06-22 23:45:54 +02:00
[[package]]
name = "nu-cmd-base"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
move common tools from `nu-command` to `nu-cmd-base` (#9455) related to - https://github.com/nushell/nushell/pull/9404 # Description to support our cratification effort and moving non-1.0 commands outside of the main focus, this PR - creates a new `nu-cmd-base` crate to hold the common structs, traits and functions used by all command-related crates - to start the transition, moves the `input_handler` module from `nu-command` to `nu-cmd-base` # User-Facing Changes ``` $nothing ``` # Tests + Formatting - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # After Submitting ``` $nothing ```
2023-06-22 23:45:54 +02:00
dependencies = [
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"indexmap",
Move `eval_hook` to `nu-cmd-base` (#10146) I moved hook to *nu_cmd_base* instead of *nu_cli* because it will enable other developers to continue to use hook even if they decide to write their on cli or NOT depend on nu-cli Then they will still have the hook functionality because they can include nu-cmd-base
2023-08-29 23:46:50 +02:00
"miette",
cratification: move the bytes command to nu-cmd-extra (#9509) now that #9455 has landed we can move the bytes command to nu-cmd-extra in concert with moving nu_command::util to nu-cmd-base
2023-06-23 21:23:08 +02:00
"nu-engine",
Allow filesystem commands to access files with glob metachars in name (#10694) (squashed version of #10557, clean commit history and review thread) Fixes #10571, also potentially: #10364, #10211, #9558, #9310, # Description Changes processing of arguments to filesystem commands that are source paths or globs. Applies to `cp, cp-old, mv, rm, du` but not `ls` (because it uses a different globbing interface) or `glob` (because it uses a different globbing library). The core of the change is to lookup the argument first as a file and only glob if it is not. That way, a path containing glob metacharacters can be referenced without glob quoting, though it will have to be single quoted to avoid nushell parsing. Before: A file path that looks like a glob is not matched by the glob specified as a (source) argument and takes some thinking about to access. You might say the glob pattern shadows a file with the same spelling. ``` > ls a* ╭───┬────────┬──────┬──────┬────────────────╮ │ # │ name │ type │ size │ modified │ ├───┼────────┼──────┼──────┼────────────────┤ │ 0 │ a[bc]d │ file │ 0 B │ 34 seconds ago │ │ 1 │ abd │ file │ 0 B │ now │ │ 2 │ acd │ file │ 0 B │ now │ ╰───┴────────┴──────┴──────┴────────────────╯ > cp --verbose 'a[bc]d' dest copied /home/bobhy/src/rust/work/r4/abd to /home/bobhy/src/rust/work/r4/dest/abd copied /home/bobhy/src/rust/work/r4/acd to /home/bobhy/src/rust/work/r4/dest/acd > ## Note -- a[bc]d *not* copied, and seemingly hard to access. > cp --verbose 'a\[bc\]d' dest Error: × No matches found ╭─[entry #33:1:1] 1 │ cp --verbose 'a\[bc\]d' dest · ─────┬──── · ╰── no matches found ╰──── > #.. but is accessible with enough glob quoting. > cp --verbose 'a[[]bc[]]d' dest copied /home/bobhy/src/rust/work/r4/a[bc]d to /home/bobhy/src/rust/work/r4/dest/a[bc]d ``` Before_2: if file has glob metachars but isn't a valid pattern, user gets a confusing error: ``` > touch 'a[b' > cp 'a[b' dest Error: × Pattern syntax error near position 30: invalid range pattern ╭─[entry #13:1:1] 1 │ cp 'a[b' dest · ──┬── · ╰── invalid pattern ╰──── ``` After: Args to cp, mv, etc. are tried first as literal files, and only as globs if not found to be files. ``` > cp --verbose 'a[bc]d' dest copied /home/bobhy/src/rust/work/r4/a[bc]d to /home/bobhy/src/rust/work/r4/dest/a[bc]d > cp --verbose '[a][bc]d' dest copied /home/bobhy/src/rust/work/r4/abd to /home/bobhy/src/rust/work/r4/dest/abd copied /home/bobhy/src/rust/work/r4/acd to /home/bobhy/src/rust/work/r4/dest/acd ``` After_2: file with glob metachars but invalid pattern just works. (though Windows does not allow file name to contain `*`.). ``` > cp --verbose 'a[b' dest copied /home/bobhy/src/rust/work/r4/a[b to /home/bobhy/src/rust/work/r4/dest/a[b ``` So, with this fix, a file shadows a glob pattern with the same spelling. If you have such a file and really want to use the glob pattern, you will have to glob quote some of the characters in the pattern. I think that's less confusing to the user: if ls shows a file with a weird name, s/he'll still be able to copy, rename or delete it. # User-Facing Changes Could break some existing scripts. If user happened to have a file with a globbish name but was using a glob pattern with the same spelling, the new version will process the file and not expand the glob. # 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-10-18 20:31:15 +02:00
"nu-glob",
Move `eval_hook` to `nu-cmd-base` (#10146) I moved hook to *nu_cmd_base* instead of *nu_cli* because it will enable other developers to continue to use hook even if they decide to write their on cli or NOT depend on nu-cli Then they will still have the hook functionality because they can include nu-cmd-base
2023-08-29 23:46:50 +02:00
"nu-parser",
cratification: move the bytes command to nu-cmd-extra (#9509) now that #9455 has landed we can move the bytes command to nu-cmd-extra in concert with moving nu_command::util to nu-cmd-base
2023-06-23 21:23:08 +02:00
"nu-path",
move common tools from `nu-command` to `nu-cmd-base` (#9455) related to - https://github.com/nushell/nushell/pull/9404 # Description to support our cratification effort and moving non-1.0 commands outside of the main focus, this PR - creates a new `nu-cmd-base` crate to hold the common structs, traits and functions used by all command-related crates - to start the transition, moves the `input_handler` module from `nu-command` to `nu-cmd-base` # User-Facing Changes ``` $nothing ``` # Tests + Formatting - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # After Submitting ``` $nothing ```
2023-06-22 23:45:54 +02:00
"nu-protocol",
Allow filesystem commands to access files with glob metachars in name (#10694) (squashed version of #10557, clean commit history and review thread) Fixes #10571, also potentially: #10364, #10211, #9558, #9310, # Description Changes processing of arguments to filesystem commands that are source paths or globs. Applies to `cp, cp-old, mv, rm, du` but not `ls` (because it uses a different globbing interface) or `glob` (because it uses a different globbing library). The core of the change is to lookup the argument first as a file and only glob if it is not. That way, a path containing glob metacharacters can be referenced without glob quoting, though it will have to be single quoted to avoid nushell parsing. Before: A file path that looks like a glob is not matched by the glob specified as a (source) argument and takes some thinking about to access. You might say the glob pattern shadows a file with the same spelling. ``` > ls a* ╭───┬────────┬──────┬──────┬────────────────╮ │ # │ name │ type │ size │ modified │ ├───┼────────┼──────┼──────┼────────────────┤ │ 0 │ a[bc]d │ file │ 0 B │ 34 seconds ago │ │ 1 │ abd │ file │ 0 B │ now │ │ 2 │ acd │ file │ 0 B │ now │ ╰───┴────────┴──────┴──────┴────────────────╯ > cp --verbose 'a[bc]d' dest copied /home/bobhy/src/rust/work/r4/abd to /home/bobhy/src/rust/work/r4/dest/abd copied /home/bobhy/src/rust/work/r4/acd to /home/bobhy/src/rust/work/r4/dest/acd > ## Note -- a[bc]d *not* copied, and seemingly hard to access. > cp --verbose 'a\[bc\]d' dest Error: × No matches found ╭─[entry #33:1:1] 1 │ cp --verbose 'a\[bc\]d' dest · ─────┬──── · ╰── no matches found ╰──── > #.. but is accessible with enough glob quoting. > cp --verbose 'a[[]bc[]]d' dest copied /home/bobhy/src/rust/work/r4/a[bc]d to /home/bobhy/src/rust/work/r4/dest/a[bc]d ``` Before_2: if file has glob metachars but isn't a valid pattern, user gets a confusing error: ``` > touch 'a[b' > cp 'a[b' dest Error: × Pattern syntax error near position 30: invalid range pattern ╭─[entry #13:1:1] 1 │ cp 'a[b' dest · ──┬── · ╰── invalid pattern ╰──── ``` After: Args to cp, mv, etc. are tried first as literal files, and only as globs if not found to be files. ``` > cp --verbose 'a[bc]d' dest copied /home/bobhy/src/rust/work/r4/a[bc]d to /home/bobhy/src/rust/work/r4/dest/a[bc]d > cp --verbose '[a][bc]d' dest copied /home/bobhy/src/rust/work/r4/abd to /home/bobhy/src/rust/work/r4/dest/abd copied /home/bobhy/src/rust/work/r4/acd to /home/bobhy/src/rust/work/r4/dest/acd ``` After_2: file with glob metachars but invalid pattern just works. (though Windows does not allow file name to contain `*`.). ``` > cp --verbose 'a[b' dest copied /home/bobhy/src/rust/work/r4/a[b to /home/bobhy/src/rust/work/r4/dest/a[b ``` So, with this fix, a file shadows a glob pattern with the same spelling. If you have such a file and really want to use the glob pattern, you will have to glob quote some of the characters in the pattern. I think that's less confusing to the user: if ls shows a file with a weird name, s/he'll still be able to copy, rename or delete it. # User-Facing Changes Could break some existing scripts. If user happened to have a file with a globbish name but was using a glob pattern with the same spelling, the new version will process the file and not expand the glob. # 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-10-18 20:31:15 +02:00
"nu-test-support",
"nu-utils",
"rstest",
move common tools from `nu-command` to `nu-cmd-base` (#9455) related to - https://github.com/nushell/nushell/pull/9404 # Description to support our cratification effort and moving non-1.0 commands outside of the main focus, this PR - creates a new `nu-cmd-base` crate to hold the common structs, traits and functions used by all command-related crates - to start the transition, moves the `input_handler` module from `nu-command` to `nu-cmd-base` # User-Facing Changes ``` $nothing ``` # Tests + Formatting - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # After Submitting ``` $nothing ```
2023-06-22 23:45:54 +02:00
]
move dataframe commands to nu-cmd-dataframe (#9241) All of the dataframe commands ported over with no issues... ### 11 tests are commented out (for now) So 100 of the original 111 tests are passing with only 11 tests being ignored for now.. As per our conversation in the core team meeting on Wednesday I took @jntrnr suggestion and just commented out the tests dealing with [IntoDatetime](https://github.com/nushell/nushell/blob/main/crates/nu-command/src/conversions/into/mod.rs) Later on we can move this functionality out of nu-command if we decide it makes sense... ### The following tests were ignored... ```rust modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_day.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_hour.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_minute.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_month.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_nanosecond.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_ordinal.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_second.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_week.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_weekday.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_year.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/string/strftime.rs ```
2023-05-19 19:56:08 +02:00
[[package]]
name = "nu-cmd-dataframe"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
move dataframe commands to nu-cmd-dataframe (#9241) All of the dataframe commands ported over with no issues... ### 11 tests are commented out (for now) So 100 of the original 111 tests are passing with only 11 tests being ignored for now.. As per our conversation in the core team meeting on Wednesday I took @jntrnr suggestion and just commented out the tests dealing with [IntoDatetime](https://github.com/nushell/nushell/blob/main/crates/nu-command/src/conversions/into/mod.rs) Later on we can move this functionality out of nu-command if we decide it makes sense... ### The following tests were ignored... ```rust modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_day.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_hour.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_minute.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_month.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_nanosecond.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_ordinal.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_second.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_week.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_weekday.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_year.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/string/strftime.rs ```
2023-05-19 19:56:08 +02:00
dependencies = [
"chrono",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"chrono-tz",
Bump `fancy-regex` to single `0.12.0` version (#11389) Supersedes #11039 that was broken due to dependabot not correctly taking the workspace into account (this bug has been worked around in #11387)
2023-12-21 17:10:33 +01:00
"fancy-regex",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"indexmap",
move dataframe commands to nu-cmd-dataframe (#9241) All of the dataframe commands ported over with no issues... ### 11 tests are commented out (for now) So 100 of the original 111 tests are passing with only 11 tests being ignored for now.. As per our conversation in the core team meeting on Wednesday I took @jntrnr suggestion and just commented out the tests dealing with [IntoDatetime](https://github.com/nushell/nushell/blob/main/crates/nu-command/src/conversions/into/mod.rs) Later on we can move this functionality out of nu-command if we decide it makes sense... ### The following tests were ignored... ```rust modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_day.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_hour.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_minute.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_month.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_nanosecond.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_ordinal.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_second.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_week.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_weekday.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_year.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/string/strftime.rs ```
2023-05-19 19:56:08 +02:00
"nu-cmd-lang",
"nu-engine",
"nu-parser",
"nu-protocol",
"nu-test-support",
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
"num 0.4.1",
move dataframe commands to nu-cmd-dataframe (#9241) All of the dataframe commands ported over with no issues... ### 11 tests are commented out (for now) So 100 of the original 111 tests are passing with only 11 tests being ignored for now.. As per our conversation in the core team meeting on Wednesday I took @jntrnr suggestion and just commented out the tests dealing with [IntoDatetime](https://github.com/nushell/nushell/blob/main/crates/nu-command/src/conversions/into/mod.rs) Later on we can move this functionality out of nu-command if we decide it makes sense... ### The following tests were ignored... ```rust modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_day.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_hour.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_minute.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_month.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_nanosecond.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_ordinal.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_second.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_week.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_weekday.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_year.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/string/strftime.rs ```
2023-05-19 19:56:08 +02:00
"polars",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"polars-arrow",
Expose polars avro support (#10019) # Description Exposes polars avro support via dfr open and dfr to-avro --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-08-16 03:31:49 +02:00
"polars-io",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"polars-ops",
"polars-plan",
move dataframe commands to nu-cmd-dataframe (#9241) All of the dataframe commands ported over with no issues... ### 11 tests are commented out (for now) So 100 of the original 111 tests are passing with only 11 tests being ignored for now.. As per our conversation in the core team meeting on Wednesday I took @jntrnr suggestion and just commented out the tests dealing with [IntoDatetime](https://github.com/nushell/nushell/blob/main/crates/nu-command/src/conversions/into/mod.rs) Later on we can move this functionality out of nu-command if we decide it makes sense... ### The following tests were ignored... ```rust modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_day.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_hour.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_minute.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_month.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_nanosecond.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_ordinal.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_second.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_week.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_weekday.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_year.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/string/strftime.rs ```
2023-05-19 19:56:08 +02:00
"serde",
update sqlparser dep to 0.34 (#9549) # Description This PR updates the sqlparser dep to 0.34.0. closes #9525 # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-28 16:54:08 +02:00
"sqlparser",
move dataframe commands to nu-cmd-dataframe (#9241) All of the dataframe commands ported over with no issues... ### 11 tests are commented out (for now) So 100 of the original 111 tests are passing with only 11 tests being ignored for now.. As per our conversation in the core team meeting on Wednesday I took @jntrnr suggestion and just commented out the tests dealing with [IntoDatetime](https://github.com/nushell/nushell/blob/main/crates/nu-command/src/conversions/into/mod.rs) Later on we can move this functionality out of nu-command if we decide it makes sense... ### The following tests were ignored... ```rust modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_day.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_hour.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_minute.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_month.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_nanosecond.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_ordinal.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_second.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_week.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_weekday.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/date/get_year.rs modified: crates/nu-cmd-dataframe/src/dataframe/series/string/strftime.rs ```
2023-05-19 19:56:08 +02:00
]
nu-cmd-extra crate infrastructure in place with the Bits command as the model for adding other commands (#9327) I wanted to get the infrastructure in place for starters for our *nu-cmd-extra* crate... The plan is to put inside here the following commands... * bits * bytes * math I thought it would be easier to do one at a time as well as get the nu-cmd-extra crate out there on crates.io for this upcoming release... Once this lands the infrastructure will be in place to move over the other noted commands for now... And then add other stuff we do NOT want to be in 1.0.
2023-06-01 19:46:16 +02:00
[[package]]
name = "nu-cmd-extra"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
nu-cmd-extra crate infrastructure in place with the Bits command as the model for adding other commands (#9327) I wanted to get the infrastructure in place for starters for our *nu-cmd-extra* crate... The plan is to put inside here the following commands... * bits * bytes * math I thought it would be easier to do one at a time as well as get the nu-cmd-extra crate out there on crates.io for this upcoming release... Once this lands the infrastructure will be in place to move over the other noted commands for now... And then add other stuff we do NOT want to be in 1.0.
2023-06-01 19:46:16 +02:00
dependencies = [
Update `unicode-linebreak` to `0.1.5` (#9814) # Description This deduplicates `ahash` as it was previously an outdated build-dependency of `unicode-linebreak` Should provide a small benefit to initial from scratch compile. # User-Facing Changes None
2023-07-30 22:17:36 +02:00
"ahash",
Bump `fancy-regex` to single `0.12.0` version (#11389) Supersedes #11039 that was broken due to dependabot not correctly taking the workspace into account (this bug has been worked around in #11387)
2023-12-21 17:10:33 +01:00
"fancy-regex",
Use `heck` for string casing (again) (#10680) Re-fixes #3674, if that is seen as desirable to do. # Description This PR changes the implementation of the `--features=extra` string casing commands from Inflector to `heck`, as in PR #4081. This PR landed a long time ago, but somewhere along the way (i can't find it) the implementation ended up being switched back to Inflector. # User-Facing Changes Inflector and `heck` implement casing differently, so all of the commands have different behavior around edge cases (consecutive capitals, interspersed numbers and letters, etc) ### Before ```nu G:/Dev/nu-itself/nushell> [UserID ABCdefGHI foo123bar] | str camel-case ╭───┬───────────╮ │ 0 │ userID │ │ 1 │ abcdefGHI │ │ 2 │ foo123Bar │ ╰───┴───────────╯ G:/Dev/nu-itself/nushell> [UserID ABCdefGHI foo123bar] | str snake-case ╭───┬─────────────╮ │ 0 │ user_id │ │ 1 │ ab_cdef_ghi │ │ 2 │ foo_12_3bar │ ╰───┴─────────────╯ ``` ### After ```nu G:/Dev/nu-itself/nushell> [UserID ABCdefGHI foo123bar] | str camel-case ╭───┬───────────╮ │ 0 │ userId │ │ 1 │ abCdefGhi │ │ 2 │ foo123bar │ ╰───┴───────────╯ G:/Dev/nu-itself/nushell> [UserID ABCdefGHI foo123bar] | str snake-case ╭───┬─────────────╮ │ 0 │ user_id │ │ 1 │ ab_cdef_ghi │ │ 2 │ foo123bar │ ╰───┴─────────────╯ ``` # Tests + Formatting The existing string casing tests pass... because none of them relied on any of these edge cases
2023-10-13 12:52:35 +02:00
"heck",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"htmlescape",
Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787) # Description Now use `nu-ansi-term` 0.49 Small adjustments to accommodate breaking changes. # User-Facing Changes None
2023-07-24 13:16:18 +02:00
"nu-ansi-term",
cratification: move the bytes command to nu-cmd-extra (#9509) now that #9455 has landed we can move the bytes command to nu-cmd-extra in concert with moving nu_command::util to nu-cmd-base
2023-06-23 21:23:08 +02:00
"nu-cmd-base",
nu-cmd-extra crate infrastructure in place with the Bits command as the model for adding other commands (#9327) I wanted to get the infrastructure in place for starters for our *nu-cmd-extra* crate... The plan is to put inside here the following commands... * bits * bytes * math I thought it would be easier to do one at a time as well as get the nu-cmd-extra crate out there on crates.io for this upcoming release... Once this lands the infrastructure will be in place to move over the other noted commands for now... And then add other stuff we do NOT want to be in 1.0.
2023-06-01 19:46:16 +02:00
"nu-cmd-lang",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"nu-command",
nu-cmd-extra crate infrastructure in place with the Bits command as the model for adding other commands (#9327) I wanted to get the infrastructure in place for starters for our *nu-cmd-extra* crate... The plan is to put inside here the following commands... * bits * bytes * math I thought it would be easier to do one at a time as well as get the nu-cmd-extra crate out there on crates.io for this upcoming release... Once this lands the infrastructure will be in place to move over the other noted commands for now... And then add other stuff we do NOT want to be in 1.0.
2023-06-01 19:46:16 +02:00
"nu-engine",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"nu-json",
nu-cmd-extra crate infrastructure in place with the Bits command as the model for adding other commands (#9327) I wanted to get the infrastructure in place for starters for our *nu-cmd-extra* crate... The plan is to put inside here the following commands... * bits * bytes * math I thought it would be easier to do one at a time as well as get the nu-cmd-extra crate out there on crates.io for this upcoming release... Once this lands the infrastructure will be in place to move over the other noted commands for now... And then add other stuff we do NOT want to be in 1.0.
2023-06-01 19:46:16 +02:00
"nu-parser",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"nu-pretty-hex",
nu-cmd-extra crate infrastructure in place with the Bits command as the model for adding other commands (#9327) I wanted to get the infrastructure in place for starters for our *nu-cmd-extra* crate... The plan is to put inside here the following commands... * bits * bytes * math I thought it would be easier to do one at a time as well as get the nu-cmd-extra crate out there on crates.io for this upcoming release... Once this lands the infrastructure will be in place to move over the other noted commands for now... And then add other stuff we do NOT want to be in 1.0.
2023-06-01 19:46:16 +02:00
"nu-protocol",
"nu-test-support",
cratification: move the bytes command to nu-cmd-extra (#9509) now that #9455 has landed we can move the bytes command to nu-cmd-extra in concert with moving nu_command::util to nu-cmd-base
2023-06-23 21:23:08 +02:00
"nu-utils",
nu-cmd-extra crate infrastructure in place with the Bits command as the model for adding other commands (#9327) I wanted to get the infrastructure in place for starters for our *nu-cmd-extra* crate... The plan is to put inside here the following commands... * bits * bytes * math I thought it would be easier to do one at a time as well as get the nu-cmd-extra crate out there on crates.io for this upcoming release... Once this lands the infrastructure will be in place to move over the other noted commands for now... And then add other stuff we do NOT want to be in 1.0.
2023-06-01 19:46:16 +02:00
"num-traits",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"rust-embed",
"serde",
"serde_urlencoded",
nu-cmd-extra crate infrastructure in place with the Bits command as the model for adding other commands (#9327) I wanted to get the infrastructure in place for starters for our *nu-cmd-extra* crate... The plan is to put inside here the following commands... * bits * bytes * math I thought it would be easier to do one at a time as well as get the nu-cmd-extra crate out there on crates.io for this upcoming release... Once this lands the infrastructure will be in place to move over the other noted commands for now... And then add other stuff we do NOT want to be in 1.0.
2023-06-01 19:46:16 +02:00
]
Cratification: Break out nu_cmd_lang into a separate crate (#8181) # Description This breaks out the core_commands into a separate crate called nu_cmd_lang _(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.)_ # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-02-24 16:54:42 +01:00
[[package]]
name = "nu-cmd-lang"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Cratification: Break out nu_cmd_lang into a separate crate (#8181) # Description This breaks out the core_commands into a separate crate called nu_cmd_lang _(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.)_ # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-02-24 16:54:42 +01:00
dependencies = [
Bump `fancy-regex` to single `0.12.0` version (#11389) Supersedes #11039 that was broken due to dependabot not correctly taking the workspace into account (this bug has been worked around in #11387)
2023-12-21 17:10:33 +01:00
"fancy-regex",
Bump itertools from 0.11.0 to 0.12.0 (#11360) Bumps [itertools](https://github.com/rust-itertools/itertools) from 0.11.0 to 0.12.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rust-itertools/itertools/blob/master/CHANGELOG.md">itertools's changelog</a>.</em></p> <blockquote> <h2>0.12.0</h2> <h3>Breaking</h3> <ul> <li>Made <code>take_while_inclusive</code> consume iterator by value (<a href="https://redirect.github.com/rust-itertools/itertools/issues/709">#709</a>)</li> <li>Added <code>Clone</code> bound to <code>Unique</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/777">#777</a>)</li> </ul> <h3>Added</h3> <ul> <li>Added <code>Itertools::try_len</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/723">#723</a>)</li> <li>Added free function <code>sort_unstable</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/796">#796</a>)</li> <li>Added <code>GroupMap::fold_with</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/778">#778</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/785">#785</a>)</li> <li>Added <code>PeekNth::{peek_mut, peek_nth_mut}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/716">#716</a>)</li> <li>Added <code>PeekNth::{next_if, next_if_eq}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/734">#734</a>)</li> <li>Added conversion into <code>(Option&lt;A&gt;,Option&lt;B&gt;)</code> to <code>EitherOrBoth</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/713">#713</a>)</li> <li>Added conversion from <code>Either&lt;A, B&gt;</code> to <code>EitherOrBoth&lt;A, B&gt;</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/715">#715</a>)</li> <li>Implemented <code>ExactSizeIterator</code> for <code>Tuples</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/761">#761</a>)</li> <li>Implemented <code>ExactSizeIterator</code> for <code>(Circular)TupleWindows</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/752">#752</a>)</li> <li>Made <code>EitherOrBoth&lt;T&gt;</code> a shorthand for <code>EitherOrBoth&lt;T, T&gt;</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/719">#719</a>)</li> </ul> <h3>Changed</h3> <ul> <li>Added missing <code>#[must_use]</code> annotations on iterator adaptors (<a href="https://redirect.github.com/rust-itertools/itertools/issues/794">#794</a>)</li> <li>Made <code>Combinations</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/795">#795</a>)</li> <li>Made <code>Intersperse(With)</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/797">#797</a>)</li> <li>Made <code>Permutations</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/793">#793</a>)</li> <li>Made <code>Product</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/800">#800</a>)</li> <li>Made <code>TupleWindows</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/602">#602</a>)</li> <li>Specialized <code>Combinations::{count, size_hint}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/729">#729</a>)</li> <li>Specialized <code>CombinationsWithReplacement::{count, size_hint}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/737">#737</a>)</li> <li>Specialized <code>Powerset::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/765">#765</a>)</li> <li>Specialized <code>Powerset::count</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/735">#735</a>)</li> <li>Specialized <code>TupleCombinations::{count, size_hint}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/763">#763</a>)</li> <li>Specialized <code>TupleCombinations::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/775">#775</a>)</li> <li>Specialized <code>WhileSome::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/780">#780</a>)</li> <li>Specialized <code>WithPosition::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/772">#772</a>)</li> <li>Specialized <code>ZipLongest::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/774">#774</a>)</li> <li>Changed <code>{min, max}_set*</code> operations require <code>alloc</code> feature, instead of <code>std</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/760">#760</a>)</li> <li>Improved documentation of <code>tree_fold1</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/787">#787</a>)</li> <li>Improved documentation of <code>permutations</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/724">#724</a>)</li> <li>Fixed typo in documentation of <code>multiunzip</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/770">#770</a>)</li> </ul> <h3>Notable Internal Changes</h3> <ul> <li>Improved specialization tests (<a href="https://redirect.github.com/rust-itertools/itertools/issues/799">#799</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/786">#786</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/782">#782</a>)</li> <li>Simplified implementation of <code>Permutations</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/739">#739</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/748">#748</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/790">#790</a>)</li> <li>Combined <code>Merge</code>/<code>MergeBy</code>/<code>MergeJoinBy</code> implementations (<a href="https://redirect.github.com/rust-itertools/itertools/issues/736">#736</a>)</li> <li>Simplified <code>Permutations::size_hint</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/739">#739</a>)</li> <li>Fix wrapping arithmetic in benchmarks (<a href="https://redirect.github.com/rust-itertools/itertools/issues/770">#770</a>)</li> <li>Enforced <code>rustfmt</code> in CI (<a href="https://redirect.github.com/rust-itertools/itertools/issues/751">#751</a>)</li> <li>Disallowed compile warnings in CI (<a href="https://redirect.github.com/rust-itertools/itertools/issues/720">#720</a>)</li> <li>Used <code>cargo hack</code> to check MSRV (<a href="https://redirect.github.com/rust-itertools/itertools/issues/754">#754</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rust-itertools/itertools/commit/98ecabb47d7147dae06fc3fa400ec758947194f3"><code>98ecabb</code></a> chore: Release itertools version 0.12.0</li> <li><a href="https://github.com/rust-itertools/itertools/commit/22fc427ac5282cbdafccfe38a686ec1d3b720120"><code>22fc427</code></a> prepare v0.12.0 release</li> <li><a href="https://github.com/rust-itertools/itertools/commit/6d291786a9c9686a3997d93c513bd18326611fe5"><code>6d29178</code></a> Document the field <code>a_cur</code> of <code>Product</code></li> <li><a href="https://github.com/rust-itertools/itertools/commit/bf2b0129d1d3cc1ffa733059f3088adb6d745fe6"><code>bf2b012</code></a> Better <code>Product::size_hint</code></li> <li><a href="https://github.com/rust-itertools/itertools/commit/8d07f6b8566a515118ca8b119f358b73d483152b"><code>8d07f6b</code></a> Make <code>Product</code> lazy</li> <li><a href="https://github.com/rust-itertools/itertools/commit/d7e6bab9fd0ad79130692f8e48e21375362a7614"><code>d7e6bab</code></a> Document the field <code>peek</code> of <code>IntersperseWith</code></li> <li><a href="https://github.com/rust-itertools/itertools/commit/9b01a118919f0d1f7c3327d1a15a5eb660f3912e"><code>9b01a11</code></a> Make <code>IntersperseWith</code> lazy</li> <li><a href="https://github.com/rust-itertools/itertools/commit/4f22173b93a2eb58da16b7da6d08e6c3f1c56544"><code>4f22173</code></a> Refactor <code>IntersperseWith::next</code></li> <li><a href="https://github.com/rust-itertools/itertools/commit/b76172b412116356ebef05b884a6e4def63a4d17"><code>b76172b</code></a> chore: adjust docs to reflect discussion in the PR</li> <li><a href="https://github.com/rust-itertools/itertools/commit/955927f6c424f895ad7519d413bc5718e6ad26bf"><code>955927f</code></a> chore: fixup docs of tree_fold1</li> <li>Additional commits viewable in <a href="https://github.com/rust-itertools/itertools/compare/v0.11.0...v0.12.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=itertools&package-manager=cargo&previous-version=0.11.0&new-version=0.12.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-12-20 15:58:07 +01:00
"itertools 0.12.0",
Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787) # Description Now use `nu-ansi-term` 0.49 Small adjustments to accommodate breaking changes. # User-Facing Changes None
2023-07-24 13:16:18 +02:00
"nu-ansi-term",
Cratification: Break out nu_cmd_lang into a separate crate (#8181) # Description This breaks out the core_commands into a separate crate called nu_cmd_lang _(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.)_ # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-02-24 16:54:42 +01:00
"nu-engine",
"nu-parser",
"nu-protocol",
"nu-utils",
"shadow-rs",
]
allow flatshape (command line syntax) theming (#502) * allow flatshape (command line syntax) theming * renamed crate, organized
2021-12-16 13:17:29 +01:00
[[package]]
name = "nu-color-config"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
allow flatshape (command line syntax) theming (#502) * allow flatshape (command line syntax) theming * renamed crate, organized
2021-12-16 13:17:29 +01:00
dependencies = [
Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787) # Description Now use `nu-ansi-term` 0.49 Small adjustments to accommodate breaking changes. # User-Facing Changes None
2023-07-24 13:16:18 +02:00
"nu-ansi-term",
color_config now accepts closures as color values (#7141) # Description Closes #6909. You can now add closures to your `color_config` themes. Whenever a value would be printed with `table`, the closure is run with the value piped-in. The closure must return either a {fg,bg,attr} record or a color name (`'light_red'` etc.). This returned style is used to colour the value. This is entirely backwards-compatible with existing config.nu files. Example code excerpt: ``` let my_theme = { header: green_bold bool: { if $in { 'light_cyan' } else { 'light_red' } } int: purple_bold filesize: { |e| if $e == 0b { 'gray' } else if $e < 1mb { 'purple_bold' } else { 'cyan_bold' } } duration: purple_bold date: { (date now) - $in | if $in > 1wk { 'cyan_bold' } else if $in > 1day { 'green_bold' } else { 'yellow_bold' } } range: yellow_bold string: { if $in =~ '^#\w{6}$' { $in } else { 'white' } } nothing: white ``` Example output with this in effect: ![2022-11-16 12 47 23 AM - style_computer rs_-_nushell_-_VSCodium](https://user-images.githubusercontent.com/83939/201952558-482de05d-69c7-4bf2-91fc-d0964bf71264.png) ![2022-11-16 12 39 41 AM - style_computer rs_-_nushell_-_VSCodium](https://user-images.githubusercontent.com/83939/201952580-2384bb86-b680-40fe-8192-71bae396c738.png) ![2022-11-15 09 21 54 PM - run_external rs_-_nushell_-_VSCodium](https://user-images.githubusercontent.com/83939/201952601-343fc15d-e4a8-4a92-ad89-9a7d17d42748.png) Slightly important notes: * Some color_config names, namely "separator", "empty" and "hints", pipe in `null` instead of a value. * Currently, doing anything non-trivial inside a closure has an understandably big perf hit. I currently do not actually recommend something like `string: { if $in =~ '^#\w{6}$' { $in } else { 'white' } }` for serious work, mainly because of the abundance of string-type data in the world. Nevertheless, lesser-used types like "date" and "duration" work well with this. * I had to do some reorganisation in order to make it possible to call `eval_block()` that late in table rendering. I invented a new struct called "StyleComputer" which holds the engine_state and stack of the initial `table` command (implicit or explicit). * StyleComputer has a `compute()` method which takes a color_config name and a nu value, and always returns the correct Style, so you don't have to worry about A) the color_config value was set at all, B) whether it was set to a closure or not, or C) which default style to use in those cases. * Currently, errors encountered during execution of the closures are thrown in the garbage. Any other ideas are welcome. (Nonetheless, errors result in a huge perf hit when they are encountered. I think what should be done is to assume something terrible happened to the user's config and invalidate the StyleComputer for that `table` run, thus causing subsequent output to just be Style::default().) * More thorough tests are forthcoming - ran into some difficulty using `nu!` to take an alternative config, and for some reason `let-env config =` statements don't seem to work inside `nu!` pipelines(???) * The default config.nu has not been updated to make use of this yet. Do tell if you think I should incorporate that into this. # User-Facing Changes See above. # 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 --features=extra -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace --features=extra` to check that all tests pass # 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.
2022-12-17 14:07:56 +01:00
"nu-engine",
Patch explore 4 (#7517) ref #7339 - This PR updates explore to take some of the colors from nushell, namely the line colors and the ls_colors. note: Not sure why this regression appeared maybe it's a feature or it's no longer supposed to be supported? Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-12-18 15:43:15 +01:00
"nu-json",
allow flatshape (command line syntax) theming (#502) * allow flatshape (command line syntax) theming * renamed crate, organized
2021-12-16 13:17:29 +01:00
"nu-protocol",
color_config now accepts closures as color values (#7141) # Description Closes #6909. You can now add closures to your `color_config` themes. Whenever a value would be printed with `table`, the closure is run with the value piped-in. The closure must return either a {fg,bg,attr} record or a color name (`'light_red'` etc.). This returned style is used to colour the value. This is entirely backwards-compatible with existing config.nu files. Example code excerpt: ``` let my_theme = { header: green_bold bool: { if $in { 'light_cyan' } else { 'light_red' } } int: purple_bold filesize: { |e| if $e == 0b { 'gray' } else if $e < 1mb { 'purple_bold' } else { 'cyan_bold' } } duration: purple_bold date: { (date now) - $in | if $in > 1wk { 'cyan_bold' } else if $in > 1day { 'green_bold' } else { 'yellow_bold' } } range: yellow_bold string: { if $in =~ '^#\w{6}$' { $in } else { 'white' } } nothing: white ``` Example output with this in effect: ![2022-11-16 12 47 23 AM - style_computer rs_-_nushell_-_VSCodium](https://user-images.githubusercontent.com/83939/201952558-482de05d-69c7-4bf2-91fc-d0964bf71264.png) ![2022-11-16 12 39 41 AM - style_computer rs_-_nushell_-_VSCodium](https://user-images.githubusercontent.com/83939/201952580-2384bb86-b680-40fe-8192-71bae396c738.png) ![2022-11-15 09 21 54 PM - run_external rs_-_nushell_-_VSCodium](https://user-images.githubusercontent.com/83939/201952601-343fc15d-e4a8-4a92-ad89-9a7d17d42748.png) Slightly important notes: * Some color_config names, namely "separator", "empty" and "hints", pipe in `null` instead of a value. * Currently, doing anything non-trivial inside a closure has an understandably big perf hit. I currently do not actually recommend something like `string: { if $in =~ '^#\w{6}$' { $in } else { 'white' } }` for serious work, mainly because of the abundance of string-type data in the world. Nevertheless, lesser-used types like "date" and "duration" work well with this. * I had to do some reorganisation in order to make it possible to call `eval_block()` that late in table rendering. I invented a new struct called "StyleComputer" which holds the engine_state and stack of the initial `table` command (implicit or explicit). * StyleComputer has a `compute()` method which takes a color_config name and a nu value, and always returns the correct Style, so you don't have to worry about A) the color_config value was set at all, B) whether it was set to a closure or not, or C) which default style to use in those cases. * Currently, errors encountered during execution of the closures are thrown in the garbage. Any other ideas are welcome. (Nonetheless, errors result in a huge perf hit when they are encountered. I think what should be done is to assume something terrible happened to the user's config and invalidate the StyleComputer for that `table` run, thus causing subsequent output to just be Style::default().) * More thorough tests are forthcoming - ran into some difficulty using `nu!` to take an alternative config, and for some reason `let-env config =` statements don't seem to work inside `nu!` pipelines(???) * The default config.nu has not been updated to make use of this yet. Do tell if you think I should incorporate that into this. # User-Facing Changes See above. # 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 --features=extra -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace --features=extra` to check that all tests pass # 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.
2022-12-17 14:07:56 +01:00
"nu-test-support",
"nu-utils",
allow flatshape (command line syntax) theming (#502) * allow flatshape (command line syntax) theming * renamed crate, organized
2021-12-16 13:17:29 +01:00
"serde",
Extract nu_source into a crate This commit extracts Tag, Span, Text, as well as source-related debug facilities into a new crate called nu_source. This change is much bigger than one might have expected because the previous code relied heavily on implementing inherent methods on `Tagged<T>` and `Spanned<T>`, which is no longer possible. As a result, this change creates more concrete types instead of using `Tagged<T>`. One notable example: Tagged<Value> became Value, and Value became UntaggedValue. This change clarifies the intent of the code in many places, but it does make it a big change.
2019-11-21 15:33:14 +01:00
]
Split nu-cli into nu-cli/nu-engine (#2898) We split off the evaluation engine part of nu-cli into its own crate. This helps improve build times for nu-cli by 17% in my tests. It also helps us see a bit better what's the core engine portion vs the part specific to the interactive CLI piece. There's more than can be done here, but I think it's a good start in the right direction.
2021-01-10 03:50:49 +01:00
Bump to 0.25.2 (#2908)
2021-01-11 19:50:53 +01:00
[[package]]
nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
name = "nu-command"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Add commands
2021-09-03 00:58:15 +02:00
dependencies = [
enable cd to work with directory abbreviations (#5452) * enable cd to work with abbreviations * add abbreviation example * fix tests * make it configurable
2022-05-06 14:58:32 +02:00
"alphanumeric-sort",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"base64 0.21.5",
A new subcommand to str, str-expand. (#9290) # 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. --> Description can be found [here: https://github.com/nushell/nushell/discussions/9277#discussioncomment-5997793](https://github.com/nushell/nushell/discussions/9277#discussioncomment-5997793) # User-Facing Changes Again, examples can be found in the discussion #9277 <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting I've written tests that cover the changes I've made. <!-- 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-06-28 19:57:44 +02:00
"bracoxide",
Binary into int (#5941) * Add support for binary to into int * Add test
2022-07-03 20:31:50 +02:00
"byteorder",
add ability to parse strings like "100kib" and "100 kib"
2021-10-12 22:22:12 +02:00
"bytesize",
`from xlsx` `from ods` and `from toml` (#352) * MathEval Variance and Stddev * Fix tests and linting * Typo * Deal with streams when they are not tables * `from toml` command * From ods * From XLSX
2021-11-19 20:23:35 +01:00
"calamine",
Add encoding auto-detection for `decode` (#10030) # Description Allow `decode` command to guess the encoding of input if no encoding name is given. # User-Facing Changes * `decode` now has an optional parameter instead of required one. User can just run `decode` to let the command automatically detect encoding and convert it to utf-8. <img width="575" alt="Example" src="https://github.com/nushell/nushell/assets/1991933/03a0ba11-910e-4db9-89aa-79cfec06893f"> * Based on the detect result, user may have to give a encoding name <img width="572" alt="Error Sample1" src="https://github.com/nushell/nushell/assets/1991933/f21fda85-1f04-4cb3-9feb-cb9fb7dcee07"> or get informed that the input is not supported by `decode` <img width="568" alt="Error Sample2" src="https://github.com/nushell/nushell/assets/1991933/dd3cc4c0-f119-493e-8609-d07594fc055a"> # Tests + Formatting * `cargo fmt --all -- --check` : OK * `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect -A clippy::result_large_err`: OK * `cargo test --workspace` : OK * `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"`: OK # After Submitting [Command document](https://www.nushell.sh/commands/docs/decode.html) is auto-generated and requires no action. --------- Co-authored-by: Horasal <horsal@horsal.dev>
2023-08-25 02:21:17 +02:00
"chardetng",
Add unit parsing and eval support
2021-10-05 04:27:39 +02:00
"chrono",
Add a simple scope variable
2021-11-02 04:08:05 +01:00
"chrono-humanize",
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
"chrono-tz",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"crossterm",
Add from csv and from tsv (#320)
2021-11-09 21:17:37 +01:00
"csv",
little cleanup
2021-10-15 20:51:25 +02:00
"dialoguer",
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
"digest",
imp: bump rustyline to 8.0.0 (#3167) * imp: bump rustyline to 8.0.0 * fix: rustyline 8 keybindings * fix: commands count/length test Co-authored-by: alexhk <alexhk@protonmail.com>
2021-03-14 03:13:31 +01:00
"dirs-next",
nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
"dtparse",
"encoding_rs",
Bump `fancy-regex` to single `0.12.0` version (#11389) Supersedes #11039 that was broken due to dependabot not correctly taking the workspace into account (this bug has been worked around in #11387)
2023-12-21 17:10:33 +01:00
"fancy-regex",
nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
"filesize",
Implement rest of `touch` flags (#5119) * Add timestamp flag to `touch` command * Add modify flag to `touch` command * Add date flag to `touch` command * Remove unnecessary `touch` test and fix tests setups * Change `touch` flags descriptions * Update `touch` example * Add reference flag to `touch` command * Add access flag to `touch` command * Add no-create flag to `touch` command * Replace `unwrap` with `expect`
2022-04-07 13:44:05 +02:00
"filetime",
Re-port filesystem commands (#4387) * Re-port the filesystem commands * Remove commented out section
2022-02-09 15:56:27 +01:00
"fs_extra",
nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
"htmlescape",
allow parsing of human readable datetimes (#11051) # Description This PR adds the ability to parse human readable datetime strings as part of the `into datetime` command. I added a new `-n`/`--list-human` parameter that produces this list to give the user an idea of what is supported. ```nushell ❯ into datetime --list-human ╭#─┬parseable human datetime examples┬───result───╮ │0 │Today 18:30 │in 8 hours │ │1 │2022-11-07 13:25:30 │a year ago │ │2 │15:20 Friday │in 3 days │ │3 │This Friday 17:00 │in 3 days │ │4 │13:25, Next Tuesday │in a week │ │5 │Last Friday at 19:45 │3 days ago │ │6 │In 3 days │in 2 days │ │7 │In 2 hours │in 2 hours │ │8 │10 hours and 5 minutes ago │10 hours ago│ │9 │1 years ago │a year ago │ │10│A year ago │a year ago │ │11│A month ago │a month ago │ │12│A week ago │a week ago │ │13│A day ago │a day ago │ │14│An hour ago │an hour ago │ │15│A minute ago │a minute ago│ │16│A second ago │now │ │17│Now │now │ ╰#─┴parseable human datetime examples┴───result───╯ ``` Or with `$env.config.datetime_format.table` set. ```nushell ❯ into datetime --list-human ╭#─┬parseable human datetime examples┬──────result───────╮ │0 │Today 18:30 │11/14/23 06:30:00PM│ │1 │2022-11-07 13:25:30 │11/07/22 01:25:30PM│ │2 │15:20 Friday │11/17/23 03:20:00PM│ │3 │This Friday 17:00 │11/17/23 05:00:00PM│ │4 │13:25, Next Tuesday │11/21/23 01:25:00PM│ │5 │Last Friday at 19:45 │11/10/23 07:45:00PM│ │6 │In 3 days │11/17/23 10:12:54AM│ │7 │In 2 hours │11/14/23 12:12:54PM│ │8 │10 hours and 5 minutes ago │11/14/23 12:07:54AM│ │9 │1 years ago │11/13/22 10:12:54AM│ │10│A year ago │11/13/22 10:12:54AM│ │11│A month ago │10/15/23 11:12:54AM│ │12│A week ago │11/07/23 10:12:54AM│ │13│A day ago │11/13/23 10:12:54AM│ │14│An hour ago │11/14/23 09:12:54AM│ │15│A minute ago │11/14/23 10:11:54AM│ │16│A second ago │11/14/23 10:12:53AM│ │17│Now │11/14/23 10:12:54AM│ ╰#─┴parseable human datetime examples┴──────result───────╯ ``` # 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-11-16 00:43:37 +01:00
"human-date-parser",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"indexmap",
Progress bar Implementation (#7661) # Description _(Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience.)_ I implemented the status bar we talk about yesterday. The idea was inspired by the progress bar of `wget`. I decided to go for the second suggestion by `@Reilly` > 2. add an Option<usize> or whatever to RawStream (and ListStream?) for situations where you do know the length ahead of time For now only works with the command `save` but after the approve of this PR we can see how we can implement it on commands like `cp` and `mv` When using `fetch` nushell will check if there is any `content-length` attribute in the request header. If so, then `fetch` will send it through the new `Option` variable in the `RawStream` to the `save`. If we know the total size we show the progress bar ![nu_pb01](https://user-images.githubusercontent.com/38369407/210298647-07ee55ea-e751-41b1-a84d-f72ec1f6e9e5.jpg) but if we don't then we just show the stats like: data already saved, bytes per second, and time lapse. ![nu_pb02](https://user-images.githubusercontent.com/38369407/210298698-1ef65f51-40cc-4481-83de-309cbd1049cb.jpg) ![nu_pb03](https://user-images.githubusercontent.com/38369407/210298701-eef2ef13-9206-4a98-8202-e4fe5531d79d.jpg) Please let me know If I need to make any changes and I will be happy to do it. # User-Facing Changes A new flag (`--progress` `-p`) was added to the `save` command Examples: ```nu fetch https://github.com/torvalds/linux/archive/refs/heads/master.zip | save --progress -f main.zip fetch https://releases.ubuntu.com/22.04.1/ubuntu-22.04.1-desktop-amd64.iso | save --progress -f main.zip open main.zip --raw | save --progress main.copy ``` # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - I am getting some errors and its weird because the errors are showing up in files i haven't touch. Is this normal? # 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. Co-authored-by: Reilly Wood <reilly.wood@icloud.com>
2023-01-11 02:57:48 +01:00
"indicatif",
Bump itertools from 0.11.0 to 0.12.0 (#11360) Bumps [itertools](https://github.com/rust-itertools/itertools) from 0.11.0 to 0.12.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rust-itertools/itertools/blob/master/CHANGELOG.md">itertools's changelog</a>.</em></p> <blockquote> <h2>0.12.0</h2> <h3>Breaking</h3> <ul> <li>Made <code>take_while_inclusive</code> consume iterator by value (<a href="https://redirect.github.com/rust-itertools/itertools/issues/709">#709</a>)</li> <li>Added <code>Clone</code> bound to <code>Unique</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/777">#777</a>)</li> </ul> <h3>Added</h3> <ul> <li>Added <code>Itertools::try_len</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/723">#723</a>)</li> <li>Added free function <code>sort_unstable</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/796">#796</a>)</li> <li>Added <code>GroupMap::fold_with</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/778">#778</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/785">#785</a>)</li> <li>Added <code>PeekNth::{peek_mut, peek_nth_mut}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/716">#716</a>)</li> <li>Added <code>PeekNth::{next_if, next_if_eq}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/734">#734</a>)</li> <li>Added conversion into <code>(Option&lt;A&gt;,Option&lt;B&gt;)</code> to <code>EitherOrBoth</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/713">#713</a>)</li> <li>Added conversion from <code>Either&lt;A, B&gt;</code> to <code>EitherOrBoth&lt;A, B&gt;</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/715">#715</a>)</li> <li>Implemented <code>ExactSizeIterator</code> for <code>Tuples</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/761">#761</a>)</li> <li>Implemented <code>ExactSizeIterator</code> for <code>(Circular)TupleWindows</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/752">#752</a>)</li> <li>Made <code>EitherOrBoth&lt;T&gt;</code> a shorthand for <code>EitherOrBoth&lt;T, T&gt;</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/719">#719</a>)</li> </ul> <h3>Changed</h3> <ul> <li>Added missing <code>#[must_use]</code> annotations on iterator adaptors (<a href="https://redirect.github.com/rust-itertools/itertools/issues/794">#794</a>)</li> <li>Made <code>Combinations</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/795">#795</a>)</li> <li>Made <code>Intersperse(With)</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/797">#797</a>)</li> <li>Made <code>Permutations</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/793">#793</a>)</li> <li>Made <code>Product</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/800">#800</a>)</li> <li>Made <code>TupleWindows</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/602">#602</a>)</li> <li>Specialized <code>Combinations::{count, size_hint}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/729">#729</a>)</li> <li>Specialized <code>CombinationsWithReplacement::{count, size_hint}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/737">#737</a>)</li> <li>Specialized <code>Powerset::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/765">#765</a>)</li> <li>Specialized <code>Powerset::count</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/735">#735</a>)</li> <li>Specialized <code>TupleCombinations::{count, size_hint}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/763">#763</a>)</li> <li>Specialized <code>TupleCombinations::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/775">#775</a>)</li> <li>Specialized <code>WhileSome::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/780">#780</a>)</li> <li>Specialized <code>WithPosition::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/772">#772</a>)</li> <li>Specialized <code>ZipLongest::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/774">#774</a>)</li> <li>Changed <code>{min, max}_set*</code> operations require <code>alloc</code> feature, instead of <code>std</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/760">#760</a>)</li> <li>Improved documentation of <code>tree_fold1</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/787">#787</a>)</li> <li>Improved documentation of <code>permutations</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/724">#724</a>)</li> <li>Fixed typo in documentation of <code>multiunzip</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/770">#770</a>)</li> </ul> <h3>Notable Internal Changes</h3> <ul> <li>Improved specialization tests (<a href="https://redirect.github.com/rust-itertools/itertools/issues/799">#799</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/786">#786</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/782">#782</a>)</li> <li>Simplified implementation of <code>Permutations</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/739">#739</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/748">#748</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/790">#790</a>)</li> <li>Combined <code>Merge</code>/<code>MergeBy</code>/<code>MergeJoinBy</code> implementations (<a href="https://redirect.github.com/rust-itertools/itertools/issues/736">#736</a>)</li> <li>Simplified <code>Permutations::size_hint</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/739">#739</a>)</li> <li>Fix wrapping arithmetic in benchmarks (<a href="https://redirect.github.com/rust-itertools/itertools/issues/770">#770</a>)</li> <li>Enforced <code>rustfmt</code> in CI (<a href="https://redirect.github.com/rust-itertools/itertools/issues/751">#751</a>)</li> <li>Disallowed compile warnings in CI (<a href="https://redirect.github.com/rust-itertools/itertools/issues/720">#720</a>)</li> <li>Used <code>cargo hack</code> to check MSRV (<a href="https://redirect.github.com/rust-itertools/itertools/issues/754">#754</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rust-itertools/itertools/commit/98ecabb47d7147dae06fc3fa400ec758947194f3"><code>98ecabb</code></a> chore: Release itertools version 0.12.0</li> <li><a href="https://github.com/rust-itertools/itertools/commit/22fc427ac5282cbdafccfe38a686ec1d3b720120"><code>22fc427</code></a> prepare v0.12.0 release</li> <li><a href="https://github.com/rust-itertools/itertools/commit/6d291786a9c9686a3997d93c513bd18326611fe5"><code>6d29178</code></a> Document the field <code>a_cur</code> of <code>Product</code></li> <li><a href="https://github.com/rust-itertools/itertools/commit/bf2b0129d1d3cc1ffa733059f3088adb6d745fe6"><code>bf2b012</code></a> Better <code>Product::size_hint</code></li> <li><a href="https://github.com/rust-itertools/itertools/commit/8d07f6b8566a515118ca8b119f358b73d483152b"><code>8d07f6b</code></a> Make <code>Product</code> lazy</li> <li><a href="https://github.com/rust-itertools/itertools/commit/d7e6bab9fd0ad79130692f8e48e21375362a7614"><code>d7e6bab</code></a> Document the field <code>peek</code> of <code>IntersperseWith</code></li> <li><a href="https://github.com/rust-itertools/itertools/commit/9b01a118919f0d1f7c3327d1a15a5eb660f3912e"><code>9b01a11</code></a> Make <code>IntersperseWith</code> lazy</li> <li><a href="https://github.com/rust-itertools/itertools/commit/4f22173b93a2eb58da16b7da6d08e6c3f1c56544"><code>4f22173</code></a> Refactor <code>IntersperseWith::next</code></li> <li><a href="https://github.com/rust-itertools/itertools/commit/b76172b412116356ebef05b884a6e4def63a4d17"><code>b76172b</code></a> chore: adjust docs to reflect discussion in the PR</li> <li><a href="https://github.com/rust-itertools/itertools/commit/955927f6c424f895ad7519d413bc5718e6ad26bf"><code>955927f</code></a> chore: fixup docs of tree_fold1</li> <li>Additional commits viewable in <a href="https://github.com/rust-itertools/itertools/compare/v0.11.0...v0.12.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=itertools&package-manager=cargo&previous-version=0.11.0&new-version=0.12.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-12-20 15:58:07 +01:00
"itertools 0.12.0",
fix: fixcd (#6799) * fix: fixcd try to fix Log: try to fix the bug with can enter a permisson error fold * change wording * fat * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-11-04 19:38:39 +01:00
"libc",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"log",
respect lscolors env var; measure width minus ansi
2021-10-08 16:40:20 +02:00
"lscolors",
Add sha256 to the hash command (#3836) Hashers now uses on Rust Crypto Digest trait which makes it trivial to implement additional hash functions. The original `md5` crate does not implement the Digest trait and was replaced by `md-5` crate which does. Sha256 uses already included `sha2` crate.
2021-07-25 21:08:08 +02:00
"md-5",
feat: add a `command_not_found` hook (#8314) # Description Add a `command_not_found` function to `$env.config.hooks`. If this function outputs a string, then it's included in the `help`. An example hook on *Arch Linux*, to find packages that contain the binary, looks like: ```nushell let-env config = { # ... hooks: { command_not_found: { |cmd_name| ( try { let pkgs = (pkgfile --binaries --verbose $cmd_name) ( $"(ansi $env.config.color_config.shape_external)($cmd_name)(ansi reset) " + $"may be found in the following packages:\n($pkgs)" ) } catch { null } ) } # ... ``` # User-Facing Changes - Add a `command_not_found` function to `$env.config.hooks`. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-20 05:05:22 +01:00
"miette",
Move sys, ps, fetch, post to internal commands (#3983) * Move sys, ps, fetch, post to internal commands * Remove old plugins * clippy Co-authored-by: JT <jonatha.d.turner@gmail.com>
2021-09-01 04:29:09 +02:00
"mime",
add `--mime-type(-m)` to `ls` in the `type` column (#7616) # Description This PR adds the `mime-type` to the `type` column if you add the `--mime-type(-m)` flag to `ls`. <img width="853" alt="Screenshot 2022-12-27 at 11 43 20 AM" src="https://user-images.githubusercontent.com/343840/209705499-27fe40fe-0356-4d9d-97f2-4b2dc52e0963.png"> <img width="781" alt="Screenshot 2022-12-27 at 11 45 53 AM" src="https://user-images.githubusercontent.com/343840/209705509-4d677389-fd68-401e-a7af-3fc6052743b6.png"> # User-Facing Changes If you specify the `-m` flag, you get the "guessed at" mime type. The guess is based on the file name and uses this crate https://docs.rs/mime_guess/latest/mime_guess/ for the guessing. Part of issue #7612 and and #7524 There's some debate on if the `mime-type` should be added to the `type` column or if there should be a separate `mime` column. I tend to lean on the side of `type` since it's technically a type and it's only in that column if you ask it to be there. Also, I'd prefer to reuse a column rather than having a list of sprawling columns. Also, as @KodiCraft suggested, there is precedence as with `ls -d` where the summed size is in the size column. I could go either way and if someone wants to create a `mime` column, we'd probably accept it. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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.
2022-12-27 19:46:23 +01:00
"mime_guess",
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
"mockito",
changes Reqwest to Ureq. (#8320) # Description _(Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes.)_ This pull request removes `Reqwest` and replaces it with `Ureq` to remove some of our dependencies, giving us faster compile times as well as smaller binaries. `Ureq` does not have an async runtime included so we do not need build heavy dependencies such as `Tokio`. From older tests I had the number of build units be reduced from `430 -> 392`. The default of `Ureq` uses `Rustls` but it has been configured to instead use `native_tls` which should work exactly the same as the `tls` works now. I removed `content-length` from the http commands as after refactoring i did not see a reason to have it available, correct me if this is something we should preserve. In the medium, to long term, we should maybe consider changing to `rustls` to have the same `tls` on all platforms. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-05 23:48:13 +01:00
"native-tls",
rename nushell's cp command to cp-old making coreutils the default cp (#10678) # Description This PR renames nushell's `cp` command to `cp-old` to make room for `ucp` to be renamed to `cp`, making the coreutils version of `cp` the default for nushell. After some period of time, we should remove `cp-old` entirely. # 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-10-11 01:13:28 +02:00
"nix",
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"notify-debouncer-full",
Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787) # Description Now use `nu-ansi-term` 0.49 Small adjustments to accommodate breaking changes. # User-Facing Changes None
2023-07-24 13:16:18 +02:00
"nu-ansi-term",
move common tools from `nu-command` to `nu-cmd-base` (#9455) related to - https://github.com/nushell/nushell/pull/9404 # Description to support our cratification effort and moving non-1.0 commands outside of the main focus, this PR - creates a new `nu-cmd-base` crate to hold the common structs, traits and functions used by all command-related crates - to start the transition, moves the `input_handler` module from `nu-command` to `nu-cmd-base` # User-Facing Changes ``` $nothing ``` # Tests + Formatting - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # After Submitting ``` $nothing ```
2023-06-22 23:45:54 +02:00
"nu-cmd-base",
Cratification: Break out nu_cmd_lang into a separate crate (#8181) # Description This breaks out the core_commands into a separate crate called nu_cmd_lang _(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.)_ # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-02-24 16:54:42 +01:00
"nu-cmd-lang",
allow flatshape (command line syntax) theming (#502) * allow flatshape (command line syntax) theming * renamed crate, organized
2021-12-16 13:17:29 +01:00
"nu-color-config",
Add commands
2021-09-03 00:58:15 +02:00
"nu-engine",
Nu glob (#4818) * Fork glob. Normalise license holder * Fix more licenses * unwraps * bad doc test
2022-03-13 19:30:27 +01:00
"nu-glob",
Add 'from json'
2021-10-01 07:11:49 +02:00
"nu-json",
example unit test
2021-10-09 15:10:10 +02:00
"nu-parser",
Add simple cd
2021-10-02 22:16:37 +02:00
"nu-path",
Add string stream and binary stream, add text decoding (#570) * WIP * Add binary/string streams and text decoding * Make string collection fallible * Oops, forgot pretty hex * Oops, forgot pretty hex * clippy
2021-12-24 08:22:11 +01:00
"nu-pretty-hex",
Add commands
2021-09-03 00:58:15 +02:00
"nu-protocol",
Add nu-system and rewrite ps command (#734) * Add nu-system and rewrite ps command * Add more deps * Add more deps * clippy * clippy * clippy * clippy * clippy * clippy
2022-01-14 07:20:53 +01:00
"nu-system",
Add a very silly table
2021-09-10 04:27:12 +02:00
"nu-table",
moved `grid` to it's own crate named `nu-term-grid`
2021-10-07 17:32:39 +02:00
"nu-term-grid",
Add initial nu-test-support port (#913) * Add initial nu-test-support port * finish changing binary name * Oops, these aren't Windows-safe tests
2022-02-02 21:59:01 +01:00
"nu-test-support",
added `nu-utils` crate, fixed issue where externals turn off vt processing (#4857) * added `nu-utils` crate, fixed issue where externals turn off vt processing * hopefully make work in non-windows environments * clippy
2022-03-16 23:21:06 +01:00
"nu-utils",
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
"num 0.4.1",
Add decimals to int when using `into string --decimals` (#6085) * Add decimals to int when using `into string --decimals` * Add tests for `into string` when converting int with `--decimals` * Apply formatting * Merge `into_str` test files * Comment out unused code and add TODOs * Use decimal separator depending on system locale * Add test helper to run closure in different locale * Add tests for int-to-string conversion using different locales * Add utils function to get system locale * Add panic message when locking mutex fails * Catch and resume panic later to prevent Mutex poisoning when test fails * Move test to `nu-test-support` to keep `nu-utils` free of `nu-*` dependencies See https://github.com/nushell/nushell/pull/6085#issuecomment-1193131694 * Rename test support fn `with_fake_locale` to `with_locale_override` * Move `get_system_locale()` to `locale` module * Allow overriding locale with special env variable (when not in release) * Use special env var to override locale during testing * Allow callback to return a value in `with_locale_override()` * Allow multiple options in `nu!` macro * Allow to set locale as `nu!` macro option * Use new `locale` option of `nu!` macro instead of `with_locale_override` Using the `locale` options does not lock the `LOCALE_OVERRIDE_MUTEX` mutex in `nu-test-support::locale_override` but instead calls the `nu` command directly with the `NU_LOCALE_OVERRIDE` environment variable. This allows for parallel test excecution. * Fix: Add option identifier for `cwd` in usage of `nu!` macro * Rely on `Display` trait for formatting `nu!` macro command - Removed the `DisplayPath` trait - Implement `Display` for `AbsolutePath`, `RelativePath` and `AbsoluteFile` * Default to locale `en_US.UTF-8` for tests when using `nu!` macro * Add doc comment to `nu!` macro * Format code using `cargo fmt --all` * Pass function directly instead of wrapping the call in a closure https://rust-lang.github.io/rust-clippy/master/index.html#redundant_closure * Pass function to `or_else()` instead of calling it inside `or()` https://rust-lang.github.io/rust-clippy/master/index.html#or_fun_call * Fix: Add option identifier for `cwd` in usage of `nu!` macro
2022-08-13 04:13:50 +02:00
"num-format",
Add `bits shl` and `bits shr` command (#6202) * Add `bits shift-left` and `bits shift-right` command * update bits shift error tips * some code refactor * update shift right * some code refactor for bits shift commands * rename bits shift commands align with bits operators * update search term * Update crates/nu-command/src/bits/not.rs Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com> * Update crates/nu-command/src/bits/shift_left.rs Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com> * Update crates/nu-command/src/bits/shift_right.rs Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com> * ci skip * change default number-bytes for bits shift * fix bits not tests * fix bits tests Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com>
2022-08-02 22:52:04 +02:00
"num-traits",
Fix needs_quotes() in `to nuon` (closes #6989) (#7056) * to nuon: fix needs_quotes() Also, null now serialises as null instead of $nothing. * Clippy * Add missing quote * Remove two unnecessary characters * Add short datetime tests * Make regex simplificatified * Alphabetise 'use' statements * Improve perf by putting case-insensitive cases in regex * Fix 1 test
2022-11-19 12:09:39 +01:00
"once_cell",
let `start` open anything and everything (#7580) # Description Fixes #7546 's request. I'm unsure, so hopefully someone in charge of design can chip in. # User-Facing Changes `open` now opens directories in the default file manager. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-03 19:47:37 +01:00
"open",
Add --redirect-combine option to run-external (#8918) # Description Add option that combines both output streams to the `run-external` command. This allows you to do something like this: ```nushell let res = do -i { run-external --redirect-combine <command that prints to stdout and stderr> } | complete if $res.exit_code != 0 { # Only print output when command has failed. print "The command has failed, these are the logs:" print $res.stdout } ``` # User-Facing Changes No breaking changes, just an extra option. # Tests + Formatting Added a test that checks the new option # 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. --> Co-authored-by: Jelle Besseling <jelle@bigbridge.nl>
2023-04-28 14:55:48 +02:00
"os_pipe",
Fix ls relative path & command argument path expansion (#757) * Switch to short-names when the path is a relative_path (a dir) and exit with an error if the path does not exist * Remove debugging print line * Show relative filenames... It does not work yet for ls ../ * Try something else to fix relative paths... it works, but the ../ code part is not very pretty * Add canonicalize check and remove code clones * Fix the canonicalize_with issue pointed out by kubouch. Not sure the prefix_str is what kubouch suggested * Fix the canonicalize_with issue pointed out by kubouch. Not sure the prefix_str is what kubouch suggested * Add single-dot expansion to nu-path * Move value path expansion from parser to eval Fixes #745 * Remove single dot expansion from parser It is not necessary since it will get expanded anyway in the eval. * Fix ls to display globs with relative paths * Use pathdiff crate to get relative paths for ls Co-authored-by: Stefan Stanciulescu <contact@stefanstanciulescu.com>
2022-01-16 14:55:56 +01:00
"pathdiff",
Url encode to escape special characters (#7664) Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com>
2023-01-05 19:24:38 +01:00
"percent-encoding",
`string | fill` counts clusters, not graphemes; and doesn't count ANSI escape codes (#8134) Enhancement of new `fill` command (#7846) to handle content including ANSI escape codes for formatting or multi-code-point Unicode grapheme clusters. In both of these cases, the content is (many) bytes longer than its visible length, and `fill` was counting the extra bytes so not adding enough fill characters. # Description This script: ```rust # the teacher emoji `\u{1F9D1}\u{200D}\u{1F3EB}` is 3 code points, but only 1 print position wide. echo "This output should be 3 print positions wide, with leading and trailing `+`" $"\u{1F9D1}\u{200D}\u{1F3EB}" | fill -c "+" -w 3 -a "c" echo "This output should be 3 print positions wide, with leading and trailing `+`" $"(ansi green)a(ansi reset)" | fill -c "+" -w 3 -a c echo "" ``` Was producing this output: ```rust This output should be 3 print positions wide, with leading and trailing `+` 🧑‍🏫 This output should be 3 print positions wide, with leading and trailing `+` a ``` After this PR, it produces this output: ```rust This output should be 3 print positions wide, with leading and trailing `+` +🧑‍🏫+ This output should be 3 print positions wide, with leading and trailing `+` +a+ ``` # User-Facing Changes Users may have to undo fixes they may have introduced to work around the former behavior. I have one such in my prompt string that I can now revert. # Tests + Formatting Don't forget to add tests that cover your changes. -- Done Make sure you've run and fixed any issues with these commands: - [x] `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [x] `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - [x] `cargo test --workspace` to check that all tests pass # After Submitting `fill` command not documented in the book, and it still talks about `str lpad/rpad`. I'll fix. Note added dependency on a new library `print-positions`, which is an iterator that yields a complete print position (cluster + Ansi sequence) per call. Should this be vendored?
2023-02-20 13:32:20 +01:00
"print-positions",
Bump `procfs` to 0.16.0 (#11115) Fix the breaking changes. Get's rid of some outdated transitive dependencies. Sadly we need to expose more of `procfs` to `nu-command` based on how the features of `nu-system` are exposed right now. Conditional compilation/dependencies from hell included Supersedes #11101
2023-11-20 21:22:35 +01:00
"procfs",
Bump `calamine` and fix clippy (#10314) Upgrade calamine to 0.22 Reduces one potential dependency duplication Supersedes #10305 Includes fixes for clippy lints as API changed to return owned data.
2023-09-11 12:39:52 +02:00
"quick-xml",
nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
"quickcheck",
"quickcheck_macros",
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"rand",
Add a simple parallel each
2021-10-26 03:30:53 +02:00
"rayon",
Handle mixed LF+CRLF in `lines` (#7316) This closes #4989. Previously `lines` was unable to handle text input with CRLF line breaks _and_ LF line breaks. ### Before: ![image](https://user-images.githubusercontent.com/26268125/205207685-b25da9e1-19fa-4abb-8ab2-0dd216c63fc0.png) ### After: ![image](https://user-images.githubusercontent.com/26268125/205207808-9f687242-a8c2-4b79-a12c-38b0583d8d52.png)
2022-12-02 17:30:26 +01:00
"regex",
nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
"roxmltree",
Bump rstest from 0.17.0 to 0.18.1 (#9782)
2023-08-08 19:11:05 +02:00
"rstest",
Initial SQLite functionality (#5182) * Add SQLite functionality to open * Add in-memory SQLite tests * clippy fixes * Fix up old SQLite-related tests
2022-04-14 05:15:02 +02:00
"rusqlite",
Fix mv data loss when changing folder case (step 1) (#6599) * Fix mv data loss when changing folder case (step 1) * Use same-file to detect when changing case on Windows
2022-09-23 20:09:31 +02:00
"same-file",
`from yaml` and `from yml` (#322) * MathEval Variance and Stddev * Fix tests and linting * Typo * Deal with streams when they are not tables * `from yaml` and `from yml` `from yaml` and `from yml` from yaml and from yml * Fix collect_string * Fix tests and linting
2021-11-10 02:02:33 +01:00
"serde",
update `ast` to support output to json (#8962) # Description This PR changes the `ast` command to be able to output `--json` as well as `nuon` (default) with "pretty" and "minified" output. I'm hoping this functionality will be usable in the vscode extension for semantic tokenization and highlighting. # User-Facing Changes There's a new `--json`/`-j` option. Prior version output of nuon is maintained as default. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-04-26 15:15:42 +02:00
"serde_json",
`from url` and `from eml` (#324) * MathEval Variance and Stddev * Fix tests and linting * Typo * Deal with streams when they are not tables * FromEml and FromUrl Added tests for from eml
2021-11-12 21:46:39 +01:00
"serde_urlencoded",
`from yaml` and `from yml` (#322) * MathEval Variance and Stddev * Fix tests and linting * Typo * Deal with streams when they are not tables * `from yaml` and `from yml` `from yaml` and `from yml` from yaml and from yml * Fix collect_string * Fix tests and linting
2021-11-10 02:02:33 +01:00
"serde_yaml",
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
"sha2",
update dfr to polars 0.30.0 (#9424) # Description Update the polars dependency for dataframes to stay on-version. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 19:05:45 +02:00
"sysinfo",
Revert "Add an option to move header on borders" (#9908) Reverts nushell/nushell#9796 This is just draft since we're seeing some issues with the latest fixes to table drawing that just landed with #9796. We're hoping to get these fixed, but if we're not able to fix them before the next release, we'll need to revert (hence this PR, just in case we need it).
2023-08-03 21:52:12 +02:00
"tabled",
Bump terminal_size from 0.2.6 to 0.3.0 (#10409) Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.6 to 0.3.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/eminence/terminal-size/releases">terminal_size's releases</a>.</em></p> <blockquote> <h2>v0.3.0</h2> <h2>What's Changed</h2> <ul> <li>Check all streams (out/err/in) to find one that has a tty and size by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://redirect.github.com/eminence/terminal-size/pull/58">eminence/terminal-size#58</a> <ul> <li>Note that this is a subtle change in behavior, since the <code>terminal_size()</code> function will now return success in cases more cases than before</li> </ul> </li> <li>Update to rustix 0.38 by <a href="https://github.com/chenx97"><code>@​chenx97</code></a> in <a href="https://redirect.github.com/eminence/terminal-size/pull/57">eminence/terminal-size#57</a> <ul> <li>This change bumps the MSRV from 1.48.0 to 1.63.0</li> </ul> </li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/eminence/terminal-size/compare/v0.2.6...v0.3.0">https://github.com/eminence/terminal-size/compare/v0.2.6...v0.3.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/eminence/terminal-size/commit/2983b7bf18531bbd2face938d2889f4590f9cb56"><code>2983b7b</code></a> Release v0.3.0</li> <li><a href="https://github.com/eminence/terminal-size/commit/27a4459b22594e804a608d0d29d194d2c6e454e3"><code>27a4459</code></a> Merge pull request <a href="https://redirect.github.com/eminence/terminal-size/issues/57">#57</a> from chenx97/rustix-0.38</li> <li><a href="https://github.com/eminence/terminal-size/commit/c24c1c34e51408c70136c9e6cff79d6d60f8aeed"><code>c24c1c3</code></a> Bump MSRV to 1.63.0</li> <li><a href="https://github.com/eminence/terminal-size/commit/78e13c77d7de86cf6d95dfaaf3ff71fec95d0cb4"><code>78e13c7</code></a> Update to rustix 0.38</li> <li><a href="https://github.com/eminence/terminal-size/commit/18c58b1ed5e4306826226d95e835ffd32f8c5926"><code>18c58b1</code></a> Merge pull request <a href="https://redirect.github.com/eminence/terminal-size/issues/58">#58</a> from eminence/check_all_streams</li> <li><a href="https://github.com/eminence/terminal-size/commit/08f0e73926c11adc3105dbf4eb84dd8c9e6c873a"><code>08f0e73</code></a> Check all streams (out/err/in) to find one that has a tty and size</li> <li>See full diff in <a href="https://github.com/eminence/terminal-size/compare/v0.2.6...v0.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=terminal_size&package-manager=cargo&previous-version=0.2.6&new-version=0.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-09-18 07:50:17 +02:00
"terminal_size 0.3.0",
Add a simple scope variable
2021-11-02 04:08:05 +01:00
"titlecase",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"toml 0.8.8",
nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
"trash",
"umask",
"unicode-segmentation",
changes Reqwest to Ureq. (#8320) # Description _(Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes.)_ This pull request removes `Reqwest` and replaces it with `Ureq` to remove some of our dependencies, giving us faster compile times as well as smaller binaries. `Ureq` does not have an async runtime included so we do not need build heavy dependencies such as `Tokio`. From older tests I had the number of build units be reduced from `430 -> 392`. The default of `Ureq` uses `Rustls` but it has been configured to instead use `native_tls` which should work exactly the same as the `tls` works now. I removed `content-length` from the http commands as after refactoring i did not see a reason to have it available, correct me if this is something we should preserve. In the medium, to long term, we should maybe consider changing to `rustls` to have the same `tls` on all platforms. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-05 23:48:13 +01:00
"ureq",
nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
"url",
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
"uu_cp",
Add `umkdir` command (#10785) A `mkdir` command, which uses `uu_mkdir` as backend. close #10515.
2023-10-30 13:59:48 +01:00
"uu_mkdir",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"uu_mktemp",
implement whoami using uutils (#10488) <!-- 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. --> Implements `whoami` using the `whoami` command from uutils as backend. This is a draft because it depends on https://github.com/uutils/coreutils/pull/5310 and a new release of uutils needs to be made (and the paths in `Cargo.toml` should be updated). At this point, this is more of a proof of concept 😄 Additionally, this implements a (simple and naive) conversion from the uutils `UResult` to the nushell `ShellError`, which should help with the integration of other utils, too. I can split that off into a separate PR if desired. I put this command in the "platform" category. If it should go somewhere else, let me know! The tests will currently fail, because I've used a local path to uutils. Once the PR on the uutils side is merged, I'll update it to a git path so that it can be tested and runs on more machines than just mine. # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> New `whoami` command. This might break some users who expect the system `whoami` command. However, the result of this new command should be very close, just with a nicer help message, at least for Linux users. The default `whoami` on Windows is quite different from this implementation: https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/whoami # 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-10-25 16:53:52 +02:00
"uu_whoami",
nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
"uuid",
new `glob` command (#5087)
2022-04-04 22:45:01 +02:00
"wax",
Bump which from 4.4.2 to 5.0.0 (#10811)
2023-10-23 08:14:28 +02:00
"which 5.0.0",
Bump windows from 0.48.0 to 0.52.0 (#11325) # Description Bump `windows` to 0.52.0 and fix `is_admin` https://github.com/microsoft/windows-rs/pull/2476 # User-Facing Changes N/A --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-12-21 18:49:15 +01:00
"windows 0.52.0",
changes Reqwest to Ureq. (#8320) # Description _(Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes.)_ This pull request removes `Reqwest` and replaces it with `Ureq` to remove some of our dependencies, giving us faster compile times as well as smaller binaries. `Ureq` does not have an async runtime included so we do not need build heavy dependencies such as `Tokio`. From older tests I had the number of build units be reduced from `430 -> 392`. The default of `Ureq` uses `Rustls` but it has been configured to instead use `native_tls` which should work exactly the same as the `tls` works now. I removed `content-length` from the http commands as after refactoring i did not see a reason to have it available, correct me if this is something we should preserve. In the medium, to long term, we should maybe consider changing to `rustls` to have the same `tls` on all platforms. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-05 23:48:13 +01:00
"winreg",
Bump to 0.25.2 (#2908)
2021-01-11 19:50:53 +01:00
]
Split nu-cli into nu-cli/nu-engine (#2898) We split off the evaluation engine part of nu-cli into its own crate. This helps improve build times for nu-cli by 17% in my tests. It also helps us see a bit better what's the core engine portion vs the part specific to the interactive CLI piece. There's more than can be done here, but I think it's a good start in the right direction.
2021-01-10 03:50:49 +01:00
[[package]]
name = "nu-engine"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Split nu-cli into nu-cli/nu-engine (#2898) We split off the evaluation engine part of nu-cli into its own crate. This helps improve build times for nu-cli by 17% in my tests. It also helps us see a bit better what's the core engine portion vs the part specific to the interactive CLI piece. There's more than can be done here, but I think it's a good start in the right direction.
2021-01-10 03:50:49 +01:00
dependencies = [
Nu glob (#4818) * Fork glob. Normalise license holder * Fix more licenses * unwraps * bad doc test
2022-03-13 19:30:27 +01:00
"nu-glob",
Move path handling to nu-path (#3653) * fixes #3616
2021-06-20 01:07:26 +02:00
"nu-path",
Split nu-cli into nu-cli/nu-engine (#2898) We split off the evaluation engine part of nu-cli into its own crate. This helps improve build times for nu-cli by 17% in my tests. It also helps us see a bit better what's the core engine portion vs the part specific to the interactive CLI piece. There's more than can be done here, but I think it's a good start in the right direction.
2021-01-10 03:50:49 +01:00
"nu-protocol",
refactor all write_alls to ensure flushing (#5567)
2022-05-17 20:28:18 +02:00
"nu-utils",
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 03:30:48 +01:00
]
[MVP][WIP] `less` like pager (#6984) Run it as `explore`. #### example ```nu ls | explore ``` Configuration points in `config.nu` file. ``` # A 'explore' utility config explore_config: { highlight: { bg: 'yellow', fg: 'black' } status_bar: { bg: '#C4C9C6', fg: '#1D1F21' } command_bar: { fg: '#C4C9C6' } split_line: '#404040' cursor: true # selected_column: 'blue' # selected_row: { fg: 'yellow', bg: '#C1C2A3' } # selected_cell: { fg: 'white', bg: '#777777' } # line_shift: false, # line_index: false, # line_head_top: false, # line_head_bottom: false, } ``` You can start without a pipeline and type `explore` and it'll give you a few tips. ![image](https://user-images.githubusercontent.com/343840/205088971-a8c0262f-f222-4641-b13a-027fbd4f5e1a.png) If you type `:help` you an see the help screen with some information on what tui keybindings are available. ![image](https://user-images.githubusercontent.com/343840/205089461-c4c54217-7ec4-4fa0-96c0-643d68dc0062.png) From the `:help` screen you can now hit `i` and that puts you in `cursor` aka `inspection` mode and you can move the cursor left right up down and it you put it on an area such as `[table 5 rows]` and hit the enter key, you'll see something like this, which shows all the `:` commands. If you hit `esc` it will take you to the previous screen. ![image](https://user-images.githubusercontent.com/343840/205090155-3558a14b-87b7-4072-8dfb-dc8cc2ef4943.png) If you then type `:try` you'll get this type of window where you can type in the top portion and see results in the bottom. ![image](https://user-images.githubusercontent.com/343840/205089185-3c065551-0792-43d6-a13c-a52762856209.png) The `:nu` command is interesting because you can type pipelines like `:nu ls | sort-by type size` or another pipeline of your choosing such as `:nu sys` and that will show the table that looks like this, which we're calling "table mode". ![image](https://user-images.githubusercontent.com/343840/205090809-e686ff0f-6d0b-4347-8ed0-8c59adfbd741.png) If you hit the `t` key it will now transpose the view to look like this. ![image](https://user-images.githubusercontent.com/343840/205090948-a834d7f2-1713-4dfe-92fe-5432f287df3d.png) In table mode or transposed table mode you can use the `i` key to inspect any collapsed field like `{record 8 fields}`, `[table 16 rows]`, `[list x]`, etc. One of the original benefits was that when you're in a view that has a lot of columns, `explore` gives you the ability to scroll left, right, up, and down. `explore` is also smart enough to know when you're in table mode versus preview mode. If you do `open Cargo.toml | explore` you get this. ![image](https://user-images.githubusercontent.com/343840/205091822-cac79130-3a52-4ca8-9210-eba5be30ed58.png) If you type `open --raw Cargo.toml | explore` you get this where you can scroll left, right, up, down. This is called preview mode. ![image](https://user-images.githubusercontent.com/343840/205091990-69455191-ab78-4fea-a961-feafafc16d70.png) When you're in table mode, you can also type `:preview`. So, with `open --raw Cargo.toml | explore`, if you type `:preview`, it will look like this. ![image](https://user-images.githubusercontent.com/343840/205092569-436aa55a-0474-48d5-ab71-baddb1f43027.png) Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-12-01 16:32:10 +01:00
[[package]]
name = "nu-explore"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
[MVP][WIP] `less` like pager (#6984) Run it as `explore`. #### example ```nu ls | explore ``` Configuration points in `config.nu` file. ``` # A 'explore' utility config explore_config: { highlight: { bg: 'yellow', fg: 'black' } status_bar: { bg: '#C4C9C6', fg: '#1D1F21' } command_bar: { fg: '#C4C9C6' } split_line: '#404040' cursor: true # selected_column: 'blue' # selected_row: { fg: 'yellow', bg: '#C1C2A3' } # selected_cell: { fg: 'white', bg: '#777777' } # line_shift: false, # line_index: false, # line_head_top: false, # line_head_bottom: false, } ``` You can start without a pipeline and type `explore` and it'll give you a few tips. ![image](https://user-images.githubusercontent.com/343840/205088971-a8c0262f-f222-4641-b13a-027fbd4f5e1a.png) If you type `:help` you an see the help screen with some information on what tui keybindings are available. ![image](https://user-images.githubusercontent.com/343840/205089461-c4c54217-7ec4-4fa0-96c0-643d68dc0062.png) From the `:help` screen you can now hit `i` and that puts you in `cursor` aka `inspection` mode and you can move the cursor left right up down and it you put it on an area such as `[table 5 rows]` and hit the enter key, you'll see something like this, which shows all the `:` commands. If you hit `esc` it will take you to the previous screen. ![image](https://user-images.githubusercontent.com/343840/205090155-3558a14b-87b7-4072-8dfb-dc8cc2ef4943.png) If you then type `:try` you'll get this type of window where you can type in the top portion and see results in the bottom. ![image](https://user-images.githubusercontent.com/343840/205089185-3c065551-0792-43d6-a13c-a52762856209.png) The `:nu` command is interesting because you can type pipelines like `:nu ls | sort-by type size` or another pipeline of your choosing such as `:nu sys` and that will show the table that looks like this, which we're calling "table mode". ![image](https://user-images.githubusercontent.com/343840/205090809-e686ff0f-6d0b-4347-8ed0-8c59adfbd741.png) If you hit the `t` key it will now transpose the view to look like this. ![image](https://user-images.githubusercontent.com/343840/205090948-a834d7f2-1713-4dfe-92fe-5432f287df3d.png) In table mode or transposed table mode you can use the `i` key to inspect any collapsed field like `{record 8 fields}`, `[table 16 rows]`, `[list x]`, etc. One of the original benefits was that when you're in a view that has a lot of columns, `explore` gives you the ability to scroll left, right, up, and down. `explore` is also smart enough to know when you're in table mode versus preview mode. If you do `open Cargo.toml | explore` you get this. ![image](https://user-images.githubusercontent.com/343840/205091822-cac79130-3a52-4ca8-9210-eba5be30ed58.png) If you type `open --raw Cargo.toml | explore` you get this where you can scroll left, right, up, down. This is called preview mode. ![image](https://user-images.githubusercontent.com/343840/205091990-69455191-ab78-4fea-a961-feafafc16d70.png) When you're in table mode, you can also type `:preview`. So, with `open --raw Cargo.toml | explore`, if you type `:preview`, it will look like this. ![image](https://user-images.githubusercontent.com/343840/205092569-436aa55a-0474-48d5-ab71-baddb1f43027.png) Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-12-01 16:32:10 +01:00
dependencies = [
Remove duplicated dependency on `ansi-str 0.7` (#9641) # Description `tabled`/`papergrid` already use `ansi-str 0.8` while `nu-explore` itself was still depending on `0.7`. Single fix necessary to adapt to the new API. cc @zhiburt # User-Facing Changes None
2023-07-10 09:24:08 +02:00
"ansi-str",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"crossterm",
Patch explore 4 (#7517) ref #7339 - This PR updates explore to take some of the colors from nushell, namely the line colors and the ls_colors. note: Not sure why this regression appeared maybe it's a feature or it's no longer supposed to be supported? Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-12-18 15:43:15 +01:00
"lscolors",
Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787) # Description Now use `nu-ansi-term` 0.49 Small adjustments to accommodate breaking changes. # User-Facing Changes None
2023-07-24 13:16:18 +02:00
"nu-ansi-term",
[MVP][WIP] `less` like pager (#6984) Run it as `explore`. #### example ```nu ls | explore ``` Configuration points in `config.nu` file. ``` # A 'explore' utility config explore_config: { highlight: { bg: 'yellow', fg: 'black' } status_bar: { bg: '#C4C9C6', fg: '#1D1F21' } command_bar: { fg: '#C4C9C6' } split_line: '#404040' cursor: true # selected_column: 'blue' # selected_row: { fg: 'yellow', bg: '#C1C2A3' } # selected_cell: { fg: 'white', bg: '#777777' } # line_shift: false, # line_index: false, # line_head_top: false, # line_head_bottom: false, } ``` You can start without a pipeline and type `explore` and it'll give you a few tips. ![image](https://user-images.githubusercontent.com/343840/205088971-a8c0262f-f222-4641-b13a-027fbd4f5e1a.png) If you type `:help` you an see the help screen with some information on what tui keybindings are available. ![image](https://user-images.githubusercontent.com/343840/205089461-c4c54217-7ec4-4fa0-96c0-643d68dc0062.png) From the `:help` screen you can now hit `i` and that puts you in `cursor` aka `inspection` mode and you can move the cursor left right up down and it you put it on an area such as `[table 5 rows]` and hit the enter key, you'll see something like this, which shows all the `:` commands. If you hit `esc` it will take you to the previous screen. ![image](https://user-images.githubusercontent.com/343840/205090155-3558a14b-87b7-4072-8dfb-dc8cc2ef4943.png) If you then type `:try` you'll get this type of window where you can type in the top portion and see results in the bottom. ![image](https://user-images.githubusercontent.com/343840/205089185-3c065551-0792-43d6-a13c-a52762856209.png) The `:nu` command is interesting because you can type pipelines like `:nu ls | sort-by type size` or another pipeline of your choosing such as `:nu sys` and that will show the table that looks like this, which we're calling "table mode". ![image](https://user-images.githubusercontent.com/343840/205090809-e686ff0f-6d0b-4347-8ed0-8c59adfbd741.png) If you hit the `t` key it will now transpose the view to look like this. ![image](https://user-images.githubusercontent.com/343840/205090948-a834d7f2-1713-4dfe-92fe-5432f287df3d.png) In table mode or transposed table mode you can use the `i` key to inspect any collapsed field like `{record 8 fields}`, `[table 16 rows]`, `[list x]`, etc. One of the original benefits was that when you're in a view that has a lot of columns, `explore` gives you the ability to scroll left, right, up, and down. `explore` is also smart enough to know when you're in table mode versus preview mode. If you do `open Cargo.toml | explore` you get this. ![image](https://user-images.githubusercontent.com/343840/205091822-cac79130-3a52-4ca8-9210-eba5be30ed58.png) If you type `open --raw Cargo.toml | explore` you get this where you can scroll left, right, up, down. This is called preview mode. ![image](https://user-images.githubusercontent.com/343840/205091990-69455191-ab78-4fea-a961-feafafc16d70.png) When you're in table mode, you can also type `:preview`. So, with `open --raw Cargo.toml | explore`, if you type `:preview`, it will look like this. ![image](https://user-images.githubusercontent.com/343840/205092569-436aa55a-0474-48d5-ab71-baddb1f43027.png) Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-12-01 16:32:10 +01:00
"nu-color-config",
"nu-engine",
nu-explore/ A few things (#7339) ref #7332 Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-12-16 16:47:07 +01:00
"nu-json",
[MVP][WIP] `less` like pager (#6984) Run it as `explore`. #### example ```nu ls | explore ``` Configuration points in `config.nu` file. ``` # A 'explore' utility config explore_config: { highlight: { bg: 'yellow', fg: 'black' } status_bar: { bg: '#C4C9C6', fg: '#1D1F21' } command_bar: { fg: '#C4C9C6' } split_line: '#404040' cursor: true # selected_column: 'blue' # selected_row: { fg: 'yellow', bg: '#C1C2A3' } # selected_cell: { fg: 'white', bg: '#777777' } # line_shift: false, # line_index: false, # line_head_top: false, # line_head_bottom: false, } ``` You can start without a pipeline and type `explore` and it'll give you a few tips. ![image](https://user-images.githubusercontent.com/343840/205088971-a8c0262f-f222-4641-b13a-027fbd4f5e1a.png) If you type `:help` you an see the help screen with some information on what tui keybindings are available. ![image](https://user-images.githubusercontent.com/343840/205089461-c4c54217-7ec4-4fa0-96c0-643d68dc0062.png) From the `:help` screen you can now hit `i` and that puts you in `cursor` aka `inspection` mode and you can move the cursor left right up down and it you put it on an area such as `[table 5 rows]` and hit the enter key, you'll see something like this, which shows all the `:` commands. If you hit `esc` it will take you to the previous screen. ![image](https://user-images.githubusercontent.com/343840/205090155-3558a14b-87b7-4072-8dfb-dc8cc2ef4943.png) If you then type `:try` you'll get this type of window where you can type in the top portion and see results in the bottom. ![image](https://user-images.githubusercontent.com/343840/205089185-3c065551-0792-43d6-a13c-a52762856209.png) The `:nu` command is interesting because you can type pipelines like `:nu ls | sort-by type size` or another pipeline of your choosing such as `:nu sys` and that will show the table that looks like this, which we're calling "table mode". ![image](https://user-images.githubusercontent.com/343840/205090809-e686ff0f-6d0b-4347-8ed0-8c59adfbd741.png) If you hit the `t` key it will now transpose the view to look like this. ![image](https://user-images.githubusercontent.com/343840/205090948-a834d7f2-1713-4dfe-92fe-5432f287df3d.png) In table mode or transposed table mode you can use the `i` key to inspect any collapsed field like `{record 8 fields}`, `[table 16 rows]`, `[list x]`, etc. One of the original benefits was that when you're in a view that has a lot of columns, `explore` gives you the ability to scroll left, right, up, and down. `explore` is also smart enough to know when you're in table mode versus preview mode. If you do `open Cargo.toml | explore` you get this. ![image](https://user-images.githubusercontent.com/343840/205091822-cac79130-3a52-4ca8-9210-eba5be30ed58.png) If you type `open --raw Cargo.toml | explore` you get this where you can scroll left, right, up, down. This is called preview mode. ![image](https://user-images.githubusercontent.com/343840/205091990-69455191-ab78-4fea-a961-feafafc16d70.png) When you're in table mode, you can also type `:preview`. So, with `open --raw Cargo.toml | explore`, if you type `:preview`, it will look like this. ![image](https://user-images.githubusercontent.com/343840/205092569-436aa55a-0474-48d5-ab71-baddb1f43027.png) Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-12-01 16:32:10 +01:00
"nu-parser",
"nu-protocol",
"nu-table",
Patch explore 4 (#7517) ref #7339 - This PR updates explore to take some of the colors from nushell, namely the line colors and the ls_colors. note: Not sure why this regression appeared maybe it's a feature or it's no longer supposed to be supported? Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-12-18 15:43:15 +01:00
"nu-utils",
using ratatui instead of tui (#8952) # Description Refer to https://github.com/fdehau/tui-rs/issues/654, I found that tui maybe un-maintained, instead, I'd suggest to use an actively fork https://github.com/tui-rs-revival/ratatui cc: @zhiburt # User-Facing Changes NaN
2023-04-26 01:07:23 +02:00
"ratatui",
[MVP][WIP] `less` like pager (#6984) Run it as `explore`. #### example ```nu ls | explore ``` Configuration points in `config.nu` file. ``` # A 'explore' utility config explore_config: { highlight: { bg: 'yellow', fg: 'black' } status_bar: { bg: '#C4C9C6', fg: '#1D1F21' } command_bar: { fg: '#C4C9C6' } split_line: '#404040' cursor: true # selected_column: 'blue' # selected_row: { fg: 'yellow', bg: '#C1C2A3' } # selected_cell: { fg: 'white', bg: '#777777' } # line_shift: false, # line_index: false, # line_head_top: false, # line_head_bottom: false, } ``` You can start without a pipeline and type `explore` and it'll give you a few tips. ![image](https://user-images.githubusercontent.com/343840/205088971-a8c0262f-f222-4641-b13a-027fbd4f5e1a.png) If you type `:help` you an see the help screen with some information on what tui keybindings are available. ![image](https://user-images.githubusercontent.com/343840/205089461-c4c54217-7ec4-4fa0-96c0-643d68dc0062.png) From the `:help` screen you can now hit `i` and that puts you in `cursor` aka `inspection` mode and you can move the cursor left right up down and it you put it on an area such as `[table 5 rows]` and hit the enter key, you'll see something like this, which shows all the `:` commands. If you hit `esc` it will take you to the previous screen. ![image](https://user-images.githubusercontent.com/343840/205090155-3558a14b-87b7-4072-8dfb-dc8cc2ef4943.png) If you then type `:try` you'll get this type of window where you can type in the top portion and see results in the bottom. ![image](https://user-images.githubusercontent.com/343840/205089185-3c065551-0792-43d6-a13c-a52762856209.png) The `:nu` command is interesting because you can type pipelines like `:nu ls | sort-by type size` or another pipeline of your choosing such as `:nu sys` and that will show the table that looks like this, which we're calling "table mode". ![image](https://user-images.githubusercontent.com/343840/205090809-e686ff0f-6d0b-4347-8ed0-8c59adfbd741.png) If you hit the `t` key it will now transpose the view to look like this. ![image](https://user-images.githubusercontent.com/343840/205090948-a834d7f2-1713-4dfe-92fe-5432f287df3d.png) In table mode or transposed table mode you can use the `i` key to inspect any collapsed field like `{record 8 fields}`, `[table 16 rows]`, `[list x]`, etc. One of the original benefits was that when you're in a view that has a lot of columns, `explore` gives you the ability to scroll left, right, up, and down. `explore` is also smart enough to know when you're in table mode versus preview mode. If you do `open Cargo.toml | explore` you get this. ![image](https://user-images.githubusercontent.com/343840/205091822-cac79130-3a52-4ca8-9210-eba5be30ed58.png) If you type `open --raw Cargo.toml | explore` you get this where you can scroll left, right, up, down. This is called preview mode. ![image](https://user-images.githubusercontent.com/343840/205091990-69455191-ab78-4fea-a961-feafafc16d70.png) When you're in table mode, you can also type `:preview`. So, with `open --raw Cargo.toml | explore`, if you type `:preview`, it will look like this. ![image](https://user-images.githubusercontent.com/343840/205092569-436aa55a-0474-48d5-ab71-baddb1f43027.png) Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-12-01 16:32:10 +01:00
"strip-ansi-escapes",
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
"terminal_size 0.2.6",
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
"unicode-width",
[MVP][WIP] `less` like pager (#6984) Run it as `explore`. #### example ```nu ls | explore ``` Configuration points in `config.nu` file. ``` # A 'explore' utility config explore_config: { highlight: { bg: 'yellow', fg: 'black' } status_bar: { bg: '#C4C9C6', fg: '#1D1F21' } command_bar: { fg: '#C4C9C6' } split_line: '#404040' cursor: true # selected_column: 'blue' # selected_row: { fg: 'yellow', bg: '#C1C2A3' } # selected_cell: { fg: 'white', bg: '#777777' } # line_shift: false, # line_index: false, # line_head_top: false, # line_head_bottom: false, } ``` You can start without a pipeline and type `explore` and it'll give you a few tips. ![image](https://user-images.githubusercontent.com/343840/205088971-a8c0262f-f222-4641-b13a-027fbd4f5e1a.png) If you type `:help` you an see the help screen with some information on what tui keybindings are available. ![image](https://user-images.githubusercontent.com/343840/205089461-c4c54217-7ec4-4fa0-96c0-643d68dc0062.png) From the `:help` screen you can now hit `i` and that puts you in `cursor` aka `inspection` mode and you can move the cursor left right up down and it you put it on an area such as `[table 5 rows]` and hit the enter key, you'll see something like this, which shows all the `:` commands. If you hit `esc` it will take you to the previous screen. ![image](https://user-images.githubusercontent.com/343840/205090155-3558a14b-87b7-4072-8dfb-dc8cc2ef4943.png) If you then type `:try` you'll get this type of window where you can type in the top portion and see results in the bottom. ![image](https://user-images.githubusercontent.com/343840/205089185-3c065551-0792-43d6-a13c-a52762856209.png) The `:nu` command is interesting because you can type pipelines like `:nu ls | sort-by type size` or another pipeline of your choosing such as `:nu sys` and that will show the table that looks like this, which we're calling "table mode". ![image](https://user-images.githubusercontent.com/343840/205090809-e686ff0f-6d0b-4347-8ed0-8c59adfbd741.png) If you hit the `t` key it will now transpose the view to look like this. ![image](https://user-images.githubusercontent.com/343840/205090948-a834d7f2-1713-4dfe-92fe-5432f287df3d.png) In table mode or transposed table mode you can use the `i` key to inspect any collapsed field like `{record 8 fields}`, `[table 16 rows]`, `[list x]`, etc. One of the original benefits was that when you're in a view that has a lot of columns, `explore` gives you the ability to scroll left, right, up, and down. `explore` is also smart enough to know when you're in table mode versus preview mode. If you do `open Cargo.toml | explore` you get this. ![image](https://user-images.githubusercontent.com/343840/205091822-cac79130-3a52-4ca8-9210-eba5be30ed58.png) If you type `open --raw Cargo.toml | explore` you get this where you can scroll left, right, up, down. This is called preview mode. ![image](https://user-images.githubusercontent.com/343840/205091990-69455191-ab78-4fea-a961-feafafc16d70.png) When you're in table mode, you can also type `:preview`. So, with `open --raw Cargo.toml | explore`, if you type `:preview`, it will look like this. ![image](https://user-images.githubusercontent.com/343840/205092569-436aa55a-0474-48d5-ab71-baddb1f43027.png) Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-12-01 16:32:10 +01:00
]
Nu glob (#4818) * Fork glob. Normalise license holder * Fix more licenses * unwraps * bad doc test
2022-03-13 19:30:27 +01:00
[[package]]
name = "nu-glob"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Nu glob (#4818) * Fork glob. Normalise license holder * Fix more licenses * unwraps * bad doc test
2022-03-13 19:30:27 +01:00
dependencies = [
"doc-comment",
]
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
[[package]]
name = "nu-json"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
dependencies = [
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"linked-hash-map",
"num-traits",
"serde",
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
]
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
[[package]]
name = "nu-lsp"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
dependencies = [
"assert-json-diff",
Implement LSP Text Document Synchronization (#10941)
2023-11-16 00:35:48 +01:00
"crossbeam-channel",
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
"lsp-server",
"lsp-types",
"miette",
"nu-cli",
"nu-cmd-lang",
"nu-command",
"nu-parser",
"nu-protocol",
"nu-test-support",
"reedline",
"ropey",
"serde",
"serde_json",
"tempfile",
]
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 03:30:48 +01:00
[[package]]
name = "nu-parser"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
dependencies = [
prevent alias name from being filesize or number (#6595) * prevent alias name from being filesize or number * add test * fmt
2022-09-29 00:08:38 +02:00
"bytesize",
Date literals (#4619) * Date literals * update deps * Add date+duration
2022-02-24 03:02:48 +01:00
"chrono",
Bump itertools from 0.11.0 to 0.12.0 (#11360) Bumps [itertools](https://github.com/rust-itertools/itertools) from 0.11.0 to 0.12.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rust-itertools/itertools/blob/master/CHANGELOG.md">itertools's changelog</a>.</em></p> <blockquote> <h2>0.12.0</h2> <h3>Breaking</h3> <ul> <li>Made <code>take_while_inclusive</code> consume iterator by value (<a href="https://redirect.github.com/rust-itertools/itertools/issues/709">#709</a>)</li> <li>Added <code>Clone</code> bound to <code>Unique</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/777">#777</a>)</li> </ul> <h3>Added</h3> <ul> <li>Added <code>Itertools::try_len</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/723">#723</a>)</li> <li>Added free function <code>sort_unstable</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/796">#796</a>)</li> <li>Added <code>GroupMap::fold_with</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/778">#778</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/785">#785</a>)</li> <li>Added <code>PeekNth::{peek_mut, peek_nth_mut}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/716">#716</a>)</li> <li>Added <code>PeekNth::{next_if, next_if_eq}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/734">#734</a>)</li> <li>Added conversion into <code>(Option&lt;A&gt;,Option&lt;B&gt;)</code> to <code>EitherOrBoth</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/713">#713</a>)</li> <li>Added conversion from <code>Either&lt;A, B&gt;</code> to <code>EitherOrBoth&lt;A, B&gt;</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/715">#715</a>)</li> <li>Implemented <code>ExactSizeIterator</code> for <code>Tuples</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/761">#761</a>)</li> <li>Implemented <code>ExactSizeIterator</code> for <code>(Circular)TupleWindows</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/752">#752</a>)</li> <li>Made <code>EitherOrBoth&lt;T&gt;</code> a shorthand for <code>EitherOrBoth&lt;T, T&gt;</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/719">#719</a>)</li> </ul> <h3>Changed</h3> <ul> <li>Added missing <code>#[must_use]</code> annotations on iterator adaptors (<a href="https://redirect.github.com/rust-itertools/itertools/issues/794">#794</a>)</li> <li>Made <code>Combinations</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/795">#795</a>)</li> <li>Made <code>Intersperse(With)</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/797">#797</a>)</li> <li>Made <code>Permutations</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/793">#793</a>)</li> <li>Made <code>Product</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/800">#800</a>)</li> <li>Made <code>TupleWindows</code> lazy (<a href="https://redirect.github.com/rust-itertools/itertools/issues/602">#602</a>)</li> <li>Specialized <code>Combinations::{count, size_hint}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/729">#729</a>)</li> <li>Specialized <code>CombinationsWithReplacement::{count, size_hint}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/737">#737</a>)</li> <li>Specialized <code>Powerset::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/765">#765</a>)</li> <li>Specialized <code>Powerset::count</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/735">#735</a>)</li> <li>Specialized <code>TupleCombinations::{count, size_hint}</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/763">#763</a>)</li> <li>Specialized <code>TupleCombinations::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/775">#775</a>)</li> <li>Specialized <code>WhileSome::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/780">#780</a>)</li> <li>Specialized <code>WithPosition::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/772">#772</a>)</li> <li>Specialized <code>ZipLongest::fold</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/774">#774</a>)</li> <li>Changed <code>{min, max}_set*</code> operations require <code>alloc</code> feature, instead of <code>std</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/760">#760</a>)</li> <li>Improved documentation of <code>tree_fold1</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/787">#787</a>)</li> <li>Improved documentation of <code>permutations</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/724">#724</a>)</li> <li>Fixed typo in documentation of <code>multiunzip</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/770">#770</a>)</li> </ul> <h3>Notable Internal Changes</h3> <ul> <li>Improved specialization tests (<a href="https://redirect.github.com/rust-itertools/itertools/issues/799">#799</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/786">#786</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/782">#782</a>)</li> <li>Simplified implementation of <code>Permutations</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/739">#739</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/748">#748</a>, <a href="https://redirect.github.com/rust-itertools/itertools/issues/790">#790</a>)</li> <li>Combined <code>Merge</code>/<code>MergeBy</code>/<code>MergeJoinBy</code> implementations (<a href="https://redirect.github.com/rust-itertools/itertools/issues/736">#736</a>)</li> <li>Simplified <code>Permutations::size_hint</code> (<a href="https://redirect.github.com/rust-itertools/itertools/issues/739">#739</a>)</li> <li>Fix wrapping arithmetic in benchmarks (<a href="https://redirect.github.com/rust-itertools/itertools/issues/770">#770</a>)</li> <li>Enforced <code>rustfmt</code> in CI (<a href="https://redirect.github.com/rust-itertools/itertools/issues/751">#751</a>)</li> <li>Disallowed compile warnings in CI (<a href="https://redirect.github.com/rust-itertools/itertools/issues/720">#720</a>)</li> <li>Used <code>cargo hack</code> to check MSRV (<a href="https://redirect.github.com/rust-itertools/itertools/issues/754">#754</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rust-itertools/itertools/commit/98ecabb47d7147dae06fc3fa400ec758947194f3"><code>98ecabb</code></a> chore: Release itertools version 0.12.0</li> <li><a href="https://github.com/rust-itertools/itertools/commit/22fc427ac5282cbdafccfe38a686ec1d3b720120"><code>22fc427</code></a> prepare v0.12.0 release</li> <li><a href="https://github.com/rust-itertools/itertools/commit/6d291786a9c9686a3997d93c513bd18326611fe5"><code>6d29178</code></a> Document the field <code>a_cur</code> of <code>Product</code></li> <li><a href="https://github.com/rust-itertools/itertools/commit/bf2b0129d1d3cc1ffa733059f3088adb6d745fe6"><code>bf2b012</code></a> Better <code>Product::size_hint</code></li> <li><a href="https://github.com/rust-itertools/itertools/commit/8d07f6b8566a515118ca8b119f358b73d483152b"><code>8d07f6b</code></a> Make <code>Product</code> lazy</li> <li><a href="https://github.com/rust-itertools/itertools/commit/d7e6bab9fd0ad79130692f8e48e21375362a7614"><code>d7e6bab</code></a> Document the field <code>peek</code> of <code>IntersperseWith</code></li> <li><a href="https://github.com/rust-itertools/itertools/commit/9b01a118919f0d1f7c3327d1a15a5eb660f3912e"><code>9b01a11</code></a> Make <code>IntersperseWith</code> lazy</li> <li><a href="https://github.com/rust-itertools/itertools/commit/4f22173b93a2eb58da16b7da6d08e6c3f1c56544"><code>4f22173</code></a> Refactor <code>IntersperseWith::next</code></li> <li><a href="https://github.com/rust-itertools/itertools/commit/b76172b412116356ebef05b884a6e4def63a4d17"><code>b76172b</code></a> chore: adjust docs to reflect discussion in the PR</li> <li><a href="https://github.com/rust-itertools/itertools/commit/955927f6c424f895ad7519d413bc5718e6ad26bf"><code>955927f</code></a> chore: fixup docs of tree_fold1</li> <li>Additional commits viewable in <a href="https://github.com/rust-itertools/itertools/compare/v0.11.0...v0.12.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=itertools&package-manager=cargo&previous-version=0.11.0&new-version=0.12.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-12-20 15:58:07 +01:00
"itertools 0.12.0",
Add parser tracing, fix 629 (#638)
2022-01-01 22:42:50 +01:00
"log",
when spawned process during register plugin, pass env to child process (#6261) * when spawned process during register plugin, pass env to child process * tweak comment * tweak comment * remove trailing whitespace Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-08 14:26:49 +02:00
"nu-engine",
Expand globs and filepaths (#348)
2021-11-18 20:32:27 +01:00
"nu-path",
Plugin repeated (#417) * not repeated decl in file and help * implemented heashmap for repeated * sorted scope commands
2021-12-03 15:29:55 +01:00
"nu-plugin",
Add nu-protocol
2021-09-02 03:29:43 +02:00
"nu-protocol",
Bump rstest from 0.17.0 to 0.18.1 (#9782)
2023-08-08 19:11:05 +02:00
"rstest",
Plugins signature load (#349) * saving signatures to file * loading plugin signature from file * is_plugin column for help command
2021-11-19 03:51:42 +01:00
"serde_json",
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 03:30:48 +01:00
]
Move path handling to nu-path (#3653) * fixes #3616
2021-06-20 01:07:26 +02:00
[[package]]
name = "nu-path"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Move path handling to nu-path (#3653) * fixes #3616
2021-06-20 01:07:26 +02:00
dependencies = [
"dirs-next",
Try not to use verbatim paths for UNC shares (#6824)
2022-10-22 18:51:52 +02:00
"omnipath",
Adding ~user tilde recognition in file paths (#5251) * Added search terms to math commands * Attempts to add ~user. From: // Extend this to work with "~user" style of home paths * Clippy recommendation * clippy suggestions, again. * fixing non-compilation on windows and macos * fmt apparently does not like my imports * even more clippy issues. * less expect(), single conversion, match. Should work for MacOS too. * Attempted to add functionality for windows: all it does is take the home path of current user, and replace the username. * silly mistake in Windows version of user_home_dir() * Update tilde.rs * user_home_dir now returns a path instead of a string - should be smoother with no conversions to string * clippy warnings * clippy warnings 2 * Changed user_home_dir to return PathBuf now. * Changed user_home_dir to return PathBuf now. * forgot to fmt * fixed windows build errors from modifying pathbuf but not returning it * fixed windows clippy errors from returning () instead of pathbuf * forgot to fmt * borrowed path did not live long enough. * previously, path.push did not work because rest_of_path started with "/" - it was not relative. Removing the / makes it a relative path again. * Issue fixed. * Update tilde.rs * fmt. * There is now a zero chance of panic. All expect()s have been removed.
2022-04-25 00:12:57 +02:00
"pwd",
Move path handling to nu-path (#3653) * fixes #3616
2021-06-20 01:07:26 +02:00
]
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01:00
[[package]]
name = "nu-plugin"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
plugin crate
2021-10-28 08:12:33 +02:00
dependencies = [
Add CustomValue support to plugins (#6070) * Skeleton implementation Lots and lots of TODOs * Bootstrap simple CustomValue plugin support test * Create nu_plugin_custom_value * Skeleton for nu_plugin_custom_values * Return a custom value from plugin * Encode CustomValues from plugin calls as PluginResponse::PluginData * Add new PluginCall variant CollapseCustomValue * Handle CollapseCustomValue plugin calls * Add CallInput::Data variant to CallInfo inputs * Handle CallInfo with CallInput::Data plugin calls * Send CallInput::Data if Value is PluginCustomValue from plugin calls * Remove unnecessary boxing of plugins CallInfo * Add fields needed to collapse PluginCustomValue to it * Document PluginCustomValue and its purpose * Impl collapsing using plugin calls in PluginCustomValue::to_base_value * Implement proper typetag based deserialization for CoolCustomValue * Test demonstrating that passing back a custom value to plugin works * Added a failing test for describing plugin CustomValues * Support describe for PluginCustomValues - Add name to PluginResponse::PluginData - Also turn it into a struct for clarity - Add name to PluginCustomValue - Return name field from PluginCustomValue * Demonstrate that plugins can create and handle multiple CustomValues * Add bincode to nu-plugin dependencies This is for demonstration purposes, any schemaless binary seralization format will work. I picked bincode since it's the most popular for Rust but there are defintely better options out there for this usecase * serde_json::Value -> Vec<u8> * Update capnp schema for new CallInfo.input field * Move call_input capnp serialization and deserialization into new file * Deserialize Value's span from Value itself instead of passing call.head I am not sure if this was correct and I am breaking it or if it was a bug, I don't fully understand how nu creates and uses Spans. What should reuse spans and what should recreate new ones? But yeah it felt weird that the Value's Span was being ignored since in the json serializer just uses the Value's Span * Add call_info value round trip test * Add capnp CallInput::Data serialization and deserialization support * Add CallInfo::CollapseCustomValue to capnp schema * Add capnp PluginCall::CollapseCustomValue serialization and deserialization support * Add PluginResponse::PluginData to capnp schema * Add capnp PluginResponse::PluginData serialization and deserialization support * Switch plugins::custom_values tests to capnp Both json and capnp would work now! Sadly I can't choose both at the same time :( * Add missing JsonSerializer round trip tests * Handle plugin returning PluginData as a response to CollapseCustomValue * Refactor plugin calling into a reusable function Many less levels of indentation now! * Export PluginData from nu_plugin So plugins can create their very own serve_plugin with whatever CustomValue behavior they may desire * Error if CustomValue cannot be handled by Plugin
2022-07-25 18:32:56 +02:00
"bincode",
Plugin with evaluated call (#393) * plugin trait * impl of trait * record and absolute path * plugin example crate * clippy error * correcting cargo * evaluated call for plugin
2021-12-02 06:42:56 +01:00
"nu-engine",
plugin crate
2021-10-28 08:12:33 +02:00
"nu-protocol",
add MessagePack as a plugin protocol (#6370)
2022-08-21 13:13:38 +02:00
"rmp-serde",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"serde",
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01:00
"serde_json",
]
add nu-pretty-hex, add into binary, update binaryview (#3370) * add nu-pretty-hex, add into binary, update binaryview * updated parameter name, updated examples * fixed nu-pretty-hex test * fixed tests again! and added a no color option to pretty-hex
2021-05-01 18:12:25 +02:00
[[package]]
name = "nu-pretty-hex"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Add string stream and binary stream, add text decoding (#570) * WIP * Add binary/string streams and text decoding * Make string collection fallible * Oops, forgot pretty hex * Oops, forgot pretty hex * clippy
2021-12-24 08:22:11 +01:00
dependencies = [
Consider space for single `...` column not enough space (#6080) * nu-table: Refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: consider space for single `...` column not enough space Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-19 19:35:25 +02:00
"heapless",
Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787) # Description Now use `nu-ansi-term` 0.49 Small adjustments to accommodate breaking changes. # User-Facing Changes None
2023-07-24 13:16:18 +02:00
"nu-ansi-term",
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"rand",
add nu-pretty-hex, add into binary, update binaryview (#3370) * add nu-pretty-hex, add into binary, update binaryview * updated parameter name, updated examples * fixed nu-pretty-hex test * fixed tests again! and added a no color option to pretty-hex
2021-05-01 18:12:25 +02:00
]
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 03:30:48 +01:00
[[package]]
name = "nu-protocol"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
WIP
2021-09-02 10:25:22 +02:00
dependencies = [
Add unit parsing and eval support
2021-10-05 04:27:39 +02:00
"byte-unit",
"chrono",
"chrono-humanize",
Bump `fancy-regex` to single `0.12.0` version (#11389) Supersedes #11039 that was broken due to dependabot not correctly taking the workspace into account (this bug has been worked around in #11387)
2023-12-21 17:10:33 +01:00
"fancy-regex",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"indexmap",
Add LRU regex cache (#7587) Closes #7572 by adding a cache for compiled regexes of type `Arc<Mutex<LruCache<String, Regex>>>` to `EngineState` . The cache is limited to 100 entries (limit chosen arbitrarily) and evicts least-recently-used items first. This PR makes a noticeable difference when using regexes for `color_config`, e.g.: ```bash #first set string formatting in config.nu like: string: { if $in =~ '^#\w{6}$' { $in } else { 'white' } }` # then try displaying and exploring a table with many strings # this is instant after the PR, but takes hundreds of milliseconds before ['#ff0033', '#0025ee', '#0087aa', 'string', '#4101ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff', '#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff','#ff0033', '#0025ee', '#0087aa', 'string', '#6103ff'] ``` ## New dependency (`lru`) This uses [the popular `lru` crate](https://lib.rs/crates/lru). The new dependency adds 19.8KB to a Linux release build of Nushell. I think this is OK, especially since the crate can be useful elsewhere in Nu.
2022-12-23 23:30:04 +01:00
"lru",
Reduce required dependencies for diagnostics (#6648) Disable backtrace on miette - gimli crate requires several seconds Disable diagnostics on wax - depends on an outdated miette version Builds fine, no observable loss in diagnostics quality of life Removes 10 crates that have to be compiled.
2022-10-24 21:42:32 +02:00
"miette",
Make $nu constant (#10160)
2023-09-01 08:18:55 +02:00
"nu-path",
"nu-system",
`$env.config` now always holds a record with only valid values (#7309) # Description Closes #7059. Rather than generate a new Record each time $env.config is accessed (as described in that issue), instead `$env.config = ` now A) parses the input record, then B) un-parses it into a clean Record with only the valid values, and stores that as an env-var. The reasoning for this is that I believe `config_to_nu_record()` (the method that performs step B) will be useful in later PRs. (See below) As a result, this also "fixes" the following "bug": ``` 〉$env.config = 'butts' $env.config is not a record 〉$env.config butts ``` ~~Instead, `$env.config = 'butts'` now turns `$env.config` into the default (not the default config.nu, but `Config::default()`, which notably has empty keybindings, color_config, menus and hooks vecs).~~ This doesn't attempt to fix #7110. cc @Kangaxx-0 # Example of new behaviour OLD: ``` 〉$env.config = ($env.config | merge { foo: 1 }) $env.config.foo is an unknown config setting 〉$env.config.foo 1 ``` NEW: ``` 〉$env.config = ($env.config | merge { foo: 1 }) Error: × Config record contains invalid values or unknown settings Error: × Error while applying config changes ╭─[entry #1:1:1] 1 │ $env.config = ($env.config | merge { foo: 1 }) · ┬ · ╰── $env.config.foo is an unknown config setting ╰──── help: This value has been removed from your $env.config record. 〉$env.config.foo Error: nu::shell::column_not_found (link) × Cannot find column ╭─[entry #1:1:1] 1 │ $env.config = ($env.config | merge { foo: 1 }) · ──┬── · ╰── value originates here ╰──── ╭─[entry #2:1:1] 1 │ $env.config.foo · ─┬─ · ╰── cannot find column 'foo' ╰──── ``` # Example of new errors OLD: ``` $env.config.cd.baz is an unknown config setting $env.config.foo is an unknown config setting $env.config.bar is an unknown config setting $env.config.table.qux is an unknown config setting $env.config.history.qux is an unknown config setting ``` NEW: ``` Error: × Config record contains invalid values or unknown settings Error: × Error while applying config changes ╭─[C:\Users\Leon\AppData\Roaming\nushell\config.nu:267:1] 267 │ abbreviations: true # allows `cd s/o/f` to expand to `cd some/other/folder` 268 │ baz: 3, · ┬ · ╰── $env.config.cd.baz is an unknown config setting 269 │ } ╰──── help: This value has been removed from your $env.config record. Error: × Error while applying config changes ╭─[C:\Users\Leon\AppData\Roaming\nushell\config.nu:269:1] 269 │ } 270 │ foo: 1, · ┬ · ╰── $env.config.foo is an unknown config setting 271 │ bar: 2, ╰──── help: This value has been removed from your $env.config record. Error: × Error while applying config changes ╭─[C:\Users\Leon\AppData\Roaming\nushell\config.nu:270:1] 270 │ foo: 1, 271 │ bar: 2, · ┬ · ╰── $env.config.bar is an unknown config setting ╰──── help: This value has been removed from your $env.config record. Error: × Error while applying config changes ╭─[C:\Users\Leon\AppData\Roaming\nushell\config.nu:279:1] 279 │ } 280 │ qux: 4, · ┬ · ╰── $env.config.table.qux is an unknown config setting 281 │ } ╰──── help: This value has been removed from your $env.config record. Error: × Error while applying config changes ╭─[C:\Users\Leon\AppData\Roaming\nushell\config.nu:285:1] 285 │ file_format: "plaintext" # "sqlite" or "plaintext" 286 │ qux: 2 · ┬ · ╰── $env.config.history.qux is an unknown config setting 287 │ } ╰──── help: This value has been removed from your $env.config record. ``` # User-Facing Changes See above. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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.
2022-12-10 14:34:46 +01:00
"nu-test-support",
refactor all write_alls to ensure flushing (#5567)
2022-05-17 20:28:18 +02:00
"nu-utils",
Filesize formatting (#456) * configure the format of filesize * type-o * removed some comments * updated tests * accomodated filesize_metric better, added test
2021-12-09 20:19:36 +01:00
"num-format",
Bump rstest from 0.17.0 to 0.18.1 (#9782)
2023-08-08 19:11:05 +02:00
"rstest",
Add 'from json'
2021-10-01 07:11:49 +02:00
"serde",
Plugins signature load (#349) * saving signatures to file * loading plugin signature from file * is_plugin column for help command
2021-11-19 03:51:42 +01:00
"serde_json",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"strum",
"strum_macros",
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
"thiserror",
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
"typetag",
WIP
2021-09-02 10:25:22 +02:00
]
Add nu-protocol
2021-09-02 03:29:43 +02:00
stdlib: make the library a standalone crate (#8770) # Description as we now have a prelude thanks to #8627, i'd like to work on the structure of the library :yum: and i think the first step is to make it a true standalone crate :smirk: this PR - moves all the library from `crates/nu-utils/standard_library/` to `crates/nu-std/` - moves the `rust` loading code from `src/run.rs` to `crates/nu-std/src/lib.rs`
2023-04-07 22:12:27 +02:00
[[package]]
name = "nu-std"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
stdlib: make the library a standalone crate (#8770) # Description as we now have a prelude thanks to #8627, i'd like to work on the structure of the library :yum: and i think the first step is to make it a true standalone crate :smirk: this PR - moves all the library from `crates/nu-utils/standard_library/` to `crates/nu-std/` - moves the `rust` loading code from `src/run.rs` to `crates/nu-std/src/lib.rs`
2023-04-07 22:12:27 +02:00
dependencies = [
"miette",
Add virtual path abstraction layer (#9245)
2023-05-23 22:48:50 +02:00
"nu-engine",
stdlib: make the library a standalone crate (#8770) # Description as we now have a prelude thanks to #8627, i'd like to work on the structure of the library :yum: and i think the first step is to make it a true standalone crate :smirk: this PR - moves all the library from `crates/nu-utils/standard_library/` to `crates/nu-std/` - moves the `rust` loading code from `src/run.rs` to `crates/nu-std/src/lib.rs`
2023-04-07 22:12:27 +02:00
"nu-parser",
"nu-protocol",
]
Add nu-system and rewrite ps command (#734) * Add nu-system and rewrite ps command * Add more deps * Add more deps * clippy * clippy * clippy * clippy * clippy * clippy
2022-01-14 07:20:53 +01:00
[[package]]
name = "nu-system"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Add nu-system and rewrite ps command (#734) * Add nu-system and rewrite ps command * Add more deps * Add more deps * clippy * clippy * clippy * clippy * clippy * clippy
2022-01-14 07:20:53 +01:00
dependencies = [
"chrono",
"libc",
"libproc",
Fixes for `ps` on Linux (#6858) * Fix ps returning nothing when process dies * Fix ps CPU calcs on Linux, remove unused thread code
2022-10-22 18:54:46 +02:00
"log",
Fix ps command CPU usage on Apple Silicon M1 macs. #4142 (#6457) * Fix ps command CPU usage on Apple Silicon M1 macs. #4142 The cpu user and system times returned my libproc are not in nanoseconds; they are in mach ticks units. This is not documented very well. The convert from mach ticks to ns, the kernel provides a timebase info function and datatype: https://developer.apple.com/documentation/driverkit/3433733-mach_timebase_info The commit makes the PS command work for me. * Cargo fmt of previous commit. * Clippy format suggestion Co-authored-by: Ondrej Baudys <ondrej.baudys@nextgen.net>
2022-09-01 08:09:52 +02:00
"mach2",
rename nushell's cp command to cp-old making coreutils the default cp (#10678) # Description This PR renames nushell's `cp` command to `cp-old` to make room for `ucp` to be renamed to `cp`, making the coreutils version of `cp` the default for nushell. After some period of time, we should remove `cp-old` entirely. # 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-10-11 01:13:28 +02:00
"nix",
Use nt-api 4 on Windows (#6949) * Bump nushell-sytem dep to ntapi 0.4 0.3.7 trigger a warning about code being incompatible with future rust versions. This is resolved in 0.4 https://github.com/MSxDOS/ntapi/issues/11 * Upgrade Cargo.lock for ntapi 0.4
2022-10-30 14:29:41 +01:00
"ntapi",
Windows ps update (#909) * query command with json, web, xml * query xml now working * clippy * comment out web tests * Initial work on query web For now we can query everything except tables * Support for querying tables Now we can query multiple tables just like before, now the only thing missing is the test coverage * Revert "Query plugin" * augment `ps -l` on windows to display more info Co-authored-by: Luccas Mateus de Medeiros Gomes <luccasmmg@gmail.com>
2022-02-01 22:05:26 +01:00
"once_cell",
Add nu-system and rewrite ps command (#734) * Add nu-system and rewrite ps command * Add more deps * Add more deps * clippy * clippy * clippy * clippy * clippy * clippy
2022-01-14 07:20:53 +01:00
"procfs",
Make $nu constant (#10160)
2023-09-01 08:18:55 +02:00
"sysinfo",
Replace `winapi` with `windows` (#11481) # Description `winapi` is not actively maintained, use the Microsoft blessed `windows` crate instead. # User-Facing Changes N/A
2024-01-04 18:17:19 +01:00
"windows 0.52.0",
Add nu-system and rewrite ps command (#734) * Add nu-system and rewrite ps command * Add more deps * Add more deps * clippy * clippy * clippy * clippy * clippy * clippy
2022-01-14 07:20:53 +01:00
]
Add a very silly table
2021-09-10 04:27:12 +02:00
[[package]]
name = "nu-table"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Add a very silly table
2021-09-10 04:27:12 +02:00
dependencies = [
Bump `fancy-regex` to single `0.12.0` version (#11389) Supersedes #11039 that was broken due to dependabot not correctly taking the workspace into account (this bug has been worked around in #11387)
2023-12-21 17:10:33 +01:00
"fancy-regex",
Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787) # Description Now use `nu-ansi-term` 0.49 Small adjustments to accommodate breaking changes. # User-Facing Changes None
2023-07-24 13:16:18 +02:00
"nu-ansi-term",
color_config now accepts closures as color values (#7141) # Description Closes #6909. You can now add closures to your `color_config` themes. Whenever a value would be printed with `table`, the closure is run with the value piped-in. The closure must return either a {fg,bg,attr} record or a color name (`'light_red'` etc.). This returned style is used to colour the value. This is entirely backwards-compatible with existing config.nu files. Example code excerpt: ``` let my_theme = { header: green_bold bool: { if $in { 'light_cyan' } else { 'light_red' } } int: purple_bold filesize: { |e| if $e == 0b { 'gray' } else if $e < 1mb { 'purple_bold' } else { 'cyan_bold' } } duration: purple_bold date: { (date now) - $in | if $in > 1wk { 'cyan_bold' } else if $in > 1day { 'green_bold' } else { 'yellow_bold' } } range: yellow_bold string: { if $in =~ '^#\w{6}$' { $in } else { 'white' } } nothing: white ``` Example output with this in effect: ![2022-11-16 12 47 23 AM - style_computer rs_-_nushell_-_VSCodium](https://user-images.githubusercontent.com/83939/201952558-482de05d-69c7-4bf2-91fc-d0964bf71264.png) ![2022-11-16 12 39 41 AM - style_computer rs_-_nushell_-_VSCodium](https://user-images.githubusercontent.com/83939/201952580-2384bb86-b680-40fe-8192-71bae396c738.png) ![2022-11-15 09 21 54 PM - run_external rs_-_nushell_-_VSCodium](https://user-images.githubusercontent.com/83939/201952601-343fc15d-e4a8-4a92-ad89-9a7d17d42748.png) Slightly important notes: * Some color_config names, namely "separator", "empty" and "hints", pipe in `null` instead of a value. * Currently, doing anything non-trivial inside a closure has an understandably big perf hit. I currently do not actually recommend something like `string: { if $in =~ '^#\w{6}$' { $in } else { 'white' } }` for serious work, mainly because of the abundance of string-type data in the world. Nevertheless, lesser-used types like "date" and "duration" work well with this. * I had to do some reorganisation in order to make it possible to call `eval_block()` that late in table rendering. I invented a new struct called "StyleComputer" which holds the engine_state and stack of the initial `table` command (implicit or explicit). * StyleComputer has a `compute()` method which takes a color_config name and a nu value, and always returns the correct Style, so you don't have to worry about A) the color_config value was set at all, B) whether it was set to a closure or not, or C) which default style to use in those cases. * Currently, errors encountered during execution of the closures are thrown in the garbage. Any other ideas are welcome. (Nonetheless, errors result in a huge perf hit when they are encountered. I think what should be done is to assume something terrible happened to the user's config and invalidate the StyleComputer for that `table` run, thus causing subsequent output to just be Style::default().) * More thorough tests are forthcoming - ran into some difficulty using `nu!` to take an alternative config, and for some reason `let-env config =` statements don't seem to work inside `nu!` pipelines(???) * The default config.nu has not been updated to make use of this yet. Do tell if you think I should incorporate that into this. # User-Facing Changes See above. # 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 --features=extra -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace --features=extra` to check that all tests pass # 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.
2022-12-17 14:07:56 +01:00
"nu-color-config",
"nu-engine",
add optional footer to table (#392) * add optional footer to table * missed a draw_table
2021-12-01 20:20:23 +01:00
"nu-protocol",
Refactor ansi stripping into `nu-utils` functions (#6966) Allows use of slightly optimized variants that check if they have to use the heavier vte parser. Tries to avoid unnnecessary allocations. Initial performance characteristics proven out in #4378. Also reduces boilerplate with right-ward drift.
2022-11-04 19:49:45 +01:00
"nu-utils",
Patch restore lead trail space bg color (#10351) ```nu $env.config.color_config.leading_trailing_space_bg = { bg: 'white' }; [[a b, 'c ']; [' 1 ' ' 2' '3 '] [' 4 ' "hello \n world " [' 1 ' 2 [1 ' 2 ' 3]]]] | table --expand ``` ![image](https://github.com/nushell/nushell/assets/20165848/01a35042-0e36-4c51-99a9-3011fabb551b) ref: #2794 close: #10317 note: test are not actually make scenes cause `nu!` strips colors. (Ideally it would need a flag to not do so) note: It does does does ... slower down quite a bit rendering... ( PS: Maybe it's better being a flag to `table` rather then a configuration option? PS: I am not sure why the logic was removed in a first place
2023-09-13 14:47:53 +02:00
"once_cell",
Revert "Add an option to move header on borders" (#9908) Reverts nushell/nushell#9796 This is just draft since we're seeing some issues with the latest fixes to table drawing that just landed with #9796. We're hoping to get these fixed, but if we're not able to fix them before the next release, we'll need to revert (hence this PR, just in case we need it).
2023-08-03 21:52:12 +02:00
"tabled",
Add a very silly table
2021-09-10 04:27:12 +02:00
]
moved `grid` to it's own crate named `nu-term-grid`
2021-10-07 17:32:39 +02:00
[[package]]
engine-q merge
2022-02-07 20:11:34 +01:00
name = "nu-term-grid"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Rename test-support to nu-test-support
2019-12-17 19:41:47 +01:00
dependencies = [
Refactor ansi stripping into `nu-utils` functions (#6966) Allows use of slightly optimized variants that check if they have to use the heavier vte parser. Tries to avoid unnnecessary allocations. Initial performance characteristics proven out in #4378. Also reduces boilerplate with right-ward drift.
2022-11-04 19:49:45 +01:00
"nu-utils",
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
"unicode-width",
`start` command in nushell (#1727) * mvp for start command * modified the signature of the start command * parse filenames * working model for macos is done * refactored to read from pipes * start command works well on macos; manual testing reveals need of --args flag support * implemented start error; color printing of warning and errors * ran clippy and fixed warnings * fix a clippy lint that was caught in pipeline * fix dead code clippy lint for windows * add cfg annotation to import
2020-05-08 20:19:48 +02:00
]
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
[[package]]
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
name = "nu-test-support"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
dependencies = [
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
"hamcrest2",
Nu glob (#4818) * Fork glob. Normalise license holder * Fix more licenses * unwraps * bad doc test
2022-03-13 19:30:27 +01:00
"nu-glob",
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
"nu-path",
Add decimals to int when using `into string --decimals` (#6085) * Add decimals to int when using `into string --decimals` * Add tests for `into string` when converting int with `--decimals` * Apply formatting * Merge `into_str` test files * Comment out unused code and add TODOs * Use decimal separator depending on system locale * Add test helper to run closure in different locale * Add tests for int-to-string conversion using different locales * Add utils function to get system locale * Add panic message when locking mutex fails * Catch and resume panic later to prevent Mutex poisoning when test fails * Move test to `nu-test-support` to keep `nu-utils` free of `nu-*` dependencies See https://github.com/nushell/nushell/pull/6085#issuecomment-1193131694 * Rename test support fn `with_fake_locale` to `with_locale_override` * Move `get_system_locale()` to `locale` module * Allow overriding locale with special env variable (when not in release) * Use special env var to override locale during testing * Allow callback to return a value in `with_locale_override()` * Allow multiple options in `nu!` macro * Allow to set locale as `nu!` macro option * Use new `locale` option of `nu!` macro instead of `with_locale_override` Using the `locale` options does not lock the `LOCALE_OVERRIDE_MUTEX` mutex in `nu-test-support::locale_override` but instead calls the `nu` command directly with the `NU_LOCALE_OVERRIDE` environment variable. This allows for parallel test excecution. * Fix: Add option identifier for `cwd` in usage of `nu!` macro * Rely on `Display` trait for formatting `nu!` macro command - Removed the `DisplayPath` trait - Implement `Display` for `AbsolutePath`, `RelativePath` and `AbsoluteFile` * Default to locale `en_US.UTF-8` for tests when using `nu!` macro * Add doc comment to `nu!` macro * Format code using `cargo fmt --all` * Pass function directly instead of wrapping the call in a closure https://rust-lang.github.io/rust-clippy/master/index.html#redundant_closure * Pass function to `or_else()` instead of calling it inside `or()` https://rust-lang.github.io/rust-clippy/master/index.html#or_fun_call * Fix: Add option identifier for `cwd` in usage of `nu!` macro
2022-08-13 04:13:50 +02:00
"nu-utils",
"num-format",
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
"tempfile",
Bump which from 4.4.2 to 5.0.0 (#10811)
2023-10-23 08:14:28 +02:00
"which 4.4.2",
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
]
added `nu-utils` crate, fixed issue where externals turn off vt processing (#4857) * added `nu-utils` crate, fixed issue where externals turn off vt processing * hopefully make work in non-windows environments * clippy
2022-03-16 23:21:06 +01:00
[[package]]
name = "nu-utils"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
added `nu-utils` crate, fixed issue where externals turn off vt processing (#4857) * added `nu-utils` crate, fixed issue where externals turn off vt processing * hopefully make work in non-windows environments * clippy
2022-03-16 23:21:06 +01:00
dependencies = [
"crossterm_winapi",
add some startup performance metrics (#7851) # Description This PR changes the old performance logging with `Instant` timers. I'm not sure if this is the best way to do it but it does help reveal where time is being spent on startup. This is what it looks like when you launch nushell with `cargo run -- --log-level info`. I'm using the `info` log level exclusively for performance monitoring at this point. ![image](https://user-images.githubusercontent.com/343840/214372903-fdfa9c99-b846-47f3-8faf-bd6ed98df3a9.png) ## After Startup Since you're in the repl, you can continue running commands. Here's the output of `ls`, for instance. ![image](https://user-images.githubusercontent.com/343840/214373035-4d2f6e2d-5c1d-43d3-b997-51d79d496ba3.png) Note that the above screenshots are in debug mode, so they're much slower than release. # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-24 21:28:59 +01:00
"log",
enable find to be able to highlight some hits (#6086) * enable find to be able to highlight some hits * oops, deps in the wrong place
2022-07-20 17:09:33 +02:00
"lscolors",
Add decimals to int when using `into string --decimals` (#6085) * Add decimals to int when using `into string --decimals` * Add tests for `into string` when converting int with `--decimals` * Apply formatting * Merge `into_str` test files * Comment out unused code and add TODOs * Use decimal separator depending on system locale * Add test helper to run closure in different locale * Add tests for int-to-string conversion using different locales * Add utils function to get system locale * Add panic message when locking mutex fails * Catch and resume panic later to prevent Mutex poisoning when test fails * Move test to `nu-test-support` to keep `nu-utils` free of `nu-*` dependencies See https://github.com/nushell/nushell/pull/6085#issuecomment-1193131694 * Rename test support fn `with_fake_locale` to `with_locale_override` * Move `get_system_locale()` to `locale` module * Allow overriding locale with special env variable (when not in release) * Use special env var to override locale during testing * Allow callback to return a value in `with_locale_override()` * Allow multiple options in `nu!` macro * Allow to set locale as `nu!` macro option * Use new `locale` option of `nu!` macro instead of `with_locale_override` Using the `locale` options does not lock the `LOCALE_OVERRIDE_MUTEX` mutex in `nu-test-support::locale_override` but instead calls the `nu` command directly with the `NU_LOCALE_OVERRIDE` environment variable. This allows for parallel test excecution. * Fix: Add option identifier for `cwd` in usage of `nu!` macro * Rely on `Display` trait for formatting `nu!` macro command - Removed the `DisplayPath` trait - Implement `Display` for `AbsolutePath`, `RelativePath` and `AbsoluteFile` * Default to locale `en_US.UTF-8` for tests when using `nu!` macro * Add doc comment to `nu!` macro * Format code using `cargo fmt --all` * Pass function directly instead of wrapping the call in a closure https://rust-lang.github.io/rust-clippy/master/index.html#redundant_closure * Pass function to `or_else()` instead of calling it inside `or()` https://rust-lang.github.io/rust-clippy/master/index.html#or_fun_call * Fix: Add option identifier for `cwd` in usage of `nu!` macro
2022-08-13 04:13:50 +02:00
"num-format",
Refactor ansi stripping into `nu-utils` functions (#6966) Allows use of slightly optimized variants that check if they have to use the heavier vte parser. Tries to avoid unnnecessary allocations. Initial performance characteristics proven out in #4378. Also reduces boilerplate with right-ward drift.
2022-11-04 19:49:45 +01:00
"strip-ansi-escapes",
Add decimals to int when using `into string --decimals` (#6085) * Add decimals to int when using `into string --decimals` * Add tests for `into string` when converting int with `--decimals` * Apply formatting * Merge `into_str` test files * Comment out unused code and add TODOs * Use decimal separator depending on system locale * Add test helper to run closure in different locale * Add tests for int-to-string conversion using different locales * Add utils function to get system locale * Add panic message when locking mutex fails * Catch and resume panic later to prevent Mutex poisoning when test fails * Move test to `nu-test-support` to keep `nu-utils` free of `nu-*` dependencies See https://github.com/nushell/nushell/pull/6085#issuecomment-1193131694 * Rename test support fn `with_fake_locale` to `with_locale_override` * Move `get_system_locale()` to `locale` module * Allow overriding locale with special env variable (when not in release) * Use special env var to override locale during testing * Allow callback to return a value in `with_locale_override()` * Allow multiple options in `nu!` macro * Allow to set locale as `nu!` macro option * Use new `locale` option of `nu!` macro instead of `with_locale_override` Using the `locale` options does not lock the `LOCALE_OVERRIDE_MUTEX` mutex in `nu-test-support::locale_override` but instead calls the `nu` command directly with the `NU_LOCALE_OVERRIDE` environment variable. This allows for parallel test excecution. * Fix: Add option identifier for `cwd` in usage of `nu!` macro * Rely on `Display` trait for formatting `nu!` macro command - Removed the `DisplayPath` trait - Implement `Display` for `AbsolutePath`, `RelativePath` and `AbsoluteFile` * Default to locale `en_US.UTF-8` for tests when using `nu!` macro * Add doc comment to `nu!` macro * Format code using `cargo fmt --all` * Pass function directly instead of wrapping the call in a closure https://rust-lang.github.io/rust-clippy/master/index.html#redundant_closure * Pass function to `or_else()` instead of calling it inside `or()` https://rust-lang.github.io/rust-clippy/master/index.html#or_fun_call * Fix: Add option identifier for `cwd` in usage of `nu!` macro
2022-08-13 04:13:50 +02:00
"sys-locale",
Improve case insensitivity consistency (#10884) # Description Add an extension trait `IgnoreCaseExt` to nu_utils which adds some case insensitivity helpers, and use them throughout nu to improve the handling of case insensitivity. Proper case folding is done via unicase, which is already a dependency via mime_guess from nu-command. In actuality a lot of code still does `to_lowercase`, because unicase only provides immediate comparison and doesn't expose a `to_folded_case` yet. And since we do a lot of `contains`/`starts_with`/`ends_with`, it's not sufficient to just have `eq_ignore_case`. But if we get access in the future, this makes us ready to use it with a change in one place. Plus, it's clearer what the purpose is at the call site to call `to_folded_case` instead of `to_lowercase` if it's exclusively for the purpose of case insensitive comparison, even if it just does `to_lowercase` still. # User-Facing Changes - Some commands that were supposed to be case insensitive remained only insensitive to ASCII case (a-z), and now are case insensitive w.r.t. non-ASCII characters as well. # Tests + Formatting - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib` --------- Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com>
2023-11-08 23:58:54 +01:00
"unicase",
added `nu-utils` crate, fixed issue where externals turn off vt processing (#4857) * added `nu-utils` crate, fixed issue where externals turn off vt processing * hopefully make work in non-windows environments * clippy
2022-03-16 23:21:06 +01:00
]
Add CustomValue support to plugins (#6070) * Skeleton implementation Lots and lots of TODOs * Bootstrap simple CustomValue plugin support test * Create nu_plugin_custom_value * Skeleton for nu_plugin_custom_values * Return a custom value from plugin * Encode CustomValues from plugin calls as PluginResponse::PluginData * Add new PluginCall variant CollapseCustomValue * Handle CollapseCustomValue plugin calls * Add CallInput::Data variant to CallInfo inputs * Handle CallInfo with CallInput::Data plugin calls * Send CallInput::Data if Value is PluginCustomValue from plugin calls * Remove unnecessary boxing of plugins CallInfo * Add fields needed to collapse PluginCustomValue to it * Document PluginCustomValue and its purpose * Impl collapsing using plugin calls in PluginCustomValue::to_base_value * Implement proper typetag based deserialization for CoolCustomValue * Test demonstrating that passing back a custom value to plugin works * Added a failing test for describing plugin CustomValues * Support describe for PluginCustomValues - Add name to PluginResponse::PluginData - Also turn it into a struct for clarity - Add name to PluginCustomValue - Return name field from PluginCustomValue * Demonstrate that plugins can create and handle multiple CustomValues * Add bincode to nu-plugin dependencies This is for demonstration purposes, any schemaless binary seralization format will work. I picked bincode since it's the most popular for Rust but there are defintely better options out there for this usecase * serde_json::Value -> Vec<u8> * Update capnp schema for new CallInfo.input field * Move call_input capnp serialization and deserialization into new file * Deserialize Value's span from Value itself instead of passing call.head I am not sure if this was correct and I am breaking it or if it was a bug, I don't fully understand how nu creates and uses Spans. What should reuse spans and what should recreate new ones? But yeah it felt weird that the Value's Span was being ignored since in the json serializer just uses the Value's Span * Add call_info value round trip test * Add capnp CallInput::Data serialization and deserialization support * Add CallInfo::CollapseCustomValue to capnp schema * Add capnp PluginCall::CollapseCustomValue serialization and deserialization support * Add PluginResponse::PluginData to capnp schema * Add capnp PluginResponse::PluginData serialization and deserialization support * Switch plugins::custom_values tests to capnp Both json and capnp would work now! Sadly I can't choose both at the same time :( * Add missing JsonSerializer round trip tests * Handle plugin returning PluginData as a response to CollapseCustomValue * Refactor plugin calling into a reusable function Many less levels of indentation now! * Export PluginData from nu_plugin So plugins can create their very own serve_plugin with whatever CustomValue behavior they may desire * Error if CustomValue cannot be handled by Plugin
2022-07-25 18:32:56 +02:00
[[package]]
name = "nu_plugin_custom_values"
version = "0.1.0"
dependencies = [
"nu-plugin",
"nu-protocol",
"serde",
"typetag",
]
Add wasm support (#2199) * Working towards a PoC for wasm * Move bson and sqlite to plugins * proof of concept now working * tests are green * Add CI test for --no-default-features * Fix some tests * Fix clippy and windows build * More fixes * Fix the windows build * Fix the windows test
2020-07-18 03:59:23 +02:00
[[package]]
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
name = "nu_plugin_example"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Add wasm support (#2199) * Working towards a PoC for wasm * Move bson and sqlite to plugins * proof of concept now working * tests are green * Add CI test for --no-default-features * Fix some tests * Fix clippy and windows build * More fixes * Fix the windows build * Fix the windows test
2020-07-18 03:59:23 +02:00
dependencies = [
"nu-plugin",
"nu-protocol",
]
Move some `from xxx` commands to plugin (#7942) # Description From nushell 0.8 philosophy: https://github.com/nushell/nushell.github.io/blob/main/contributor-book/philosophy_0_80.md#core-categories > The following categories should be moved to plugins: Uncommon format support So this pr is trying to move following commands to plugin: - [X] from eml - [x] from ics - [x] from ini - [x] from vcf And we can have a new plugin handles for these formatting, currently it's implemented here: https://github.com/WindSoilder/nu_plugin_format The command usage should be the same to original command. If it's ok, the plugin can support more formats like [parquet](https://github.com/fdncred/nu_plugin_from_parquet), or [EDN format](https://github.com/nushell/nushell/issues/6415), or something else. Just create a draft pr to show what's the blueprint looks like, and is it a good direction to move forward? # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-02-13 13:42:08 +01:00
[[package]]
name = "nu_plugin_formats"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Move some `from xxx` commands to plugin (#7942) # Description From nushell 0.8 philosophy: https://github.com/nushell/nushell.github.io/blob/main/contributor-book/philosophy_0_80.md#core-categories > The following categories should be moved to plugins: Uncommon format support So this pr is trying to move following commands to plugin: - [X] from eml - [x] from ics - [x] from ini - [x] from vcf And we can have a new plugin handles for these formatting, currently it's implemented here: https://github.com/WindSoilder/nu_plugin_format The command usage should be the same to original command. If it's ok, the plugin can support more formats like [parquet](https://github.com/fdncred/nu_plugin_from_parquet), or [EDN format](https://github.com/nushell/nushell/issues/6415), or something else. Just create a draft pr to show what's the blueprint looks like, and is it a good direction to move forward? # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-02-13 13:42:08 +01:00
dependencies = [
"eml-parser",
"ical",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"indexmap",
Move some `from xxx` commands to plugin (#7942) # Description From nushell 0.8 philosophy: https://github.com/nushell/nushell.github.io/blob/main/contributor-book/philosophy_0_80.md#core-categories > The following categories should be moved to plugins: Uncommon format support So this pr is trying to move following commands to plugin: - [X] from eml - [x] from ics - [x] from ini - [x] from vcf And we can have a new plugin handles for these formatting, currently it's implemented here: https://github.com/WindSoilder/nu_plugin_format The command usage should be the same to original command. If it's ok, the plugin can support more formats like [parquet](https://github.com/fdncred/nu_plugin_from_parquet), or [EDN format](https://github.com/nushell/nushell/issues/6415), or something else. Just create a draft pr to show what's the blueprint looks like, and is it a good direction to move forward? # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-02-13 13:42:08 +01:00
"nu-plugin",
"nu-protocol",
"rust-ini",
]
Add wasm support (#2199) * Working towards a PoC for wasm * Move bson and sqlite to plugins * proof of concept now working * tests are green * Add CI test for --no-default-features * Fix some tests * Fix clippy and windows build * More fixes * Fix the windows build * Fix the windows test
2020-07-18 03:59:23 +02:00
[[package]]
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
name = "nu_plugin_gstat"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Add wasm support (#2199) * Working towards a PoC for wasm * Move bson and sqlite to plugins * proof of concept now working * tests are green * Add CI test for --no-default-features * Fix some tests * Fix clippy and windows build * More fixes * Fix the windows build * Fix the windows test
2020-07-18 03:59:23 +02:00
dependencies = [
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
"git2",
Add wasm support (#2199) * Working towards a PoC for wasm * Move bson and sqlite to plugins * proof of concept now working * tests are green * Add CI test for --no-default-features * Fix some tests * Fix clippy and windows build * More fixes * Fix the windows build * Fix the windows test
2020-07-18 03:59:23 +02:00
"nu-plugin",
"nu-protocol",
]
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
[[package]]
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
name = "nu_plugin_inc"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
dependencies = [
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01:00
"nu-plugin",
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
"nu-protocol",
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
"semver",
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
]
Extract out xpath to a plugin. (#2661)
2020-10-13 01:18:39 +02:00
[[package]]
query command with json, web, xml (#870) * query command with json, web, xml * query xml now working * clippy * comment out web tests * Initial work on query web For now we can query everything except tables * Support for querying tables Now we can query multiple tables just like before, now the only thing missing is the test coverage * finish off * comment out web test Co-authored-by: Luccas Mateus de Medeiros Gomes <luccasmmg@gmail.com>
2022-02-01 19:45:48 +01:00
name = "nu_plugin_query"
Bump version to `0.88.2` (#11333)
2023-12-14 20:55:48 +01:00
version = "0.88.2"
query command with json, web, xml (#870) * query command with json, web, xml * query xml now working * clippy * comment out web tests * Initial work on query web For now we can query everything except tables * Support for querying tables Now we can query multiple tables just like before, now the only thing missing is the test coverage * finish off * comment out web test Co-authored-by: Luccas Mateus de Medeiros Gomes <luccasmmg@gmail.com>
2022-02-01 19:45:48 +01:00
dependencies = [
"gjson",
"nu-engine",
"nu-plugin",
"nu-protocol",
"scraper",
Extract out xpath to a plugin. (#2661)
2020-10-13 01:18:39 +02:00
"sxd-document",
"sxd-xpath",
]
removed rustyline config duplication (#2306) * removed rustyline config duplication set other rustyline defaults if line_editor section doesn't exist updated keyseq_timeout to -1 if emacs mode is chosen * change checking rustyline config to if lets * removed some unneccessary code
2020-08-05 23:34:28 +02:00
[[package]]
name = "num"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b8536030f9fea7127f841b45bb6243b27255787fb4eb83958aa1ef9d2fdc0c36"
dependencies = [
Update bigint/bigdecimal (#2585) * Update bigint/bigdecimal * clippy
2020-09-21 19:28:31 +02:00
"num-bigint 0.2.6",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
"num-complex 0.2.4",
removed rustyline config duplication (#2306) * removed rustyline config duplication set other rustyline defaults if line_editor section doesn't exist updated keyseq_timeout to -1 if emacs mode is chosen * change checking rustyline config to if lets * removed some unneccessary code
2020-08-05 23:34:28 +02:00
"num-integer",
"num-iter",
Update `uom` and `heim` dependencies (#2767) v0.29.0 and earlier versions of `uom` fail to compile on nightly because of now-ambiguous trait bounds. The issue was corrected in v0.30.0 of `uom`. `uom` and `heim` dependencies have been updated to the latest version to include this fix and allow nushell to compile on nightly. Co-authored-by: Boutin, Michael <mjboutin@ecolab.com>
2020-12-15 20:27:21 +01:00
"num-rational 0.2.4",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"num-traits",
removed rustyline config duplication (#2306) * removed rustyline config duplication set other rustyline defaults if line_editor section doesn't exist updated keyseq_timeout to -1 if emacs mode is chosen * change checking rustyline config to if lets * removed some unneccessary code
2020-08-05 23:34:28 +02:00
]
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
[[package]]
name = "num"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.4.1"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "b05180d69e3da0e530ba2a1dae5110317e49e3b7f3d41be227dc5f92e49ee7af"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
dependencies = [
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
"num-bigint 0.4.4",
"num-complex 0.4.4",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
"num-integer",
"num-iter",
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
"num-rational 0.4.1",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"num-traits",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
]
Basic support for decimal numbers This commit is more substantial than it looks: there was basically no real support for decimals before, and that impacted values all the way through. I also made Size contain a decimal instead of an integer (`1.6kb` is a reasonable thing to type), which impacted a bunch of code. The biggest impact of this commit is that it creates many more possible ways for valid nu types to fail to serialize as toml, json, etc. which typically can't support the full range of Decimal (or Bigint, which I also think we should support). This commit makes to-toml fallible, and a similar effort is necessary for the rest of the serializations. We also need to figure out how to clearly communicate to users what has happened, but failing to serialize to toml seems clearly superior to me than weird errors in basic math operations.
2019-08-30 19:29:04 +02:00
[[package]]
name = "num-bigint"
Reset ansi more often when showing errors (#425)
2021-12-04 06:02:57 +01:00
version = "0.2.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "090c7f9998ee0ff65aa5b723e4009f7b217707f1fb5ea551329cc4d6231fb304"
Basic support for decimal numbers This commit is more substantial than it looks: there was basically no real support for decimals before, and that impacted values all the way through. I also made Size contain a decimal instead of an integer (`1.6kb` is a reasonable thing to type), which impacted a bunch of code. The biggest impact of this commit is that it creates many more possible ways for valid nu types to fail to serialize as toml, json, etc. which typically can't support the full range of Decimal (or Bigint, which I also think we should support). This commit makes to-toml fallible, and a similar effort is necessary for the rest of the serializations. We also need to figure out how to clearly communicate to users what has happened, but failing to serialize to toml seems clearly superior to me than weird errors in basic math operations.
2019-08-30 19:29:04 +02:00
dependencies = [
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
"autocfg",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"num-integer",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"num-traits",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
]
[[package]]
name = "num-bigint"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.4.4"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "608e7659b5c3d7cba262d894801b9ec9d00de989e8a82bd4bef91d08da45cdc0"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
dependencies = [
"autocfg",
"num-integer",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"num-traits",
Basic support for decimal numbers This commit is more substantial than it looks: there was basically no real support for decimals before, and that impacted values all the way through. I also made Size contain a decimal instead of an integer (`1.6kb` is a reasonable thing to type), which impacted a bunch of code. The biggest impact of this commit is that it creates many more possible ways for valid nu types to fail to serialize as toml, json, etc. which typically can't support the full range of Decimal (or Bigint, which I also think we should support). This commit makes to-toml fallible, and a similar effort is necessary for the rest of the serializations. We also need to figure out how to clearly communicate to users what has happened, but failing to serialize to toml seems clearly superior to me than weird errors in basic math operations.
2019-08-30 19:29:04 +02:00
]
removed rustyline config duplication (#2306) * removed rustyline config duplication set other rustyline defaults if line_editor section doesn't exist updated keyseq_timeout to -1 if emacs mode is chosen * change checking rustyline config to if lets * removed some unneccessary code
2020-08-05 23:34:28 +02:00
[[package]]
name = "num-complex"
version = "0.2.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b6b19411a9719e753aff12e5187b74d60d3dc449ec3f4dc21e3989c3f554bc95"
dependencies = [
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
"autocfg",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"num-traits",
removed rustyline config duplication (#2306) * removed rustyline config duplication set other rustyline defaults if line_editor section doesn't exist updated keyseq_timeout to -1 if emacs mode is chosen * change checking rustyline config to if lets * removed some unneccessary code
2020-08-05 23:34:28 +02:00
]
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
[[package]]
name = "num-complex"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.4.4"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "1ba157ca0885411de85d6ca030ba7e2a83a28636056c7c699b07c8b6f7383214"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
dependencies = [
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"num-traits",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
]
Add 'str from' subcommand (#2125) * add human, precision commands * add 'str from' subcommand (converted from human/precision commands) move human tests to str from * add default locale, platform-specific SystemLocale use * fix platform specific num-format dependency, remove invalid test * change 'str from' localization to static num_format::Locale::en * minor cleanup, nudge ci * re-attempt ci
2020-07-12 05:57:39 +02:00
[[package]]
name = "num-format"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "0.4.4"
Add 'str from' subcommand (#2125) * add human, precision commands * add 'str from' subcommand (converted from human/precision commands) move human tests to str from * add default locale, platform-specific SystemLocale use * fix platform specific num-format dependency, remove invalid test * change 'str from' localization to static num_format::Locale::en * minor cleanup, nudge ci * re-attempt ci
2020-07-12 05:57:39 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "a652d9771a63711fd3c3deb670acfbe5c30a4072e664d7a3bf5a9e1056ac72c3"
Add 'str from' subcommand (#2125) * add human, precision commands * add 'str from' subcommand (converted from human/precision commands) move human tests to str from * add default locale, platform-specific SystemLocale use * fix platform specific num-format dependency, remove invalid test * change 'str from' localization to static num_format::Locale::en * minor cleanup, nudge ci * re-attempt ci
2020-07-12 05:57:39 +02:00
dependencies = [
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"arrayvec 0.7.4",
Bump scraper from 0.14.0 to 0.15.0 (#8331) Bumps [scraper](https://github.com/causal-agent/scraper) from 0.14.0 to 0.15.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/causal-agent/scraper/releases">scraper's releases</a>.</em></p> <blockquote> <h2>0.15.0</h2> <h2>What's Changed</h2> <ul> <li>Bump cssparser to 0.28 and selectors to 0.23. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li>Create dependabot.yml by <a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li>Re-export Element trait from selectors crate by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/98">causal-agent/scraper#98</a></li> <li>build(deps): fix unchecked lock and update deps by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li>Re-export selectors' CaseSensitivity enum as it is part of our public API. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/108">causal-agent/scraper#108</a></li> <li>perf(element): add one sweep element creation by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/109">causal-agent/scraper#109</a></li> <li>Added feature flag <code>atomic</code> to make use of atomic <code>StrTendril</code> type. by <a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li><a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li><a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li><a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/causal-agent/scraper/commit/3cb7e9a3202fc6f8b80820135ad071916bc2908b"><code>3cb7e9a</code></a> Version 0.15.0</li> <li><a href="https://github.com/causal-agent/scraper/commit/06f395efe0fb4e9c31cdbd81a9f9e41802572b33"><code>06f395e</code></a> Apply clippy suggestion</li> <li><a href="https://github.com/causal-agent/scraper/commit/ec91bf1ebc9921ca2adeddf93555081912c33334"><code>ec91bf1</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/102">#102</a> from jaboatman/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/4b7fb13446f5ab4400b1fdfb3092b71b3157af9a"><code>4b7fb13</code></a> Merge remote-tracking branch 'upstream/master'</li> <li><a href="https://github.com/causal-agent/scraper/commit/aa479ea170b7f2b463ccba85de0c802318d19abe"><code>aa479ea</code></a> perf(element): add one sweep element creation (<a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/109">#109</a>)</li> <li><a href="https://github.com/causal-agent/scraper/commit/9a6a638db208682593d83bef53c29052336c0487"><code>9a6a638</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/108">#108</a> from adamreichold/also-re-export-case-sensitivity</li> <li><a href="https://github.com/causal-agent/scraper/commit/794b5eef87aa1009a31d4d29093269a04e7d80fa"><code>794b5ee</code></a> Re-export selectors' CaseSensitivity enum as it is part of our public API.</li> <li><a href="https://github.com/causal-agent/scraper/commit/6abb8cd625af5ea4f5a59530f03436aa448f7c56"><code>6abb8cd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/107">#107</a> from j-mendez/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/c3dd2600dcd4c17424a307c2f82cfcab41943014"><code>c3dd260</code></a> chore(minor): fix element classes map format</li> <li><a href="https://github.com/causal-agent/scraper/commit/b7955b9049ccf5b685f53854d88cca322aa80bac"><code>b7955b9</code></a> perf(selectors): add lazy classes map</li> <li>Additional commits viewable in <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=scraper&package-manager=cargo&previous-version=0.14.0&new-version=0.15.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-06 04:37:22 +01:00
"itoa",
Add 'str from' subcommand (#2125) * add human, precision commands * add 'str from' subcommand (converted from human/precision commands) move human tests to str from * add default locale, platform-specific SystemLocale use * fix platform specific num-format dependency, remove invalid test * change 'str from' localization to static num_format::Locale::en * minor cleanup, nudge ci * re-attempt ci
2020-07-12 05:57:39 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "num-integer"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
version = "0.1.45"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
checksum = "225d3389fb3509a24c93f5c29eb6bde2586b98d9f016636dff58d7c6f7569cd9"
objectshell initial commit
2019-05-10 18:59:12 +02:00
dependencies = [
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
"autocfg",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"num-traits",
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
]
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
[[package]]
name = "num-iter"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
version = "0.1.43"
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
checksum = "7d03e6c028c5dc5cac6e2dec0efda81fc887605bb3d884578bb6d6bf7514e252"
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
dependencies = [
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
"autocfg",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"num-integer",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"num-traits",
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
]
[[package]]
name = "num-rational"
Fix the versions up a bit to prevent breakage (#1602) * Fix the versions up a bit to prevent breakage * fix up the quickcheck test to not fail on parse error
2020-04-18 05:31:57 +02:00
version = "0.2.4"
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Fix the versions up a bit to prevent breakage (#1602) * Fix the versions up a bit to prevent breakage * fix up the quickcheck test to not fail on parse error
2020-04-18 05:31:57 +02:00
checksum = "5c000134b5dbf44adc5cb772486d335293351644b801551abe8f75c84cfa4aef"
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
dependencies = [
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
"autocfg",
Update bigint/bigdecimal (#2585) * Update bigint/bigdecimal * clippy
2020-09-21 19:28:31 +02:00
"num-bigint 0.2.6",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"num-integer",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"num-traits",
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
]
Update `uom` and `heim` dependencies (#2767) v0.29.0 and earlier versions of `uom` fail to compile on nightly because of now-ambiguous trait bounds. The issue was corrected in v0.30.0 of `uom`. `uom` and `heim` dependencies have been updated to the latest version to include this fix and allow nushell to compile on nightly. Co-authored-by: Boutin, Michael <mjboutin@ecolab.com>
2020-12-15 20:27:21 +01:00
[[package]]
name = "num-rational"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
version = "0.4.1"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
checksum = "0638a1c9d0a3c0914158145bc76cff373a75a627e6ecbfb71cbe6f453a5a19b0"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
dependencies = [
"autocfg",
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
"num-bigint 0.4.4",
Update `uom` and `heim` dependencies (#2767) v0.29.0 and earlier versions of `uom` fail to compile on nightly because of now-ambiguous trait bounds. The issue was corrected in v0.30.0 of `uom`. `uom` and `heim` dependencies have been updated to the latest version to include this fix and allow nushell to compile on nightly. Co-authored-by: Boutin, Michael <mjboutin@ecolab.com>
2020-12-15 20:27:21 +01:00
"num-integer",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"num-traits",
Lots of misc improvements
2019-06-03 09:41:28 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "num-traits"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.2.17"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "39e3200413f237f41ab11ad6d161bc7239c84dcb631773ccd7de3dfe4b5c267c"
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
dependencies = [
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
"autocfg",
Dataframe commands (#3498) * Sample command * Join command with checks * More dataframes commands * Groupby and aggregate commands * Missing feature dataframe flag * Renamed file
2021-05-27 07:09:48 +02:00
"libm",
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "num_cpus"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "1.16.0"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "4161fcb6d602d4d2081af7c3a45852d875a03dd337a6bfdd6e06407b61342a43"
objectshell initial commit
2019-05-10 18:59:12 +02:00
dependencies = [
Use `is-terminal` crate for now (#9670) # Description Until we bump our minimal Rust version to `1.70.0` we can't use `std::io::IsTerminal`. The crate `is-terminal` (depending on `rustix` or `windows-sys`) can provide the same. Get's rid of the dependency on the outdated `atty` crate. We already transitively depend on it (e.g. through `miette`) As soon as we reach the new Rust version we can supersede this with @nibon7's #9550 Co-authored-by: nibon7 <nibon7@163.com>
2023-07-12 18:15:54 +02:00
"hermit-abi",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"libc",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
[[package]]
name = "num_threads"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2819ce041d2ee131036f4fc9d6ae7ae125a3a40e97ba64d04fe799ad9dabbb44"
dependencies = [
"libc",
]
Progress bar Implementation (#7661) # Description _(Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience.)_ I implemented the status bar we talk about yesterday. The idea was inspired by the progress bar of `wget`. I decided to go for the second suggestion by `@Reilly` > 2. add an Option<usize> or whatever to RawStream (and ListStream?) for situations where you do know the length ahead of time For now only works with the command `save` but after the approve of this PR we can see how we can implement it on commands like `cp` and `mv` When using `fetch` nushell will check if there is any `content-length` attribute in the request header. If so, then `fetch` will send it through the new `Option` variable in the `RawStream` to the `save`. If we know the total size we show the progress bar ![nu_pb01](https://user-images.githubusercontent.com/38369407/210298647-07ee55ea-e751-41b1-a84d-f72ec1f6e9e5.jpg) but if we don't then we just show the stats like: data already saved, bytes per second, and time lapse. ![nu_pb02](https://user-images.githubusercontent.com/38369407/210298698-1ef65f51-40cc-4481-83de-309cbd1049cb.jpg) ![nu_pb03](https://user-images.githubusercontent.com/38369407/210298701-eef2ef13-9206-4a98-8202-e4fe5531d79d.jpg) Please let me know If I need to make any changes and I will be happy to do it. # User-Facing Changes A new flag (`--progress` `-p`) was added to the `save` command Examples: ```nu fetch https://github.com/torvalds/linux/archive/refs/heads/master.zip | save --progress -f main.zip fetch https://releases.ubuntu.com/22.04.1/ubuntu-22.04.1-desktop-amd64.iso | save --progress -f main.zip open main.zip --raw | save --progress main.copy ``` # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - I am getting some errors and its weird because the errors are showing up in files i haven't touch. Is this normal? # 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. Co-authored-by: Reilly Wood <reilly.wood@icloud.com>
2023-01-11 02:57:48 +01:00
[[package]]
name = "number_prefix"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "830b246a0e5f20af87141b25c173cd1b609bd7779a4617d6ec582abaf90870f3"
Add clipboard support
2019-06-07 18:30:50 +02:00
[[package]]
name = "objc"
Merge master
2019-11-16 18:17:05 +01:00
version = "0.2.7"
Add clipboard support
2019-06-07 18:30:50 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
checksum = "915b1b472bc21c53464d6c8461c9d3af805ba1ef837e1cac254428f4a77177b1"
Add clipboard support
2019-06-07 18:30:50 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"malloc_buf",
Add clipboard support
2019-06-07 18:30:50 +02:00
]
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
[[package]]
name = "object"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.32.1"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "9cf5f9dd3933bd50a9e1f149ec995f39ae2c496d31fd772c1fd45ebc27e902b0"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
dependencies = [
"memchr",
]
Try not to use verbatim paths for UNC shares (#6824)
2022-10-22 18:51:52 +02:00
[[package]]
name = "omnipath"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
version = "0.1.6"
Try not to use verbatim paths for UNC shares (#6824)
2022-10-22 18:51:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
checksum = "80adb31078122c880307e9cdfd4e3361e6545c319f9b9dcafcb03acd3b51a575"
Try not to use verbatim paths for UNC shares (#6824)
2022-10-22 18:51:52 +02:00
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 15:47:30 +02:00
[[package]]
name = "once_cell"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "1.19.0"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 15:47:30 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "3fdb12b2476b595f9358c5161aa467c2438859caa136dec86c26fdd2efe17b92"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 15:47:30 +02:00
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
[[package]]
name = "oorandom"
version = "11.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0ab1bc2a289d34bd04a330323ac98a1b4bc82c9d9fcb1e66b63caa84da26b575"
let `start` open anything and everything (#7580) # Description Fixes #7546 's request. I'm unsure, so hopefully someone in charge of design can chip in. # User-Facing Changes `open` now opens directories in the default file manager. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-03 19:47:37 +01:00
[[package]]
name = "open"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "5.0.1"
let `start` open anything and everything (#7580) # Description Fixes #7546 's request. I'm unsure, so hopefully someone in charge of design can chip in. # User-Facing Changes `open` now opens directories in the default file manager. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-03 19:47:37 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "90878fb664448b54c4e592455ad02831e23a3f7e157374a8b95654731aac7349"
let `start` open anything and everything (#7580) # Description Fixes #7546 's request. I'm unsure, so hopefully someone in charge of design can chip in. # User-Facing Changes `open` now opens directories in the default file manager. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-03 19:47:37 +01:00
dependencies = [
Upgrade `open` crate to fix WSL bug (#8905) This PR upgrades the [`open`](https://github.com/Byron/open-rs) crate (used in the `start` command) from 4.0.1 to 4.0.2. This fixes a bug where `open` doesn't always work properly on WSL: https://github.com/Byron/open-rs/pull/71
2023-04-17 07:05:40 +02:00
"is-wsl",
Bump open from 4.1.0 to 5.0.0 (#9526)
2023-06-29 15:30:07 +02:00
"libc",
let `start` open anything and everything (#7580) # Description Fixes #7546 's request. I'm unsure, so hopefully someone in charge of design can chip in. # User-Facing Changes `open` now opens directories in the default file manager. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-03 19:47:37 +01:00
"pathdiff",
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
[[package]]
Add a --full mode to ps (#1507) * Add a --full mode to ps * Use a slightly older heim
2020-03-20 08:53:49 +01:00
name = "openssl"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.10.61"
Add a --full mode to ps (#1507) * Add a --full mode to ps * Use a slightly older heim
2020-03-20 08:53:49 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "6b8419dc8cc6d866deb801274bba2e6f8f6108c1bb7fcc10ee5ab864931dbb45"
Add a --full mode to ps (#1507) * Add a --full mode to ps * Use a slightly older heim
2020-03-20 08:53:49 +01:00
dependencies = [
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"bitflags 2.4.1",
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Add a --full mode to ps (#1507) * Add a --full mode to ps * Use a slightly older heim
2020-03-20 08:53:49 +01:00
"foreign-types",
"libc",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
"once_cell",
cargo update (#5639)
2022-05-25 19:13:14 +02:00
"openssl-macros",
Add a --full mode to ps (#1507) * Add a --full mode to ps * Use a slightly older heim
2020-03-20 08:53:49 +01:00
"openssl-sys",
]
cargo update (#5639)
2022-05-25 19:13:14 +02:00
[[package]]
name = "openssl-macros"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
version = "0.1.1"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
checksum = "a948666b637a0f465e8564c73e89d4dde00d72d4d473cc972f390fc3dcee7d9c"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
dependencies = [
"proc-macro2",
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
cargo update (#5639)
2022-05-25 19:13:14 +02:00
]
Add git branch to prompt
2019-06-01 23:11:28 +02:00
[[package]]
name = "openssl-probe"
merge main
2022-02-08 14:28:21 +01:00
version = "0.1.5"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
merge main
2022-02-08 14:28:21 +01:00
checksum = "ff011a302c396a5197692431fc1948019154afc178baf7d8e37367442a4601cf"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
Statically link OpenSSL (#5349)
2022-04-28 02:25:09 +02:00
[[package]]
name = "openssl-src"
Downgrade openssl-src to fix riscv64 build target, close #11345 (#11353)
2023-12-17 22:57:20 +01:00
version = "300.1.6+3.1.4"
Statically link OpenSSL (#5349)
2022-04-28 02:25:09 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Downgrade openssl-src to fix riscv64 build target, close #11345 (#11353)
2023-12-17 22:57:20 +01:00
checksum = "439fac53e092cd7442a3660c85dde4643ab3b5bd39040912388dcdabf6b88085"
Statically link OpenSSL (#5349)
2022-04-28 02:25:09 +02:00
dependencies = [
"cc",
]
Add git branch to prompt
2019-06-01 23:11:28 +02:00
[[package]]
name = "openssl-sys"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.9.97"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "c3eaad34cdd97d81de97964fc7f29e2d104f483840d906ef56daa1912338460b"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"cc",
"libc",
Statically link OpenSSL (#5349)
2022-04-28 02:25:09 +02:00
"openssl-src",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"pkg-config",
"vcpkg",
Add git branch to prompt
2019-06-01 23:11:28 +02:00
]
Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from (#8009) # Description Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from # Tests + Formatting Added a test to support addition of the rust-ini crate. `cargo test --package nu-command --lib -- formats::from::ini::tests --nocapture` Executed all tests. `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-09 12:47:45 +01:00
[[package]]
name = "ordered-multimap"
Bump rust-ini from 0.19.0 to 0.20.0 (#10882)
2023-10-30 12:56:13 +01:00
version = "0.7.1"
Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from (#8009) # Description Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from # Tests + Formatting Added a test to support addition of the rust-ini crate. `cargo test --package nu-command --lib -- formats::from::ini::tests --nocapture` Executed all tests. `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-09 12:47:45 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump rust-ini from 0.19.0 to 0.20.0 (#10882)
2023-10-30 12:56:13 +01:00
checksum = "a4d6a8c22fc714f0c2373e6091bf6f5e9b37b1bc0b1184874b7e0a4e303d318f"
Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from (#8009) # Description Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from # Tests + Formatting Added a test to support addition of the rust-ini crate. `cargo test --package nu-command --lib -- formats::from::ini::tests --nocapture` Executed all tests. `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-09 12:47:45 +01:00
dependencies = [
"dlv-list",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"hashbrown 0.14.3",
Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from (#8009) # Description Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from # Tests + Formatting Added a test to support addition of the rust-ini crate. `cargo test --package nu-command --lib -- formats::from::ini::tests --nocapture` Executed all tests. `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-09 12:47:45 +01:00
]
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
[[package]]
name = "os_display"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7a6229bad892b46b0dcfaaeb18ad0d2e56400f5aaea05b768bde96e73676cf75"
dependencies = [
"unicode-width",
]
Add --redirect-combine option to run-external (#8918) # Description Add option that combines both output streams to the `run-external` command. This allows you to do something like this: ```nushell let res = do -i { run-external --redirect-combine <command that prints to stdout and stderr> } | complete if $res.exit_code != 0 { # Only print output when command has failed. print "The command has failed, these are the logs:" print $res.stdout } ``` # User-Facing Changes No breaking changes, just an extra option. # Tests + Formatting Added a test that checks the new option # 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. --> Co-authored-by: Jelle Besseling <jelle@bigbridge.nl>
2023-04-28 14:55:48 +02:00
[[package]]
name = "os_pipe"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
version = "1.1.4"
Add --redirect-combine option to run-external (#8918) # Description Add option that combines both output streams to the `run-external` command. This allows you to do something like this: ```nushell let res = do -i { run-external --redirect-combine <command that prints to stdout and stderr> } | complete if $res.exit_code != 0 { # Only print output when command has failed. print "The command has failed, these are the logs:" print $res.stdout } ``` # User-Facing Changes No breaking changes, just an extra option. # Tests + Formatting Added a test that checks the new option # 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. --> Co-authored-by: Jelle Besseling <jelle@bigbridge.nl>
2023-04-28 14:55:48 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
checksum = "0ae859aa07428ca9a929b936690f8b12dc5f11dd8c6992a18ca93919f28bc177"
Add --redirect-combine option to run-external (#8918) # Description Add option that combines both output streams to the `run-external` command. This allows you to do something like this: ```nushell let res = do -i { run-external --redirect-combine <command that prints to stdout and stderr> } | complete if $res.exit_code != 0 { # Only print output when command has failed. print "The command has failed, these are the logs:" print $res.stdout } ``` # User-Facing Changes No breaking changes, just an extra option. # Tests + Formatting Added a test that checks the new option # 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. --> Co-authored-by: Jelle Besseling <jelle@bigbridge.nl>
2023-04-28 14:55:48 +02:00
dependencies = [
"libc",
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
"windows-sys 0.48.0",
Add --redirect-combine option to run-external (#8918) # Description Add option that combines both output streams to the `run-external` command. This allows you to do something like this: ```nushell let res = do -i { run-external --redirect-combine <command that prints to stdout and stderr> } | complete if $res.exit_code != 0 { # Only print output when command has failed. print "The command has failed, these are the logs:" print $res.stdout } ``` # User-Facing Changes No breaking changes, just an extra option. # Tests + Formatting Added a test that checks the new option # 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. --> Co-authored-by: Jelle Besseling <jelle@bigbridge.nl>
2023-04-28 14:55:48 +02:00
]
Bump deps and touchup (#2066)
2020-06-27 09:54:31 +02:00
[[package]]
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
name = "owo-colors"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
version = "3.5.0"
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
checksum = "c1b04fb49957986fdce4d6ee7a65027d55d4b6d2265e5848bbb507b58ccfdb6f"
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
Give tabled a try (#5969) * Drop in replacement from nu-table to tabled. Must act the same way as original nu-table. Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Fix some issues Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump ansi-str version Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update to latest Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix footer issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header style Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Use latest tabled/ansi-str * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy warnings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-06 21:57:40 +02:00
[[package]]
name = "papergrid"
Add an option to set header on border (style) (#9920) fix #9796 Sorry that you've had the issues. I've actually encountered them yesterday too (seems like they have appeared after some refactoring in the middle) but was not able to fix that rapid. Created a bunch of tests. cc: @fdncred Note: This option will be certainly slower then a default ones. (could be fixed but ... maybe later). Maybe it shall be cited somewhere. PS: Haven't tested on a wrapped/expanded tables. --------- Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-08-04 20:50:47 +02:00
version = "0.10.0"
nu-table/ Bump tabled version (#6097) Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-22 17:33:29 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add an option to set header on border (style) (#9920) fix #9796 Sorry that you've had the issues. I've actually encountered them yesterday too (seems like they have appeared after some refactoring in the middle) but was not able to fix that rapid. Created a bunch of tests. cc: @fdncred Note: This option will be certainly slower then a default ones. (could be fixed but ... maybe later). Maybe it shall be cited somewhere. PS: Haven't tested on a wrapped/expanded tables. --------- Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-08-04 20:50:47 +02:00
checksum = "a2ccbe15f2b6db62f9a9871642746427e297b0ceb85f9a7f1ee5ff47d184d0c8"
Give tabled a try (#5969) * Drop in replacement from nu-table to tabled. Must act the same way as original nu-table. Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Fix some issues Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump ansi-str version Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update to latest Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix footer issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header style Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Use latest tabled/ansi-str * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy warnings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-06 21:57:40 +02:00
dependencies = [
Remove duplicated dependency on `ansi-str 0.7` (#9641) # Description `tabled`/`papergrid` already use `ansi-str 0.8` while `nu-explore` itself was still depending on `0.7`. Single fix necessary to adapt to the new API. cc @zhiburt # User-Facing Changes None
2023-07-10 09:24:08 +02:00
"ansi-str",
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
"ansitok",
Give tabled a try (#5969) * Drop in replacement from nu-table to tabled. Must act the same way as original nu-table. Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Fix some issues Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump ansi-str version Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update to latest Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix footer issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header style Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Use latest tabled/ansi-str * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy warnings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-06 21:57:40 +02:00
"bytecount",
nu-table/ Bump tabled version (#6097) Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-22 17:33:29 +02:00
"fnv",
Give tabled a try (#5969) * Drop in replacement from nu-table to tabled. Must act the same way as original nu-table. Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Fix some issues Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump ansi-str version Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update to latest Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix footer issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header style Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Use latest tabled/ansi-str * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy warnings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-06 21:57:40 +02:00
"unicode-width",
]
Move to latest stable crossterm, with fix (#4684)
2022-03-01 13:05:46 +01:00
[[package]]
name = "parking_lot"
SQLite History MVP with timestamp, duration, working directory, exit status metadata (#5721) This PR adds support for an SQLite history via nushell/reedline#401 The SQLite history is enabled by setting history_file_format: "sqlite" in config.nu. * somewhat working sqlite history * Hook up history command * Fix error in SQlitebacked with empty lines When entering an empty line there previously was the "No command run" error with `SqliteBackedHistory` during addition of the metadata May be considered a temporary fix Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2022-06-14 22:53:33 +02:00
version = "0.12.1"
Move to latest stable crossterm, with fix (#4684)
2022-03-01 13:05:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
SQLite History MVP with timestamp, duration, working directory, exit status metadata (#5721) This PR adds support for an SQLite history via nushell/reedline#401 The SQLite history is enabled by setting history_file_format: "sqlite" in config.nu. * somewhat working sqlite history * Hook up history command * Fix error in SQlitebacked with empty lines When entering an empty line there previously was the "No command run" error with `SqliteBackedHistory` during addition of the metadata May be considered a temporary fix Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2022-06-14 22:53:33 +02:00
checksum = "3742b2c103b9f06bc9fff0a37ff4912935851bee6d36f3c02bcc755bcfec228f"
Move to latest stable crossterm, with fix (#4684)
2022-03-01 13:05:46 +01:00
dependencies = [
"lock_api",
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
"parking_lot_core",
Custom lexer
2019-05-29 17:26:45 +02:00
]
Move to latest stable crossterm, with fix (#4684)
2022-03-01 13:05:46 +01:00
[[package]]
name = "parking_lot_core"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.9.9"
Move to latest stable crossterm, with fix (#4684)
2022-03-01 13:05:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "4c42a9226546d68acdd9c0a280d17ce19bfe27a46bf68784e4066115788d008e"
Move to latest stable crossterm, with fix (#4684)
2022-03-01 13:05:46 +01:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Move to latest stable crossterm, with fix (#4684)
2022-03-01 13:05:46 +01:00
"libc",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"redox_syscall",
Move to latest stable crossterm, with fix (#4684)
2022-03-01 13:05:46 +01:00
"smallvec",
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
"windows-targets 0.48.5",
Move to latest stable crossterm, with fix (#4684)
2022-03-01 13:05:46 +01:00
]
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
[[package]]
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
name = "parquet-format-safe"
version = "0.2.4"
New take command (#3722) * Type in command description * filter name change * Clean column name * Clippy error and updated polars version * Lint correction in file * CSV Infer schema optional * Correct float operations * changes in series castings to allow other types * Clippy error correction * Removed lists from command signatures * Added not command for series * take command with args * set with idx command
2021-07-05 01:46:53 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
checksum = "1131c54b167dd4e4799ce762e1ab01549ebb94d5bdd13e6ec1b467491c378e1f"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
dependencies = [
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
"async-trait",
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
"futures",
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
]
removed rustyline config duplication (#2306) * removed rustyline config duplication set other rustyline defaults if line_editor section doesn't exist updated keyseq_timeout to -1 if emacs mode is chosen * change checking rustyline config to if lets * removed some unneccessary code
2020-08-05 23:34:28 +02:00
[[package]]
name = "parse-zoneinfo"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c705f256449c60da65e11ff6626e0c16a0a0b96aaa348de61376b249bc340f41"
dependencies = [
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"regex",
removed rustyline config duplication (#2306) * removed rustyline config duplication set other rustyline defaults if line_editor section doesn't exist updated keyseq_timeout to -1 if emacs mode is chosen * change checking rustyline config to if lets * removed some unneccessary code
2020-08-05 23:34:28 +02:00
]
add MessagePack as a plugin protocol (#6370)
2022-08-21 13:13:38 +02:00
[[package]]
name = "paste"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.0.14"
add MessagePack as a plugin protocol (#6370)
2022-08-21 13:13:38 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "de3145af08024dea9fa9914f381a17b8fc6034dfb00f3a84013f7ff43f29ed4c"
add MessagePack as a plugin protocol (#6370)
2022-08-21 13:13:38 +02:00
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
[[package]]
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
name = "pathdiff"
Fix clippy warnings (#4176)
2021-12-02 19:05:38 +01:00
version = "0.2.1"
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Fix clippy warnings (#4176)
2021-12-02 19:05:38 +01:00
checksum = "8835116a5c179084a830efb3adc117ab007512b535bc1a21c991d3b32a6b44dd"
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
[[package]]
name = "peeking_take_while"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "19b17cddbe7ec3f8bc800887bab5e717348c95ea2ca0b1bf0837fb964dc67099"
bump deps
2019-07-29 09:46:24 +02:00
[[package]]
name = "percent-encoding"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "2.3.1"
bump deps
2019-07-29 09:46:24 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "e3148f5046208a5d56bcfc03053e3ca6334e51da8dfb19b6cdc8b306fae3283e"
bump deps
2019-07-29 09:46:24 +02:00
xpath command for nushell (#2656) * xpath prototype * new xpath engine is finally working * nearly there * closer * working with list, started to add test, code cleanup * broken again * working again - time for some cleanup * cleaned up code, added error handling and test * update example, fix clippy * removed commented char
2020-10-12 15:03:00 +02:00
[[package]]
name = "peresil"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f658886ed52e196e850cfbbfddab9eaa7f6d90dd0929e264c31e5cec07e09e57"
allow parsing of human readable datetimes (#11051) # Description This PR adds the ability to parse human readable datetime strings as part of the `into datetime` command. I added a new `-n`/`--list-human` parameter that produces this list to give the user an idea of what is supported. ```nushell ❯ into datetime --list-human ╭#─┬parseable human datetime examples┬───result───╮ │0 │Today 18:30 │in 8 hours │ │1 │2022-11-07 13:25:30 │a year ago │ │2 │15:20 Friday │in 3 days │ │3 │This Friday 17:00 │in 3 days │ │4 │13:25, Next Tuesday │in a week │ │5 │Last Friday at 19:45 │3 days ago │ │6 │In 3 days │in 2 days │ │7 │In 2 hours │in 2 hours │ │8 │10 hours and 5 minutes ago │10 hours ago│ │9 │1 years ago │a year ago │ │10│A year ago │a year ago │ │11│A month ago │a month ago │ │12│A week ago │a week ago │ │13│A day ago │a day ago │ │14│An hour ago │an hour ago │ │15│A minute ago │a minute ago│ │16│A second ago │now │ │17│Now │now │ ╰#─┴parseable human datetime examples┴───result───╯ ``` Or with `$env.config.datetime_format.table` set. ```nushell ❯ into datetime --list-human ╭#─┬parseable human datetime examples┬──────result───────╮ │0 │Today 18:30 │11/14/23 06:30:00PM│ │1 │2022-11-07 13:25:30 │11/07/22 01:25:30PM│ │2 │15:20 Friday │11/17/23 03:20:00PM│ │3 │This Friday 17:00 │11/17/23 05:00:00PM│ │4 │13:25, Next Tuesday │11/21/23 01:25:00PM│ │5 │Last Friday at 19:45 │11/10/23 07:45:00PM│ │6 │In 3 days │11/17/23 10:12:54AM│ │7 │In 2 hours │11/14/23 12:12:54PM│ │8 │10 hours and 5 minutes ago │11/14/23 12:07:54AM│ │9 │1 years ago │11/13/22 10:12:54AM│ │10│A year ago │11/13/22 10:12:54AM│ │11│A month ago │10/15/23 11:12:54AM│ │12│A week ago │11/07/23 10:12:54AM│ │13│A day ago │11/13/23 10:12:54AM│ │14│An hour ago │11/14/23 09:12:54AM│ │15│A minute ago │11/14/23 10:11:54AM│ │16│A second ago │11/14/23 10:12:53AM│ │17│Now │11/14/23 10:12:54AM│ ╰#─┴parseable human datetime examples┴──────result───────╯ ``` # 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-11-16 00:43:37 +01:00
[[package]]
name = "pest"
version = "2.7.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ae9cee2a55a544be8b89dc6848072af97a20f2422603c10865be2a42b580fff5"
dependencies = [
"memchr",
"thiserror",
"ucd-trie",
]
[[package]]
name = "pest_derive"
version = "2.7.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "81d78524685f5ef2a3b3bd1cafbc9fcabb036253d9b1463e726a91cd16e2dfc2"
dependencies = [
"pest",
"pest_generator",
]
[[package]]
name = "pest_generator"
version = "2.7.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "68bd1206e71118b5356dae5ddc61c8b11e28b09ef6a31acbd15ea48a28e0c227"
dependencies = [
"pest",
"pest_meta",
"proc-macro2",
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
allow parsing of human readable datetimes (#11051) # Description This PR adds the ability to parse human readable datetime strings as part of the `into datetime` command. I added a new `-n`/`--list-human` parameter that produces this list to give the user an idea of what is supported. ```nushell ❯ into datetime --list-human ╭#─┬parseable human datetime examples┬───result───╮ │0 │Today 18:30 │in 8 hours │ │1 │2022-11-07 13:25:30 │a year ago │ │2 │15:20 Friday │in 3 days │ │3 │This Friday 17:00 │in 3 days │ │4 │13:25, Next Tuesday │in a week │ │5 │Last Friday at 19:45 │3 days ago │ │6 │In 3 days │in 2 days │ │7 │In 2 hours │in 2 hours │ │8 │10 hours and 5 minutes ago │10 hours ago│ │9 │1 years ago │a year ago │ │10│A year ago │a year ago │ │11│A month ago │a month ago │ │12│A week ago │a week ago │ │13│A day ago │a day ago │ │14│An hour ago │an hour ago │ │15│A minute ago │a minute ago│ │16│A second ago │now │ │17│Now │now │ ╰#─┴parseable human datetime examples┴───result───╯ ``` Or with `$env.config.datetime_format.table` set. ```nushell ❯ into datetime --list-human ╭#─┬parseable human datetime examples┬──────result───────╮ │0 │Today 18:30 │11/14/23 06:30:00PM│ │1 │2022-11-07 13:25:30 │11/07/22 01:25:30PM│ │2 │15:20 Friday │11/17/23 03:20:00PM│ │3 │This Friday 17:00 │11/17/23 05:00:00PM│ │4 │13:25, Next Tuesday │11/21/23 01:25:00PM│ │5 │Last Friday at 19:45 │11/10/23 07:45:00PM│ │6 │In 3 days │11/17/23 10:12:54AM│ │7 │In 2 hours │11/14/23 12:12:54PM│ │8 │10 hours and 5 minutes ago │11/14/23 12:07:54AM│ │9 │1 years ago │11/13/22 10:12:54AM│ │10│A year ago │11/13/22 10:12:54AM│ │11│A month ago │10/15/23 11:12:54AM│ │12│A week ago │11/07/23 10:12:54AM│ │13│A day ago │11/13/23 10:12:54AM│ │14│An hour ago │11/14/23 09:12:54AM│ │15│A minute ago │11/14/23 10:11:54AM│ │16│A second ago │11/14/23 10:12:53AM│ │17│Now │11/14/23 10:12:54AM│ ╰#─┴parseable human datetime examples┴──────result───────╯ ``` # 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-11-16 00:43:37 +01:00
]
[[package]]
name = "pest_meta"
version = "2.7.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7c747191d4ad9e4a4ab9c8798f1e82a39affe7ef9648390b7e5548d18e099de6"
dependencies = [
"once_cell",
"pest",
"sha2",
]
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
[[package]]
Add a simple scope variable
2021-11-02 04:08:05 +01:00
name = "phf"
list keybinding options (#906) * list keybinding optins * list keybinding options * clippy error
2022-02-04 07:47:18 +01:00
version = "0.10.1"
Add a simple scope variable
2021-11-02 04:08:05 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
list keybinding options (#906) * list keybinding optins * list keybinding options * clippy error
2022-02-04 07:47:18 +01:00
checksum = "fabbf1ead8a5bcbc20f5f8b939ee3f5b0f6f281b6ad3468b84656b658b455259"
Add a simple scope variable
2021-11-02 04:08:05 +01:00
dependencies = [
query command with json, web, xml (#870) * query command with json, web, xml * query xml now working * clippy * comment out web tests * Initial work on query web For now we can query everything except tables * Support for querying tables Now we can query multiple tables just like before, now the only thing missing is the test coverage * finish off * comment out web test Co-authored-by: Luccas Mateus de Medeiros Gomes <luccasmmg@gmail.com>
2022-02-01 19:45:48 +01:00
"phf_shared 0.10.0",
]
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
[[package]]
name = "phf"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.11.2"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "ade2d8b8f33c7333b51bcf0428d37e217e9f32192ae4772156f65063b8ce03dc"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
dependencies = [
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"phf_macros",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"phf_shared 0.11.2",
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
]
Add a simple scope variable
2021-11-02 04:08:05 +01:00
[[package]]
name = "phf_codegen"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4fb1c3a8bc4dd4e5cfce29b44ffc14bedd2ee294559a294e2a4d4c9e9a6a13cd"
dependencies = [
query command with json, web, xml (#870) * query command with json, web, xml * query xml now working * clippy * comment out web tests * Initial work on query web For now we can query everything except tables * Support for querying tables Now we can query multiple tables just like before, now the only thing missing is the test coverage * finish off * comment out web test Co-authored-by: Luccas Mateus de Medeiros Gomes <luccasmmg@gmail.com>
2022-02-01 19:45:48 +01:00
"phf_generator 0.10.0",
"phf_shared 0.10.0",
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
]
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
[[package]]
name = "phf_codegen"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.11.2"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "e8d39688d359e6b34654d328e262234662d16cc0f60ec8dcbe5e718709342a5a"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
dependencies = [
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"phf_generator 0.11.2",
"phf_shared 0.11.2",
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
]
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
[[package]]
Add a simple scope variable
2021-11-02 04:08:05 +01:00
name = "phf_generator"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5d5285893bb5eb82e6aaf5d59ee909a06a16737a8970984dd7746ba9283498d6"
dependencies = [
query command with json, web, xml (#870) * query command with json, web, xml * query xml now working * clippy * comment out web tests * Initial work on query web For now we can query everything except tables * Support for querying tables Now we can query multiple tables just like before, now the only thing missing is the test coverage * finish off * comment out web test Co-authored-by: Luccas Mateus de Medeiros Gomes <luccasmmg@gmail.com>
2022-02-01 19:45:48 +01:00
"phf_shared 0.10.0",
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"rand",
query command with json, web, xml (#870) * query command with json, web, xml * query xml now working * clippy * comment out web tests * Initial work on query web For now we can query everything except tables * Support for querying tables Now we can query multiple tables just like before, now the only thing missing is the test coverage * finish off * comment out web test Co-authored-by: Luccas Mateus de Medeiros Gomes <luccasmmg@gmail.com>
2022-02-01 19:45:48 +01:00
]
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
[[package]]
name = "phf_generator"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.11.2"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "48e4cc64c2ad9ebe670cb8fd69dd50ae301650392e81c05f9bfcb2d5bdbc24b0"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
dependencies = [
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"phf_shared 0.11.2",
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"rand",
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
]
query command with json, web, xml (#870) * query command with json, web, xml * query xml now working * clippy * comment out web tests * Initial work on query web For now we can query everything except tables * Support for querying tables Now we can query multiple tables just like before, now the only thing missing is the test coverage * finish off * comment out web test Co-authored-by: Luccas Mateus de Medeiros Gomes <luccasmmg@gmail.com>
2022-02-01 19:45:48 +01:00
[[package]]
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
name = "phf_macros"
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
version = "0.11.2"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
checksum = "3444646e286606587e49f3bcf1679b8cef1dc2c5ecc29ddacaffc305180d464b"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
dependencies = [
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"phf_generator 0.11.2",
"phf_shared 0.11.2",
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
"proc-macro2",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
]
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
[[package]]
Add a simple scope variable
2021-11-02 04:08:05 +01:00
name = "phf_shared"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b6796ad771acdc0123d2a88dc428b5e38ef24456743ddb1744ed628f9815c096"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
dependencies = [
"siphasher",
]
[[package]]
name = "phf_shared"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.11.2"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "90fcb95eef784c2ac79119d1dd819e162b5da872ce6f3c3abe1e8ca1c082f72b"
Add a simple scope variable
2021-11-02 04:08:05 +01:00
dependencies = [
"siphasher",
]
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
[[package]]
name = "pin-project-lite"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.2.13"
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "8afb450f006bf6385ca15ef45d71d2288452bc3683ce2e2cacc0d18e4be60b58"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
Small restructuring
2019-05-23 06:30:43 +02:00
[[package]]
name = "pin-utils"
Evaluation of command arguments (#1801) * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * Finish adding the baseline refactors for argument invocation * Finish cleanup and add test * Add missing plugin references
2020-05-16 05:18:24 +02:00
version = "0.1.0"
Small restructuring
2019-05-23 06:30:43 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Evaluation of command arguments (#1801) * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * WIP * Finish adding the baseline refactors for argument invocation * Finish cleanup and add test * Add missing plugin references
2020-05-16 05:18:24 +02:00
checksum = "8b870d8c151b6f2fb93e84a13146138f05d02ed11c7e7c54f8826aaaf7c9f184"
Small restructuring
2019-05-23 06:30:43 +02:00
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "pkg-config"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
version = "0.3.27"
Bat
2019-05-18 03:24:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
checksum = "26072860ba924cbfa98ea39c8c19b4dd6a4a25423dbdf219c1eca91aa0cf6964"
Bat
2019-05-18 03:24:13 +02:00
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
[[package]]
name = "planus"
Polars upgrade 0.23 (#6303) * more lazy expressions * upgrade polars and correct functions * arg-where example * cargo clippy * restore modified filter files * correct string addition with str * correct string addition with str * correct message in test
2022-08-12 14:10:36 +02:00
version = "0.3.1"
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars upgrade 0.23 (#6303) * more lazy expressions * upgrade polars and correct functions * arg-where example * cargo clippy * restore modified filter files * correct string addition with str * correct string addition with str * correct message in test
2022-08-12 14:10:36 +02:00
checksum = "fc1691dd09e82f428ce8d6310bd6d5da2557c82ff17694d2a32cad7242aea89f"
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
dependencies = [
"array-init-cursor",
]
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
[[package]]
name = "plotters"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.3.5"
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "d2c224ba00d7cadd4d5c660deaf2098e5e80e07846537c51f9cfa4be50c1fd45"
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
dependencies = [
"num-traits",
"plotters-backend",
"plotters-svg",
"wasm-bindgen",
"web-sys",
]
[[package]]
name = "plotters-backend"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.3.5"
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "9e76628b4d3a7581389a35d5b6e2139607ad7c75b17aed325f210aa91f4a9609"
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
[[package]]
name = "plotters-svg"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.3.5"
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "38f6d39893cca0701371e3c27294f09797214b86f1fb951b89ade8ec04e2abab"
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
dependencies = [
"plotters-backend",
]
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
[[package]]
name = "polars"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.35.4"
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "df8e52f9236eb722da0990a70bbb1216dcc7a77bcb00c63439d2d982823e90d5"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
dependencies = [
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"getrandom",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
"polars-core",
"polars-io",
"polars-lazy",
Lazy dataframes (#5546) * lazyframe definition * expressions and lazy frames * new alias expression * more expression commands * updated to polars main * more expressions and groupby * more expressions, fetch and sort-by * csv reader * removed open csv * unique function * joining functions * join lazy frames commands with eager commands * corrected tests * Update .gitignore * Update .gitignore Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-05-16 09:27:43 +02:00
"polars-ops",
Start to move to polars 0.29 (#9145) This does part of the work of porting to polars 0.29. However, I am not familiar enough with this part of the codebase to finish it. Things to be done: - We match two times over `polars::Expr` but `Expr::Cache` isn't handled. I don't know what should be done here - `ArgExpr:::List` was renamed to `ArgExpr::Implode`. Does that mean that `dfr list` should be renamed to `dfr implode`? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-05-12 14:44:35 +02:00
"polars-sql",
Polars update (#4875) * update to polars 0.20 * add to date parser for series
2022-03-19 12:13:34 +01:00
"polars-time",
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 16:27:37 +01:00
"version_check",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
]
[[package]]
name = "polars-arrow"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.35.4"
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "dd503430a6d9779b07915d858865fe998317ef3cfef8973881f578ac5d4baae7"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
dependencies = [
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"ahash",
"arrow-format",
"atoi_simd",
"avro-schema",
"bytemuck",
"chrono",
"dyn-clone",
"either",
"ethnum",
"fast-float",
"foreign_vec",
"futures",
"getrandom",
"hashbrown 0.14.3",
"itoa",
"lz4",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"multiversion",
"num-traits",
"polars-error",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"polars-utils",
"rustc_version",
"ryu",
Lazy dataframes (#5546) * lazyframe definition * expressions and lazy frames * new alias expression * more expression commands * updated to polars main * more expressions and groupby * more expressions, fetch and sort-by * csv reader * removed open csv * unique function * joining functions * join lazy frames commands with eager commands * corrected tests * Update .gitignore * Update .gitignore Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-05-16 09:27:43 +02:00
"serde",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"simdutf8",
"streaming-iterator",
"strength_reduce",
"zstd",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
]
[[package]]
name = "polars-core"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.35.4"
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "ae73d5b8e55decde670caba1cc82b61f14bfb9a72503198f0997d657a98dcfd6"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
dependencies = [
Update `unicode-linebreak` to `0.1.5` (#9814) # Description This deduplicates `ahash` as it was previously an outdated build-dependency of `unicode-linebreak` Should provide a small benefit to initial from scratch compile. # User-Facing Changes None
2023-07-30 22:17:36 +02:00
"ahash",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"bitflags 2.4.1",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"bytemuck",
Polars update (#4875) * update to polars 0.20 * add to date parser for series
2022-03-19 12:13:34 +01:00
"chrono",
"comfy-table",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"either",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"hashbrown 0.14.3",
"indexmap",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"num-traits",
update polars (#5791)
2022-06-15 18:45:03 +02:00
"once_cell",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
"polars-arrow",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"polars-error",
"polars-row",
Lazy dataframes (#5546) * lazyframe definition * expressions and lazy frames * new alias expression * more expression commands * updated to polars main * more expressions and groupby * more expressions, fetch and sort-by * csv reader * removed open csv * unique function * joining functions * join lazy frames commands with eager commands * corrected tests * Update .gitignore * Update .gitignore Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-05-16 09:27:43 +02:00
"polars-utils",
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"rand",
Dataframe commands (#3498) * Sample command * Join command with checks * More dataframes commands * Groupby and aggregate commands * Missing feature dataframe flag * Renamed file
2021-05-27 07:09:48 +02:00
"rand_distr",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
"rayon",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"regex",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"serde",
Going deeper (#3864) * nuframe in its own type in UntaggedValue * Removed eager dataframe from enum * Dataframe created from list of values * Corrected order in dataframe columns * Returned tag from stream collection * Removed series from dataframe commands * Arithmetic operators * forced push * forced push * Replace all command * String commands * appending operations with dfs * Testing suite for dataframes * Unit test for dataframe commands * improved equality for dataframes * moving all dataframe operations to protocol * objects in dataframes * Removed cloning when converting to row
2021-07-29 23:16:30 +02:00
"serde_json",
Polars upgrade 0.23 (#6303) * more lazy expressions * upgrade polars and correct functions * arg-where example * cargo clippy * restore modified filter files * correct string addition with str * correct string addition with str * correct message in test
2022-08-12 14:10:36 +02:00
"smartstring",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
"thiserror",
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
"version_check",
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 16:27:37 +01:00
"xxhash-rust",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
]
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
[[package]]
name = "polars-error"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.35.4"
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "eb0520d68eaa9993ae0c741409d1526beff5b8f48e1d73e4381616f8152cf488"
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
dependencies = [
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"arrow-format",
"avro-schema",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"regex",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"simdutf8",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"thiserror",
]
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
[[package]]
name = "polars-io"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.35.4"
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "96e10a0745acd6009db64bef0ceb9e23a70b1c27b26a0a6517c91f3e6363bc06"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
dependencies = [
Update `unicode-linebreak` to `0.1.5` (#9814) # Description This deduplicates `ahash` as it was previously an outdated build-dependency of `unicode-linebreak` Should provide a small benefit to initial from scratch compile. # User-Facing Changes None
2023-07-30 22:17:36 +02:00
"ahash",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"async-trait",
"atoi_simd",
Update polars to 0.27.2 (#8154) Mostly to get rid of https://github.com/pola-rs/polars/pull/6098/files This currently breaks nushell's table formatting: ``` nu ❯ open-df forcing.arrow | first could not mmap compressed IPC file, defaulting to normal read╭───┬──────────┬────┬────────┬──────────┬───────┬──────────┬──────┬──────────┬─────╮ │ # │ time │ id │ demand │ drainage │ E_pot │ infiltra │ P │ priority │ ... │ │ │ │ │ │ │ │ tion │ │ │ │ ├───┼──────────┼────┼────────┼──────────┼───────┼──────────┼──────┼──────────┼─────┤ │ 0 │ 4 years │ 1 │ 0.00 │ 0.02 │ 0.00 │ 0.00 │ 0.00 │ 4.00 │ ... │ │ │ ago │ │ │ │ │ │ │ │ │ ╰───┴──────────┴────┴────────┴──────────┴───────┴──────────┴──────┴──────────┴─────╯ ``` @visr
2023-02-22 00:32:28 +01:00
"bytes",
"chrono",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"fast-float",
Update `polars` to `0.33` (#10672) # Description Open question: Undocumented behavior for the new argument `ambiguous` to the `as_datetime` methods. I cheated by passing a default (assuming empty string). This appears like an API primarily serving the python impl: https://pola-rs.github.io/polars/py-polars/html/reference/expressions/api/polars.Expr.str.to_datetime.html#polars-expr-str-to-datetime # User-Facing Changes Only dependent on breaking changes to the behavior of polars. # Tests + Formatting No observed changes to tests Manually checked `dfr as-datetime`, doesn't seem to panic.
2023-10-11 21:28:18 +02:00
"flate2",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"futures",
Start to move to polars 0.29 (#9145) This does part of the work of porting to polars 0.29. However, I am not familiar enough with this part of the codebase to finish it. Things to be done: - We match two times over `polars::Expr` but `Expr::Cache` isn't handled. I don't know what should be done here - `ArgExpr:::List` was renamed to `ArgExpr::Implode`. Does that mean that `dfr list` should be renamed to `dfr implode`? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-05-12 14:44:35 +02:00
"home",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"itoa",
Bump to 0.40 (#4129)
2021-11-16 09:53:03 +01:00
"memchr",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
"memmap2",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"num-traits",
update polars (#5791)
2022-06-15 18:45:03 +02:00
"once_cell",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"percent-encoding",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
"polars-arrow",
"polars-core",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"polars-error",
update dfr to polars 0.30.0 (#9424) # Description Update the polars dependency for dataframes to stay on-version. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 19:05:45 +02:00
"polars-json",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"polars-parquet",
Lazy dataframes (#5546) * lazyframe definition * expressions and lazy frames * new alias expression * more expression commands * updated to polars main * more expressions and groupby * more expressions, fetch and sort-by * csv reader * removed open csv * unique function * joining functions * join lazy frames commands with eager commands * corrected tests * Update .gitignore * Update .gitignore Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-05-16 09:27:43 +02:00
"polars-time",
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
"polars-utils",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
"rayon",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"regex",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"ryu",
Lazy dataframes (#5546) * lazyframe definition * expressions and lazy frames * new alias expression * more expression commands * updated to polars main * more expressions and groupby * more expressions, fetch and sort-by * csv reader * removed open csv * unique function * joining functions * join lazy frames commands with eager commands * corrected tests * Update .gitignore * Update .gitignore Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-05-16 09:27:43 +02:00
"serde",
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 16:27:37 +01:00
"serde_json",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"simd-json",
Bump to 0.40 (#4129)
2021-11-16 09:53:03 +01:00
"simdutf8",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"smartstring",
"tokio",
"tokio-util",
"zstd",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
]
update dfr to polars 0.30.0 (#9424) # Description Update the polars dependency for dataframes to stay on-version. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 19:05:45 +02:00
[[package]]
name = "polars-json"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.35.4"
update dfr to polars 0.30.0 (#9424) # Description Update the polars dependency for dataframes to stay on-version. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 19:05:45 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "93b9cb83c19daf334c398e56a9361bd79c8ad0718296db2afab08d476bd84559"
update dfr to polars 0.30.0 (#9424) # Description Update the polars dependency for dataframes to stay on-version. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 19:05:45 +02:00
dependencies = [
Update `unicode-linebreak` to `0.1.5` (#9814) # Description This deduplicates `ahash` as it was previously an outdated build-dependency of `unicode-linebreak` Should provide a small benefit to initial from scratch compile. # User-Facing Changes None
2023-07-30 22:17:36 +02:00
"ahash",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"chrono",
update dfr to polars 0.30.0 (#9424) # Description Update the polars dependency for dataframes to stay on-version. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 19:05:45 +02:00
"fallible-streaming-iterator",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"hashbrown 0.14.3",
"indexmap",
"itoa",
update dfr to polars 0.30.0 (#9424) # Description Update the polars dependency for dataframes to stay on-version. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 19:05:45 +02:00
"num-traits",
"polars-arrow",
"polars-error",
"polars-utils",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"ryu",
update dfr to polars 0.30.0 (#9424) # Description Update the polars dependency for dataframes to stay on-version. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 19:05:45 +02:00
"simd-json",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"streaming-iterator",
update dfr to polars 0.30.0 (#9424) # Description Update the polars dependency for dataframes to stay on-version. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 19:05:45 +02:00
]
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
[[package]]
name = "polars-lazy"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.35.4"
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "3555f759705be6dd0d3762d16a0b8787b2dc4da73b57465f3b2bf1a070ba8f20"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
dependencies = [
Update `unicode-linebreak` to `0.1.5` (#9814) # Description This deduplicates `ahash` as it was previously an outdated build-dependency of `unicode-linebreak` Should provide a small benefit to initial from scratch compile. # User-Facing Changes None
2023-07-30 22:17:36 +02:00
"ahash",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"bitflags 2.4.1",
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
"glob",
Start to move to polars 0.29 (#9145) This does part of the work of porting to polars 0.29. However, I am not familiar enough with this part of the codebase to finish it. Things to be done: - We match two times over `polars::Expr` but `Expr::Cache` isn't handled. I don't know what should be done here - `ArgExpr:::List` was renamed to `ArgExpr::Implode`. Does that mean that `dfr list` should be renamed to `dfr implode`? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-05-12 14:44:35 +02:00
"once_cell",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
"polars-arrow",
"polars-core",
"polars-io",
update dfr to polars 0.30.0 (#9424) # Description Update the polars dependency for dataframes to stay on-version. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 19:05:45 +02:00
"polars-json",
update polars (#5791)
2022-06-15 18:45:03 +02:00
"polars-ops",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"polars-pipe",
"polars-plan",
Polars update (#4875) * update to polars 0.20 * add to date parser for series
2022-03-19 12:13:34 +01:00
"polars-time",
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
"polars-utils",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
"rayon",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"smartstring",
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
"version_check",
Lazy dataframes (#5546) * lazyframe definition * expressions and lazy frames * new alias expression * more expression commands * updated to polars main * more expressions and groupby * more expressions, fetch and sort-by * csv reader * removed open csv * unique function * joining functions * join lazy frames commands with eager commands * corrected tests * Update .gitignore * Update .gitignore Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-05-16 09:27:43 +02:00
]
[[package]]
name = "polars-ops"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.35.4"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "1a7eb218296aaa7f79945f08288ca32ca3cf25fa505649eeee689ec21eebf636"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
dependencies = [
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"ahash",
Start to move to polars 0.29 (#9145) This does part of the work of porting to polars 0.29. However, I am not familiar enough with this part of the codebase to finish it. Things to be done: - We match two times over `polars::Expr` but `Expr::Cache` isn't handled. I don't know what should be done here - `ArgExpr:::List` was renamed to `ArgExpr::Implode`. Does that mean that `dfr list` should be renamed to `dfr implode`? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-05-12 14:44:35 +02:00
"argminmax",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"bytemuck",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"either",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"hashbrown 0.14.3",
"indexmap",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"memchr",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"num-traits",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"polars-arrow",
"polars-core",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"polars-error",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"polars-utils",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"rand",
"rand_distr",
"rayon",
Update `polars` to `0.33` (#10672) # Description Open question: Undocumented behavior for the new argument `ambiguous` to the `as_datetime` methods. I cheated by passing a default (assuming empty string). This appears like an API primarily serving the python impl: https://pola-rs.github.io/polars/py-polars/html/reference/expressions/api/polars.Expr.str.to_datetime.html#polars-expr-str-to-datetime # User-Facing Changes Only dependent on breaking changes to the behavior of polars. # Tests + Formatting No observed changes to tests Manually checked `dfr as-datetime`, doesn't seem to panic.
2023-10-11 21:28:18 +02:00
"regex",
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 16:27:37 +01:00
"serde",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"smartstring",
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
"version_check",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
]
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "polars-parquet"
version = "0.35.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "146010e4b7dd4d2d0e58ddc762f6361f77d7a0385c54471199370c17164f67dd"
dependencies = [
"ahash",
"async-stream",
"base64 0.21.5",
"brotli",
"ethnum",
"flate2",
"futures",
"lz4",
"num-traits",
"parquet-format-safe",
"polars-arrow",
"polars-error",
"polars-utils",
"seq-macro",
"simdutf8",
"snap",
"streaming-decompression",
"zstd",
]
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
[[package]]
name = "polars-pipe"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.35.4"
Lazy dataframes (#5546) * lazyframe definition * expressions and lazy frames * new alias expression * more expression commands * updated to polars main * more expressions and groupby * more expressions, fetch and sort-by * csv reader * removed open csv * unique function * joining functions * join lazy frames commands with eager commands * corrected tests * Update .gitignore * Update .gitignore Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-05-16 09:27:43 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "66094e7df64c932a9a7bdfe7df0c65efdcb192096e11a6a765a9778f78b4bdec"
Lazy dataframes (#5546) * lazyframe definition * expressions and lazy frames * new alias expression * more expression commands * updated to polars main * more expressions and groupby * more expressions, fetch and sort-by * csv reader * removed open csv * unique function * joining functions * join lazy frames commands with eager commands * corrected tests * Update .gitignore * Update .gitignore Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-05-16 09:27:43 +02:00
dependencies = [
Update `polars` to `0.33` (#10672) # Description Open question: Undocumented behavior for the new argument `ambiguous` to the `as_datetime` methods. I cheated by passing a default (assuming empty string). This appears like an API primarily serving the python impl: https://pola-rs.github.io/polars/py-polars/html/reference/expressions/api/polars.Expr.str.to_datetime.html#polars-expr-str-to-datetime # User-Facing Changes Only dependent on breaking changes to the behavior of polars. # Tests + Formatting No observed changes to tests Manually checked `dfr as-datetime`, doesn't seem to panic.
2023-10-11 21:28:18 +02:00
"crossbeam-channel",
"crossbeam-queue",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"enum_dispatch",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"hashbrown 0.14.3",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"num-traits",
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 16:27:37 +01:00
"polars-arrow",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"polars-core",
"polars-io",
Update polars to 0.27.2 (#8154) Mostly to get rid of https://github.com/pola-rs/polars/pull/6098/files This currently breaks nushell's table formatting: ``` nu ❯ open-df forcing.arrow | first could not mmap compressed IPC file, defaulting to normal read╭───┬──────────┬────┬────────┬──────────┬───────┬──────────┬──────┬──────────┬─────╮ │ # │ time │ id │ demand │ drainage │ E_pot │ infiltra │ P │ priority │ ... │ │ │ │ │ │ │ │ tion │ │ │ │ ├───┼──────────┼────┼────────┼──────────┼───────┼──────────┼──────┼──────────┼─────┤ │ 0 │ 4 years │ 1 │ 0.00 │ 0.02 │ 0.00 │ 0.00 │ 0.00 │ 4.00 │ ... │ │ │ ago │ │ │ │ │ │ │ │ │ ╰───┴──────────┴────┴────────┴──────────┴───────┴──────────┴──────┴──────────┴─────╯ ``` @visr
2023-02-22 00:32:28 +01:00
"polars-ops",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"polars-plan",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"polars-row",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"polars-utils",
"rayon",
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 16:27:37 +01:00
"smartstring",
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
"version_check",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
]
[[package]]
name = "polars-plan"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.35.4"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "10e32a0958ef854b132bad7f8369cb3237254635d5e864c99505bc0bc1035fbc"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
dependencies = [
Update `unicode-linebreak` to `0.1.5` (#9814) # Description This deduplicates `ahash` as it was previously an outdated build-dependency of `unicode-linebreak` Should provide a small benefit to initial from scratch compile. # User-Facing Changes None
2023-07-30 22:17:36 +02:00
"ahash",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"bytemuck",
Update polars to 0.27.2 (#8154) Mostly to get rid of https://github.com/pola-rs/polars/pull/6098/files This currently breaks nushell's table formatting: ``` nu ❯ open-df forcing.arrow | first could not mmap compressed IPC file, defaulting to normal read╭───┬──────────┬────┬────────┬──────────┬───────┬──────────┬──────┬──────────┬─────╮ │ # │ time │ id │ demand │ drainage │ E_pot │ infiltra │ P │ priority │ ... │ │ │ │ │ │ │ │ tion │ │ │ │ ├───┼──────────┼────┼────────┼──────────┼───────┼──────────┼──────┼──────────┼─────┤ │ 0 │ 4 years │ 1 │ 0.00 │ 0.02 │ 0.00 │ 0.00 │ 0.00 │ 4.00 │ ... │ │ │ ago │ │ │ │ │ │ │ │ │ ╰───┴──────────┴────┴────────┴──────────┴───────┴──────────┴──────┴──────────┴─────╯ ``` @visr
2023-02-22 00:32:28 +01:00
"once_cell",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"percent-encoding",
update polars (#5791)
2022-06-15 18:45:03 +02:00
"polars-arrow",
Lazy dataframes (#5546) * lazyframe definition * expressions and lazy frames * new alias expression * more expression commands * updated to polars main * more expressions and groupby * more expressions, fetch and sort-by * csv reader * removed open csv * unique function * joining functions * join lazy frames commands with eager commands * corrected tests * Update .gitignore * Update .gitignore Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-05-16 09:27:43 +02:00
"polars-core",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"polars-io",
"polars-ops",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"polars-parquet",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"polars-time",
"polars-utils",
"rayon",
Start to move to polars 0.29 (#9145) This does part of the work of porting to polars 0.29. However, I am not familiar enough with this part of the codebase to finish it. Things to be done: - We match two times over `polars::Expr` but `Expr::Cache` isn't handled. I don't know what should be done here - `ArgExpr:::List` was renamed to `ArgExpr::Implode`. Does that mean that `dfr list` should be renamed to `dfr implode`? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-05-12 14:44:35 +02:00
"regex",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"serde",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"smartstring",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"strum_macros",
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
"version_check",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
]
[[package]]
name = "polars-row"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.35.4"
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "d135ab81cac2906ba74ea8984c7e6025d081ae5867615bcefb4d84dfdb456dac"
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
dependencies = [
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"polars-arrow",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"polars-error",
"polars-utils",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
]
Start to move to polars 0.29 (#9145) This does part of the work of porting to polars 0.29. However, I am not familiar enough with this part of the codebase to finish it. Things to be done: - We match two times over `polars::Expr` but `Expr::Cache` isn't handled. I don't know what should be done here - `ArgExpr:::List` was renamed to `ArgExpr::Implode`. Does that mean that `dfr list` should be renamed to `dfr implode`? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-05-12 14:44:35 +02:00
[[package]]
name = "polars-sql"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.35.4"
Start to move to polars 0.29 (#9145) This does part of the work of porting to polars 0.29. However, I am not familiar enough with this part of the codebase to finish it. Things to be done: - We match two times over `polars::Expr` but `Expr::Cache` isn't handled. I don't know what should be done here - `ArgExpr:::List` was renamed to `ArgExpr::Implode`. Does that mean that `dfr list` should be renamed to `dfr implode`? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-05-12 14:44:35 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "b8dbd7786849a5e3ad1fde188bf38141632f626e3a57319b0bbf7a5f1d75519e"
Start to move to polars 0.29 (#9145) This does part of the work of porting to polars 0.29. However, I am not familiar enough with this part of the codebase to finish it. Things to be done: - We match two times over `polars::Expr` but `Expr::Cache` isn't handled. I don't know what should be done here - `ArgExpr:::List` was renamed to `ArgExpr::Implode`. Does that mean that `dfr list` should be renamed to `dfr implode`? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-05-12 14:44:35 +02:00
dependencies = [
"polars-arrow",
"polars-core",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"polars-error",
Start to move to polars 0.29 (#9145) This does part of the work of porting to polars 0.29. However, I am not familiar enough with this part of the codebase to finish it. Things to be done: - We match two times over `polars::Expr` but `Expr::Cache` isn't handled. I don't know what should be done here - `ArgExpr:::List` was renamed to `ArgExpr::Implode`. Does that mean that `dfr list` should be renamed to `dfr implode`? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-05-12 14:44:35 +02:00
"polars-lazy",
"polars-plan",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"rand",
Start to move to polars 0.29 (#9145) This does part of the work of porting to polars 0.29. However, I am not familiar enough with this part of the codebase to finish it. Things to be done: - We match two times over `polars::Expr` but `Expr::Cache` isn't handled. I don't know what should be done here - `ArgExpr:::List` was renamed to `ArgExpr::Implode`. Does that mean that `dfr list` should be renamed to `dfr implode`? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-05-12 14:44:35 +02:00
"serde",
"serde_json",
update sqlparser dep to 0.34 (#9549) # Description This PR updates the sqlparser dep to 0.34.0. closes #9525 # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-28 16:54:08 +02:00
"sqlparser",
Start to move to polars 0.29 (#9145) This does part of the work of porting to polars 0.29. However, I am not familiar enough with this part of the codebase to finish it. Things to be done: - We match two times over `polars::Expr` but `Expr::Cache` isn't handled. I don't know what should be done here - `ArgExpr:::List` was renamed to `ArgExpr::Implode`. Does that mean that `dfr list` should be renamed to `dfr implode`? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-05-12 14:44:35 +02:00
]
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
[[package]]
name = "polars-time"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.35.4"
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "aae56f79e9cedd617773c1c8f5ca84a31a8b1d593714959d5f799e7bdd98fe51"
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
dependencies = [
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"atoi",
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
"chrono",
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 16:27:37 +01:00
"now",
Update polars to 0.27.2 (#8154) Mostly to get rid of https://github.com/pola-rs/polars/pull/6098/files This currently breaks nushell's table formatting: ``` nu ❯ open-df forcing.arrow | first could not mmap compressed IPC file, defaulting to normal read╭───┬──────────┬────┬────────┬──────────┬───────┬──────────┬──────┬──────────┬─────╮ │ # │ time │ id │ demand │ drainage │ E_pot │ infiltra │ P │ priority │ ... │ │ │ │ │ │ │ │ tion │ │ │ │ ├───┼──────────┼────┼────────┼──────────┼───────┼──────────┼──────┼──────────┼─────┤ │ 0 │ 4 years │ 1 │ 0.00 │ 0.02 │ 0.00 │ 0.00 │ 0.00 │ 4.00 │ ... │ │ │ ago │ │ │ │ │ │ │ │ │ ╰───┴──────────┴────┴────────┴──────────┴───────┴──────────┴──────┴──────────┴─────╯ ``` @visr
2023-02-22 00:32:28 +01:00
"once_cell",
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
"polars-arrow",
Polars update (#4875) * update to polars 0.20 * add to date parser for series
2022-03-19 12:13:34 +01:00
"polars-core",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"polars-error",
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 16:27:37 +01:00
"polars-ops",
update polars (#5791)
2022-06-15 18:45:03 +02:00
"polars-utils",
Update polars to 0.27.2 (#8154) Mostly to get rid of https://github.com/pola-rs/polars/pull/6098/files This currently breaks nushell's table formatting: ``` nu ❯ open-df forcing.arrow | first could not mmap compressed IPC file, defaulting to normal read╭───┬──────────┬────┬────────┬──────────┬───────┬──────────┬──────┬──────────┬─────╮ │ # │ time │ id │ demand │ drainage │ E_pot │ infiltra │ P │ priority │ ... │ │ │ │ │ │ │ │ tion │ │ │ │ ├───┼──────────┼────┼────────┼──────────┼───────┼──────────┼──────┼──────────┼─────┤ │ 0 │ 4 years │ 1 │ 0.00 │ 0.02 │ 0.00 │ 0.00 │ 0.00 │ 4.00 │ ... │ │ │ ago │ │ │ │ │ │ │ │ │ ╰───┴──────────┴────┴────────┴──────────┴───────┴──────────┴──────┴──────────┴─────╯ ``` @visr
2023-02-22 00:32:28 +01:00
"regex",
Lazy dataframes (#5546) * lazyframe definition * expressions and lazy frames * new alias expression * more expression commands * updated to polars main * more expressions and groupby * more expressions, fetch and sort-by * csv reader * removed open csv * unique function * joining functions * join lazy frames commands with eager commands * corrected tests * Update .gitignore * Update .gitignore Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-05-16 09:27:43 +02:00
"serde",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"smartstring",
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
]
[[package]]
name = "polars-utils"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.35.4"
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "da6ce68169fe61d46958c8eab7447360f30f2f23f6e24a0ce703a14b0a3cfbfc"
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
dependencies = [
Update `unicode-linebreak` to `0.1.5` (#9814) # Description This deduplicates `ahash` as it was previously an outdated build-dependency of `unicode-linebreak` Should provide a small benefit to initial from scratch compile. # User-Facing Changes None
2023-07-30 22:17:36 +02:00
"ahash",
Update `polars` to `0.33` (#10672) # Description Open question: Undocumented behavior for the new argument `ambiguous` to the `as_datetime` methods. I cheated by passing a default (assuming empty string). This appears like an API primarily serving the python impl: https://pola-rs.github.io/polars/py-polars/html/reference/expressions/api/polars.Expr.str.to_datetime.html#polars-expr-str-to-datetime # User-Facing Changes Only dependent on breaking changes to the behavior of polars. # Tests + Formatting No observed changes to tests Manually checked `dfr as-datetime`, doesn't seem to panic.
2023-10-11 21:28:18 +02:00
"bytemuck",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"hashbrown 0.14.3",
"indexmap",
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
"num-traits",
Update polars to 0.27.2 (#8154) Mostly to get rid of https://github.com/pola-rs/polars/pull/6098/files This currently breaks nushell's table formatting: ``` nu ❯ open-df forcing.arrow | first could not mmap compressed IPC file, defaulting to normal read╭───┬──────────┬────┬────────┬──────────┬───────┬──────────┬──────┬──────────┬─────╮ │ # │ time │ id │ demand │ drainage │ E_pot │ infiltra │ P │ priority │ ... │ │ │ │ │ │ │ │ tion │ │ │ │ ├───┼──────────┼────┼────────┼──────────┼───────┼──────────┼──────┼──────────┼─────┤ │ 0 │ 4 years │ 1 │ 0.00 │ 0.02 │ 0.00 │ 0.00 │ 0.00 │ 4.00 │ ... │ │ │ ago │ │ │ │ │ │ │ │ │ ╰───┴──────────┴────┴────────┴──────────┴───────┴──────────┴──────┴──────────┴─────╯ ``` @visr
2023-02-22 00:32:28 +01:00
"once_cell",
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
"polars-error",
Polars update (#4875) * update to polars 0.20 * add to date parser for series
2022-03-19 12:13:34 +01:00
"rayon",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"smartstring",
update dfr to polars 0.30.0 (#9424) # Description Update the polars dependency for dataframes to stay on-version. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 19:05:45 +02:00
"sysinfo",
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
"version_check",
Polars upgrade (#4665) * polars upgrade * Update describe.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-02-27 17:10:29 +01:00
]
new `glob` command (#5087)
2022-04-04 22:45:01 +02:00
[[package]]
name = "pori"
version = "0.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a4a63d338dec139f56dacc692ca63ad35a6be6a797442479b55acd611d79e906"
dependencies = [
Remove `math eval` command (#7284) Reasoning: Most missing math commands are implemented with #7258. The `meval` crate itself declares that it doesn't strive to stringent standards (https://docs.rs/meval/latest/meval/#related-projects). For example no particular special casing or transformations are performed to ensure numerical stability. It uses the same rust `std` library functions we use or have access to (and `f64`). While the command call syntax in nushell may be a bit more verbose, having a single source of truth and common commands is beneficial. Furthermore the `math` commands can themselves implement broadcasting over lists (or table columns). Closes #7073 Removed dependencies: - `meval` - `nom 1.2.4` (duplicate) User-Facing Changes: Scripts using `math eval` will break. We remove a further `eval` like behavior to get results through runtime evaluation (albeit limited in scope) Tests: - Updated tests that internally used `math eval`. - Removed one test that primarily used `math eval` to obtain a result from `str join`
2023-01-04 23:50:18 +01:00
"nom",
new `glob` command (#5087)
2022-04-04 22:45:01 +02:00
]
Progress bar Implementation (#7661) # Description _(Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience.)_ I implemented the status bar we talk about yesterday. The idea was inspired by the progress bar of `wget`. I decided to go for the second suggestion by `@Reilly` > 2. add an Option<usize> or whatever to RawStream (and ListStream?) for situations where you do know the length ahead of time For now only works with the command `save` but after the approve of this PR we can see how we can implement it on commands like `cp` and `mv` When using `fetch` nushell will check if there is any `content-length` attribute in the request header. If so, then `fetch` will send it through the new `Option` variable in the `RawStream` to the `save`. If we know the total size we show the progress bar ![nu_pb01](https://user-images.githubusercontent.com/38369407/210298647-07ee55ea-e751-41b1-a84d-f72ec1f6e9e5.jpg) but if we don't then we just show the stats like: data already saved, bytes per second, and time lapse. ![nu_pb02](https://user-images.githubusercontent.com/38369407/210298698-1ef65f51-40cc-4481-83de-309cbd1049cb.jpg) ![nu_pb03](https://user-images.githubusercontent.com/38369407/210298701-eef2ef13-9206-4a98-8202-e4fe5531d79d.jpg) Please let me know If I need to make any changes and I will be happy to do it. # User-Facing Changes A new flag (`--progress` `-p`) was added to the `save` command Examples: ```nu fetch https://github.com/torvalds/linux/archive/refs/heads/master.zip | save --progress -f main.zip fetch https://releases.ubuntu.com/22.04.1/ubuntu-22.04.1-desktop-amd64.iso | save --progress -f main.zip open main.zip --raw | save --progress main.copy ``` # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - I am getting some errors and its weird because the errors are showing up in files i haven't touch. Is this normal? # 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. Co-authored-by: Reilly Wood <reilly.wood@icloud.com>
2023-01-11 02:57:48 +01:00
[[package]]
name = "portable-atomic"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "1.6.0"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "7170ef9988bc169ba16dd36a7fa041e5c4cbeb6a35b76d4c03daded371eae7c0"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
[[package]]
name = "powerfmt"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "439ee305def115ba05938db6eb1644ff94165c5ab5e9420d1c1bcedbba909391"
Progress bar Implementation (#7661) # Description _(Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience.)_ I implemented the status bar we talk about yesterday. The idea was inspired by the progress bar of `wget`. I decided to go for the second suggestion by `@Reilly` > 2. add an Option<usize> or whatever to RawStream (and ListStream?) for situations where you do know the length ahead of time For now only works with the command `save` but after the approve of this PR we can see how we can implement it on commands like `cp` and `mv` When using `fetch` nushell will check if there is any `content-length` attribute in the request header. If so, then `fetch` will send it through the new `Option` variable in the `RawStream` to the `save`. If we know the total size we show the progress bar ![nu_pb01](https://user-images.githubusercontent.com/38369407/210298647-07ee55ea-e751-41b1-a84d-f72ec1f6e9e5.jpg) but if we don't then we just show the stats like: data already saved, bytes per second, and time lapse. ![nu_pb02](https://user-images.githubusercontent.com/38369407/210298698-1ef65f51-40cc-4481-83de-309cbd1049cb.jpg) ![nu_pb03](https://user-images.githubusercontent.com/38369407/210298701-eef2ef13-9206-4a98-8202-e4fe5531d79d.jpg) Please let me know If I need to make any changes and I will be happy to do it. # User-Facing Changes A new flag (`--progress` `-p`) was added to the `save` command Examples: ```nu fetch https://github.com/torvalds/linux/archive/refs/heads/master.zip | save --progress -f main.zip fetch https://releases.ubuntu.com/22.04.1/ubuntu-22.04.1-desktop-amd64.iso | save --progress -f main.zip open main.zip --raw | save --progress main.copy ``` # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - I am getting some errors and its weird because the errors are showing up in files i haven't touch. Is this normal? # 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. Co-authored-by: Reilly Wood <reilly.wood@icloud.com>
2023-01-11 02:57:48 +01:00
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
[[package]]
name = "ppv-lite86"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "0.2.17"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "5b40af805b3121feab8a3c29f04d8ad262fa8e0561883e7653e024ae4479e6de"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
[[package]]
name = "precomputed-hash"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "925383efa346730478fb4838dbe9137d2a47675ad789c546d150a6e1dd4ab31c"
--no-edit
2019-11-04 16:47:03 +01:00
[[package]]
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
name = "predicates"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "3.0.4"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "6dfc28575c2e3f19cb3c73b93af36460ae898d426eba6fc15b9bd2a5220758a0"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
dependencies = [
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
"anstyle",
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
"difflib",
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
"itertools 0.11.0",
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
"predicates-core",
]
[[package]]
name = "predicates-core"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
version = "1.0.6"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
checksum = "b794032607612e7abeb4db69adb4e33590fa6cf1149e95fd7cb00e634b92f174"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
[[package]]
name = "predicates-tree"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
version = "1.0.9"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
checksum = "368ba315fb8c5052ab692e68a0eefec6ec57b23a36959c14496f0b0df2c0cecf"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
dependencies = [
"predicates-core",
add rm command + stubs for open and save
2021-10-10 06:13:15 +02:00
"termtree",
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
]
[[package]]
name = "pretty_assertions"
Bump pretty_assertions from 1.3.0 to 1.4.0 (#9781)
2023-07-24 07:41:03 +02:00
version = "1.4.0"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump pretty_assertions from 1.3.0 to 1.4.0 (#9781)
2023-07-24 07:41:03 +02:00
checksum = "af7cee1a6c8a5b9208b3cb1061f10c0cb689087b3d8ce85fb9d2dd7a29b6ba66"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
dependencies = [
"diff",
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
"yansi",
--no-edit
2019-11-04 16:47:03 +01:00
]
`string | fill` counts clusters, not graphemes; and doesn't count ANSI escape codes (#8134) Enhancement of new `fill` command (#7846) to handle content including ANSI escape codes for formatting or multi-code-point Unicode grapheme clusters. In both of these cases, the content is (many) bytes longer than its visible length, and `fill` was counting the extra bytes so not adding enough fill characters. # Description This script: ```rust # the teacher emoji `\u{1F9D1}\u{200D}\u{1F3EB}` is 3 code points, but only 1 print position wide. echo "This output should be 3 print positions wide, with leading and trailing `+`" $"\u{1F9D1}\u{200D}\u{1F3EB}" | fill -c "+" -w 3 -a "c" echo "This output should be 3 print positions wide, with leading and trailing `+`" $"(ansi green)a(ansi reset)" | fill -c "+" -w 3 -a c echo "" ``` Was producing this output: ```rust This output should be 3 print positions wide, with leading and trailing `+` 🧑‍🏫 This output should be 3 print positions wide, with leading and trailing `+` a ``` After this PR, it produces this output: ```rust This output should be 3 print positions wide, with leading and trailing `+` +🧑‍🏫+ This output should be 3 print positions wide, with leading and trailing `+` +a+ ``` # User-Facing Changes Users may have to undo fixes they may have introduced to work around the former behavior. I have one such in my prompt string that I can now revert. # Tests + Formatting Don't forget to add tests that cover your changes. -- Done Make sure you've run and fixed any issues with these commands: - [x] `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [x] `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - [x] `cargo test --workspace` to check that all tests pass # After Submitting `fill` command not documented in the book, and it still talks about `str lpad/rpad`. I'll fix. Note added dependency on a new library `print-positions`, which is an iterator that yields a complete print position (cluster + Ansi sequence) per call. Should this be vendored?
2023-02-20 13:32:20 +01:00
[[package]]
name = "print-positions"
version = "0.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1df593470e3ef502e48cb0cfc9a3a61e5f61e967b78e1ed35a67ac615cfbd208"
dependencies = [
"unicode-segmentation",
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "proc-macro2"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "1.0.70"
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "39278fbbf5fb4f646ce651690877f89d1c5811a3d4acb27700c1cb3cdb78fd3b"
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
dependencies = [
cargo update (#5639)
2022-05-25 19:13:14 +02:00
"unicode-ident",
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
]
Add tree sink
2019-06-07 09:50:26 +02:00
[[package]]
Add nu-system and rewrite ps command (#734) * Add nu-system and rewrite ps command * Add more deps * Add more deps * clippy * clippy * clippy * clippy * clippy * clippy
2022-01-14 07:20:53 +01:00
name = "procfs"
Bump `procfs` to 0.16.0 (#11115) Fix the breaking changes. Get's rid of some outdated transitive dependencies. Sadly we need to expose more of `procfs` to `nu-command` based on how the features of `nu-system` are exposed right now. Conditional compilation/dependencies from hell included Supersedes #11101
2023-11-20 21:22:35 +01:00
version = "0.16.0"
Add nu-system and rewrite ps command (#734) * Add nu-system and rewrite ps command * Add more deps * Add more deps * clippy * clippy * clippy * clippy * clippy * clippy
2022-01-14 07:20:53 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump `procfs` to 0.16.0 (#11115) Fix the breaking changes. Get's rid of some outdated transitive dependencies. Sadly we need to expose more of `procfs` to `nu-command` based on how the features of `nu-system` are exposed right now. Conditional compilation/dependencies from hell included Supersedes #11101
2023-11-20 21:22:35 +01:00
checksum = "731e0d9356b0c25f16f33b5be79b1c57b562f141ebfcdb0ad8ac2c13a24293b4"
Add nu-system and rewrite ps command (#734) * Add nu-system and rewrite ps command * Add more deps * Add more deps * clippy * clippy * clippy * clippy * clippy * clippy
2022-01-14 07:20:53 +01:00
dependencies = [
Bump `procfs` to 0.16.0 (#11115) Fix the breaking changes. Get's rid of some outdated transitive dependencies. Sadly we need to expose more of `procfs` to `nu-command` based on how the features of `nu-system` are exposed right now. Conditional compilation/dependencies from hell included Supersedes #11101
2023-11-20 21:22:35 +01:00
"bitflags 2.4.1",
Add nu-system and rewrite ps command (#734) * Add nu-system and rewrite ps command * Add more deps * Add more deps * clippy * clippy * clippy * clippy * clippy * clippy
2022-01-14 07:20:53 +01:00
"chrono",
"flate2",
"hex",
"lazy_static",
Bump `procfs` to 0.16.0 (#11115) Fix the breaking changes. Get's rid of some outdated transitive dependencies. Sadly we need to expose more of `procfs` to `nu-command` based on how the features of `nu-system` are exposed right now. Conditional compilation/dependencies from hell included Supersedes #11101
2023-11-20 21:22:35 +01:00
"procfs-core",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"rustix 0.38.28",
Bump `procfs` to 0.16.0 (#11115) Fix the breaking changes. Get's rid of some outdated transitive dependencies. Sadly we need to expose more of `procfs` to `nu-command` based on how the features of `nu-system` are exposed right now. Conditional compilation/dependencies from hell included Supersedes #11101
2023-11-20 21:22:35 +01:00
]
[[package]]
name = "procfs-core"
version = "0.16.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2d3554923a69f4ce04c4a754260c338f505ce22642d3830e049a399fc2059a29"
dependencies = [
"bitflags 2.4.1",
"chrono",
"hex",
Add tree sink
2019-06-07 09:50:26 +02:00
]
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "psm"
version = "0.1.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5787f7cda34e3033a72192c018bc5883100330f362ef279a8cbccfce8bb4e874"
dependencies = [
"cc",
]
make `date format` supports locale (#6306) * add --locale flag to make output support locale * implement again based on nu-utils get_system_locale_string * add comment
2022-08-14 15:07:04 +02:00
[[package]]
name = "pure-rust-locales"
fix some new chrono warnings (#10384) # Description This PR cleans up some warnings on the latest chrono dependency. # 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-09-15 22:46:25 +02:00
version = "0.7.0"
make `date format` supports locale (#6306) * add --locale flag to make output support locale * implement again based on nu-utils get_system_locale_string * add comment
2022-08-14 15:07:04 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
fix some new chrono warnings (#10384) # Description This PR cleans up some warnings on the latest chrono dependency. # 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-09-15 22:46:25 +02:00
checksum = "ed02a829e62dc2715ceb8afb4f80e298148e1345749ceb369540fe0eb3368432"
make `date format` supports locale (#6306) * add --locale flag to make output support locale * implement again based on nu-utils get_system_locale_string * add comment
2022-08-14 15:07:04 +02:00
Adding ~user tilde recognition in file paths (#5251) * Added search terms to math commands * Attempts to add ~user. From: // Extend this to work with "~user" style of home paths * Clippy recommendation * clippy suggestions, again. * fixing non-compilation on windows and macos * fmt apparently does not like my imports * even more clippy issues. * less expect(), single conversion, match. Should work for MacOS too. * Attempted to add functionality for windows: all it does is take the home path of current user, and replace the username. * silly mistake in Windows version of user_home_dir() * Update tilde.rs * user_home_dir now returns a path instead of a string - should be smoother with no conversions to string * clippy warnings * clippy warnings 2 * Changed user_home_dir to return PathBuf now. * Changed user_home_dir to return PathBuf now. * forgot to fmt * fixed windows build errors from modifying pathbuf but not returning it * fixed windows clippy errors from returning () instead of pathbuf * forgot to fmt * borrowed path did not live long enough. * previously, path.push did not work because rest_of_path started with "/" - it was not relative. Removing the / makes it a relative path again. * Issue fixed. * Update tilde.rs * fmt. * There is now a zero chance of panic. All expect()s have been removed.
2022-04-25 00:12:57 +02:00
[[package]]
name = "pwd"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
version = "1.4.0"
Adding ~user tilde recognition in file paths (#5251) * Added search terms to math commands * Attempts to add ~user. From: // Extend this to work with "~user" style of home paths * Clippy recommendation * clippy suggestions, again. * fixing non-compilation on windows and macos * fmt apparently does not like my imports * even more clippy issues. * less expect(), single conversion, match. Should work for MacOS too. * Attempted to add functionality for windows: all it does is take the home path of current user, and replace the username. * silly mistake in Windows version of user_home_dir() * Update tilde.rs * user_home_dir now returns a path instead of a string - should be smoother with no conversions to string * clippy warnings * clippy warnings 2 * Changed user_home_dir to return PathBuf now. * Changed user_home_dir to return PathBuf now. * forgot to fmt * fixed windows build errors from modifying pathbuf but not returning it * fixed windows clippy errors from returning () instead of pathbuf * forgot to fmt * borrowed path did not live long enough. * previously, path.push did not work because rest_of_path started with "/" - it was not relative. Removing the / makes it a relative path again. * Issue fixed. * Update tilde.rs * fmt. * There is now a zero chance of panic. All expect()s have been removed.
2022-04-25 00:12:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
checksum = "72c71c0c79b9701efe4e1e4b563b2016dd4ee789eb99badcb09d61ac4b92e4a2"
Adding ~user tilde recognition in file paths (#5251) * Added search terms to math commands * Attempts to add ~user. From: // Extend this to work with "~user" style of home paths * Clippy recommendation * clippy suggestions, again. * fixing non-compilation on windows and macos * fmt apparently does not like my imports * even more clippy issues. * less expect(), single conversion, match. Should work for MacOS too. * Attempted to add functionality for windows: all it does is take the home path of current user, and replace the username. * silly mistake in Windows version of user_home_dir() * Update tilde.rs * user_home_dir now returns a path instead of a string - should be smoother with no conversions to string * clippy warnings * clippy warnings 2 * Changed user_home_dir to return PathBuf now. * Changed user_home_dir to return PathBuf now. * forgot to fmt * fixed windows build errors from modifying pathbuf but not returning it * fixed windows clippy errors from returning () instead of pathbuf * forgot to fmt * borrowed path did not live long enough. * previously, path.push did not work because rest_of_path started with "/" - it was not relative. Removing the / makes it a relative path again. * Issue fixed. * Update tilde.rs * fmt. * There is now a zero chance of panic. All expect()s have been removed.
2022-04-25 00:12:57 +02:00
dependencies = [
"libc",
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
"thiserror",
Adding ~user tilde recognition in file paths (#5251) * Added search terms to math commands * Attempts to add ~user. From: // Extend this to work with "~user" style of home paths * Clippy recommendation * clippy suggestions, again. * fixing non-compilation on windows and macos * fmt apparently does not like my imports * even more clippy issues. * less expect(), single conversion, match. Should work for MacOS too. * Attempted to add functionality for windows: all it does is take the home path of current user, and replace the username. * silly mistake in Windows version of user_home_dir() * Update tilde.rs * user_home_dir now returns a path instead of a string - should be smoother with no conversions to string * clippy warnings * clippy warnings 2 * Changed user_home_dir to return PathBuf now. * Changed user_home_dir to return PathBuf now. * forgot to fmt * fixed windows build errors from modifying pathbuf but not returning it * fixed windows clippy errors from returning () instead of pathbuf * forgot to fmt * borrowed path did not live long enough. * previously, path.push did not work because rest_of_path started with "/" - it was not relative. Removing the / makes it a relative path again. * Issue fixed. * Update tilde.rs * fmt. * There is now a zero chance of panic. All expect()s have been removed.
2022-04-25 00:12:57 +02:00
]
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "quick-error"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 07:11:42 +01:00
version = "1.2.3"
Bat
2019-05-18 03:24:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 07:11:42 +01:00
checksum = "a1d01941d82fa2ab50be1e79e6714289dd7cde78eba4c074bc5a4374f650dfe0"
Bat
2019-05-18 03:24:13 +02:00
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
[[package]]
name = "quick-error"
version = "2.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a993555f31e5a609f617c12db6250dedcac1b0a85076912c436e6fc9b2c8e6a3"
Bump quick-xml from 0.25.0 to 0.27.1 (#7768)
2023-01-16 03:06:31 +01:00
[[package]]
name = "quick-xml"
Bump quick-xml from 0.29.0 to 0.30.0 (#9870)
2023-08-14 15:58:15 +02:00
version = "0.30.0"
Bump quick-xml from 0.25.0 to 0.27.1 (#7768)
2023-01-16 03:06:31 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump quick-xml from 0.29.0 to 0.30.0 (#9870)
2023-08-14 15:58:15 +02:00
checksum = "eff6510e86862b57b210fd8cbe8ed3f0d7d600b9c2863cd4549a2e033c66e956"
Bump quick-xml from 0.25.0 to 0.27.1 (#7768)
2023-01-16 03:06:31 +01:00
dependencies = [
Bump `calamine` and fix clippy (#10314) Upgrade calamine to 0.22 Reduces one potential dependency duplication Supersedes #10305 Includes fixes for clippy lints as API changed to return owned data.
2023-09-11 12:39:52 +02:00
"encoding_rs",
Bump quick-xml from 0.25.0 to 0.27.1 (#7768)
2023-01-16 03:06:31 +01:00
"memchr",
]
Add quickcheck (#1574) * Move uptime to being a duration value * Adds our first quickcheck test
2020-04-11 21:05:59 +02:00
[[package]]
name = "quickcheck"
Update some deps (#3011)
2021-02-05 21:54:54 +01:00
version = "1.0.3"
Add quickcheck (#1574) * Move uptime to being a duration value * Adds our first quickcheck test
2020-04-11 21:05:59 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update some deps (#3011)
2021-02-05 21:54:54 +01:00
checksum = "588f6378e4dd99458b60ec275b4477add41ce4fa9f64dcba6f15adccb19b50d6"
Add quickcheck (#1574) * Move uptime to being a duration value * Adds our first quickcheck test
2020-04-11 21:05:59 +02:00
dependencies = [
Replace pretty_env_logger with simplelog (#6274) Fixes #5963 Signed-off-by: nibon7 <nibon7@163.com>
2022-08-09 18:44:37 +02:00
"env_logger",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"log",
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"rand",
Add quickcheck (#1574) * Move uptime to being a duration value * Adds our first quickcheck test
2020-04-11 21:05:59 +02:00
]
[[package]]
name = "quickcheck_macros"
Update some deps (#3011)
2021-02-05 21:54:54 +01:00
version = "1.0.0"
Add quickcheck (#1574) * Move uptime to being a duration value * Adds our first quickcheck test
2020-04-11 21:05:59 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update some deps (#3011)
2021-02-05 21:54:54 +01:00
checksum = "b22a693222d716a9587786f37ac3f6b4faedb5b80c23914e7303ff5a1d8016e9"
Add quickcheck (#1574) * Move uptime to being a duration value * Adds our first quickcheck test
2020-04-11 21:05:59 +02:00
dependencies = [
"proc-macro2",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"quote",
Bump miette from 5.6.0 to 5.7.0 (#8720)
2023-04-06 22:39:54 +02:00
"syn 1.0.109",
Add quickcheck (#1574) * Move uptime to being a duration value * Adds our first quickcheck test
2020-04-11 21:05:59 +02:00
]
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
[[package]]
name = "quote"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.0.33"
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "5267fca4496028628a95160fc423a33e8b2e6af8a5302579e322e4b520293cae"
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"proc-macro2",
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
]
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "quoted_printable"
version = "0.4.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5a3866219251662ec3b26fc217e3e05bf9c4f84325234dfb96bf0bf840889e49"
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
[[package]]
name = "rand"
corrected history menu (#4814)
2022-03-10 21:58:11 +01:00
version = "0.8.5"
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
corrected history menu (#4814)
2022-03-10 21:58:11 +01:00
checksum = "34af8d1a0e25924bc5b7c43c079c942339d8f0a8b57c39049bef581b46327404"
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
dependencies = [
"libc",
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"rand_chacha",
"rand_core",
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
]
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
[[package]]
name = "rand_chacha"
Add Test Case for Special Character Paths (#3596) Added test cases that ensure that special characters in path names are passed to external commands correctly. These cases have been implemented with rstest to reuse existing test code.
2021-06-28 12:16:03 +02:00
version = "0.3.1"
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add Test Case for Special Character Paths (#3596) Added test cases that ensure that special characters in path names are passed to external commands correctly. These cases have been implemented with rstest to reuse existing test code.
2021-06-28 12:16:03 +02:00
checksum = "e6c10a63a0fa32252be49d21e7709d4d4baf8d231c2dbce1eaa8141b9b127d88"
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
dependencies = [
"ppv-lite86",
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"rand_core",
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
]
[[package]]
name = "rand_core"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
version = "0.6.4"
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
checksum = "ec0be4795e2f6a28069bec0b5ff3e2ac9bafc99e6a9a7dc3547996c5c816922c"
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
dependencies = [
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"getrandom",
Bat
2019-05-18 03:24:13 +02:00
]
Dataframe commands (#3498) * Sample command * Join command with checks * More dataframes commands * Groupby and aggregate commands * Missing feature dataframe flag * Renamed file
2021-05-27 07:09:48 +02:00
[[package]]
name = "rand_distr"
list keybinding options (#906) * list keybinding optins * list keybinding options * clippy error
2022-02-04 07:47:18 +01:00
version = "0.4.3"
Dataframe commands (#542) * groupby object * aggregate command * eager commands * rest of dataframe commands
2021-12-21 19:32:09 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
list keybinding options (#906) * list keybinding optins * list keybinding options * clippy error
2022-02-04 07:47:18 +01:00
checksum = "32cb0b9bc82b0a0876c2dd994a7e7a2683d3e7390ca40e6886785ef0c7e3ee31"
Dataframe commands (#542) * groupby object * aggregate command * eager commands * rest of dataframe commands
2021-12-21 19:32:09 +01:00
dependencies = [
"num-traits",
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"rand",
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
]
using ratatui instead of tui (#8952) # Description Refer to https://github.com/fdehau/tui-rs/issues/654, I found that tui maybe un-maintained, instead, I'd suggest to use an actively fork https://github.com/tui-rs-revival/ratatui cc: @zhiburt # User-Facing Changes NaN
2023-04-26 01:07:23 +02:00
[[package]]
name = "ratatui"
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 02:22:25 +02:00
version = "0.23.0"
using ratatui instead of tui (#8952) # Description Refer to https://github.com/fdehau/tui-rs/issues/654, I found that tui maybe un-maintained, instead, I'd suggest to use an actively fork https://github.com/tui-rs-revival/ratatui cc: @zhiburt # User-Facing Changes NaN
2023-04-26 01:07:23 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 02:22:25 +02:00
checksum = "2e2e4cd95294a85c3b4446e63ef054eea43e0205b1fd60120c16b74ff7ff96ad"
using ratatui instead of tui (#8952) # Description Refer to https://github.com/fdehau/tui-rs/issues/654, I found that tui maybe un-maintained, instead, I'd suggest to use an actively fork https://github.com/tui-rs-revival/ratatui cc: @zhiburt # User-Facing Changes NaN
2023-04-26 01:07:23 +02:00
dependencies = [
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"bitflags 2.4.1",
using ratatui instead of tui (#8952) # Description Refer to https://github.com/fdehau/tui-rs/issues/654, I found that tui maybe un-maintained, instead, I'd suggest to use an actively fork https://github.com/tui-rs-revival/ratatui cc: @zhiburt # User-Facing Changes NaN
2023-04-26 01:07:23 +02:00
"cassowary",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"crossterm",
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 02:22:25 +02:00
"indoc",
"itertools 0.11.0",
"paste",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"strum",
using ratatui instead of tui (#8952) # Description Refer to https://github.com/fdehau/tui-rs/issues/654, I found that tui maybe un-maintained, instead, I'd suggest to use an actively fork https://github.com/tui-rs-revival/ratatui cc: @zhiburt # User-Facing Changes NaN
2023-04-26 01:07:23 +02:00
"unicode-segmentation",
"unicode-width",
]
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 15:47:30 +02:00
[[package]]
name = "rayon"
Bump rayon from 1.7.0 to 1.8.0 (#10497)
2023-09-25 13:00:05 +02:00
version = "1.8.0"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 15:47:30 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump rayon from 1.7.0 to 1.8.0 (#10497)
2023-09-25 13:00:05 +02:00
checksum = "9c27db03db7734835b3f53954b534c91069375ce6ccaa2e065441e07d9b6cdb1"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 15:47:30 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"either",
"rayon-core",
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 15:47:30 +02:00
]
[[package]]
name = "rayon-core"
Bump rayon from 1.7.0 to 1.8.0 (#10497)
2023-09-25 13:00:05 +02:00
version = "1.12.0"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 15:47:30 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump rayon from 1.7.0 to 1.8.0 (#10497)
2023-09-25 13:00:05 +02:00
checksum = "5ce3fb6ad83f861aac485e76e1985cd109d9a3713802152be56c3b1f0e0658ed"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 15:47:30 +02:00
dependencies = [
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"crossbeam-deque",
"crossbeam-utils",
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 15:47:30 +02:00
]
Bump tempfile from 3.4.0 to 3.5.0 (#8719) Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.4.0 to 3.5.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Stebalien/tempfile/blob/master/NEWS">tempfile's changelog</a>.</em></p> <blockquote> <h1>3.5.0</h1> <ul> <li>Update rustix from 0.36 to 0.37.1. This makes wasi work on rust stable</li> <li>Update <code>windows-sys</code>, <code>redox_syscall</code></li> <li>BREAKING: Remove the implementation of <code>Write for &amp;NamedTempFile&lt;F&gt; where &amp;F: Write</code>. Unfortunately, this can cause compile issues in unrelated code (<a href="https://redirect.github.com/Stebalien/tempfile/issues/224">Stebalien/tempfile#224</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/Stebalien/tempfile/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tempfile&package-manager=cargo&previous-version=3.4.0&new-version=3.5.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-06 22:39:31 +02:00
[[package]]
name = "redox_syscall"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.4.1"
Bump tempfile from 3.4.0 to 3.5.0 (#8719) Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.4.0 to 3.5.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Stebalien/tempfile/blob/master/NEWS">tempfile's changelog</a>.</em></p> <blockquote> <h1>3.5.0</h1> <ul> <li>Update rustix from 0.36 to 0.37.1. This makes wasi work on rust stable</li> <li>Update <code>windows-sys</code>, <code>redox_syscall</code></li> <li>BREAKING: Remove the implementation of <code>Write for &amp;NamedTempFile&lt;F&gt; where &amp;F: Write</code>. Unfortunately, this can cause compile issues in unrelated code (<a href="https://redirect.github.com/Stebalien/tempfile/issues/224">Stebalien/tempfile#224</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/Stebalien/tempfile/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tempfile&package-manager=cargo&previous-version=3.4.0&new-version=3.5.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-06 22:39:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "4722d768eff46b75989dd134e5c353f0d6296e5aaa3132e776cbdb56be7731aa"
Bump tempfile from 3.4.0 to 3.5.0 (#8719) Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.4.0 to 3.5.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Stebalien/tempfile/blob/master/NEWS">tempfile's changelog</a>.</em></p> <blockquote> <h1>3.5.0</h1> <ul> <li>Update rustix from 0.36 to 0.37.1. This makes wasi work on rust stable</li> <li>Update <code>windows-sys</code>, <code>redox_syscall</code></li> <li>BREAKING: Remove the implementation of <code>Write for &amp;NamedTempFile&lt;F&gt; where &amp;F: Write</code>. Unfortunately, this can cause compile issues in unrelated code (<a href="https://redirect.github.com/Stebalien/tempfile/issues/224">Stebalien/tempfile#224</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/Stebalien/tempfile/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tempfile&package-manager=cargo&previous-version=3.4.0&new-version=3.5.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-06 22:39:31 +02:00
dependencies = [
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
"bitflags 1.3.2",
Bump tempfile from 3.4.0 to 3.5.0 (#8719) Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.4.0 to 3.5.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Stebalien/tempfile/blob/master/NEWS">tempfile's changelog</a>.</em></p> <blockquote> <h1>3.5.0</h1> <ul> <li>Update rustix from 0.36 to 0.37.1. This makes wasi work on rust stable</li> <li>Update <code>windows-sys</code>, <code>redox_syscall</code></li> <li>BREAKING: Remove the implementation of <code>Write for &amp;NamedTempFile&lt;F&gt; where &amp;F: Write</code>. Unfortunately, this can cause compile issues in unrelated code (<a href="https://redirect.github.com/Stebalien/tempfile/issues/224">Stebalien/tempfile#224</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/Stebalien/tempfile/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tempfile&package-manager=cargo&previous-version=3.4.0&new-version=3.5.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-06 22:39:31 +02:00
]
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
[[package]]
name = "redox_users"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.4.4"
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "a18479200779601e498ada4e8c1e1f50e3ee19deb0259c25825a98b5603b2cb4"
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
dependencies = [
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"getrandom",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"libredox",
Help menu (#4992) * nu-completer with suggestions * help menu with scrolling * updates description rows based on space * configuration for help menu * update nu-ansi-term * corrected test for update cells * changed keybinding
2022-03-27 15:01:04 +02:00
"thiserror",
Add 'from json'
2021-10-01 07:11:49 +02:00
]
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
[[package]]
name = "reedline"
Properly update to the reedline repo patch (#11342) Follow up to #11339
2023-12-15 20:16:36 +01:00
version = "0.27.1"
Revert "Bump reedline development version" (#11425) Reverts nushell/nushell#11406 This PR https://github.com/nushell/reedline/pull/688 is causing clear screens to happen at strange times. Documented here https://github.com/nushell/nushell/pull/11406#issuecomment-1869591405
2023-12-26 16:08:32 +01:00
source = "git+https://github.com/nushell/reedline.git?branch=main#a4bfaa512be8b7214b80c63327930155da86978a"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
dependencies = [
"chrono",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"crossterm",
Update reedline to race-condition-free history (#955)
2022-02-06 01:16:21 +01:00
"fd-lock",
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 02:22:25 +02:00
"itertools 0.10.5",
Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787) # Description Now use `nu-ansi-term` 0.49 Small adjustments to accommodate breaking changes. # User-Facing Changes None
2023-07-24 13:16:18 +02:00
"nu-ansi-term",
SQLite History MVP with timestamp, duration, working directory, exit status metadata (#5721) This PR adds support for an SQLite history via nushell/reedline#401 The SQLite history is enabled by setting history_file_format: "sqlite" in config.nu. * somewhat working sqlite history * Hook up history command * Fix error in SQlitebacked with empty lines When entering an empty line there previously was the "No command run" error with `SqliteBackedHistory` during addition of the metadata May be considered a temporary fix Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2022-06-14 22:53:33 +02:00
"rusqlite",
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
"serde",
SQLite History MVP with timestamp, duration, working directory, exit status metadata (#5721) This PR adds support for an SQLite history via nushell/reedline#401 The SQLite history is enabled by setting history_file_format: "sqlite" in config.nu. * somewhat working sqlite history * Hook up history command * Fix error in SQlitebacked with empty lines When entering an empty line there previously was the "No command run" error with `SqliteBackedHistory` during addition of the metadata May be considered a temporary fix Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2022-06-14 22:53:33 +02:00
"serde_json",
update to latest reedline, change config point name, enable output without ansi (#458)
2021-12-09 23:06:26 +01:00
"strip-ansi-escapes",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"strum",
"strum_macros",
SQLite History MVP with timestamp, duration, working directory, exit status metadata (#5721) This PR adds support for an SQLite history via nushell/reedline#401 The SQLite history is enabled by setting history_file_format: "sqlite" in config.nu. * somewhat working sqlite history * Hook up history command * Fix error in SQlitebacked with empty lines When entering an empty line there previously was the "No command run" error with `SqliteBackedHistory` during addition of the metadata May be considered a temporary fix Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2022-06-14 22:53:33 +02:00
"thiserror",
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
"unicode-segmentation",
"unicode-width",
Replace dirs and directories with maintained (#2949)
2021-01-19 21:24:27 +01:00
]
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "ref-cast"
version = "1.0.20"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "acde58d073e9c79da00f2b5b84eed919c8326832648a5b109b3fce1bb1175280"
dependencies = [
"ref-cast-impl",
]
[[package]]
name = "ref-cast-impl"
version = "1.0.20"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7f7473c2cfcf90008193dd0e3e16599455cb601a9fce322b5bb55de799664925"
dependencies = [
"proc-macro2",
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "regex"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "1.10.2"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "380b951a9c5e80ddfd6136919eef32310721aa4aacd4889a8d39124b026ab343"
objectshell initial commit
2019-05-10 18:59:12 +02:00
dependencies = [
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"aho-corasick",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"memchr",
Revert "Bump regex from 1.9.6 to 1.10.2" (#10818) Reverts nushell/nushell#10812 This goes back to a version of `regex` and its dependencies that is shared with a lot of our other dependencies. Before this we did not duplicate big dependencies of `regex` that affect binary size and compile time. As there is no known bug or security problem we suffer from, we can wait on receiving the performance improvements to `regex` with the rest of our `regex` dependents.
2023-10-23 16:11:32 +02:00
"regex-automata",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"regex-syntax",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
[[package]]
name = "regex-automata"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.4.3"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "5f804c7828047e88b2d32e2d7fe5a105da8ee3264f01902f796c8e067dc2483f"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
dependencies = [
"aho-corasick",
"memchr",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"regex-syntax",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
]
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
[[package]]
name = "regex-syntax"
version = "0.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c08c74e62047bb2de4ff487b251e4a92e24f48745648451635cec7d591162d9f"
Fix duration type to not report months or years (#9632) <!-- 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! --> This PR should close #8036, #9028 (in the negative) and #9118. Fix for #9118 is a bit pedantic. As reported, the issue is: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 3yr 12month 2day 18hr 9min 33sec ``` with this PR, you now get: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 208wk 1day 18hr 9min 33sec ``` Which is strictly correct, but could still fairly be called "weird date arithmetic". # Description * [x] Abide by constraint that Value::Duration remains a number of nanoseconds with no additional fields. * [x] `to_string()` only displays weeks .. nanoseconds. Duration doesn't have base date to compute months or years from. * [x] `duration | into record` likewise only has fields for weeks .. nanoseconds. * [x] `string | into duration` now accepts compound form of duration to_string() (e.g '2day 3hr`, not just '2day') * [x] `duration | into string` now works (and produces the same representation as to_string(), which may be compound). # User-Facing Changes ## duration -> string -> duration Now you can "round trip" an arbitrary duration value: convert it to a string that may include multiple time units (a "compound" value), then convert that string back into a duration. This required changes to `string | into duration` and the addition of `duration | into string'. ``` > 2day + 3hr 2day 3hr # the "to_string()" representation (in this case, a compound value) > 2day + 3hr | into string 2day 3hr # string value > 2day + 3hr | into string | into duration 2day 3hr # round-trip duration -> string -> duration ``` Note that `to nuon` and `from nuon` already round-tripped durations, but use a different string representation. ## potentially breaking changes * string rendering of a duration no longer has 'yr' or 'month' phrases. * record from `duration | into record` no longer has 'year' or 'month' fields. The excess duration is all lumped into the `week` field, which is the largest time unit you can convert to without knowing the datetime from which the duration was calculated. Scripts that depended on month or year time units on output will need to be changed. ### Examples ``` > 365day 52wk 1day ## Used to be: ## 1yr > 365day | into record ╭──────┬────╮ │ week │ 52 │ │ day │ 1 │ │ sign │ + │ ╰──────┴────╯ ## used to be: ##╭──────┬───╮ ##│ year │ 1 │ ##│ sign │ + │ ##╰──────┴───╯ > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) 56wk 6day 6hr 7min 8sec 9ms 10µs 11ns ## used to be: ## 1yr 1month 3day 6hr 7min 8sec 9ms 10µs 11ns ## which looks reasonable, but was actually only correct in 75% of the years and 25% of the months in the last 4 years. > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) | into record ╭─────────────┬────╮ │ week │ 56 │ │ day │ 6 │ │ hour │ 6 │ │ minute │ 7 │ │ second │ 8 │ │ millisecond │ 9 │ │ microsecond │ 10 │ │ nanosecond │ 11 │ │ sign │ + │ ╰─────────────┴────╯ ``` Strictly speaking, these changes could break an existing user script. Losing years and months as time units is arguably a regression in behavior. Also, the corrected duration calculation could break an existing script that was calibrated using the old algorithm. # Tests + Formatting ``` > toolkit check pr ``` - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib` # 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. --> --------- Co-authored-by: Bob Hyman <bobhy@localhost.localdomain>
2023-08-08 13:24:09 +02:00
[[package]]
name = "relative-path"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.9.0"
Fix duration type to not report months or years (#9632) <!-- 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! --> This PR should close #8036, #9028 (in the negative) and #9118. Fix for #9118 is a bit pedantic. As reported, the issue is: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 3yr 12month 2day 18hr 9min 33sec ``` with this PR, you now get: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 208wk 1day 18hr 9min 33sec ``` Which is strictly correct, but could still fairly be called "weird date arithmetic". # Description * [x] Abide by constraint that Value::Duration remains a number of nanoseconds with no additional fields. * [x] `to_string()` only displays weeks .. nanoseconds. Duration doesn't have base date to compute months or years from. * [x] `duration | into record` likewise only has fields for weeks .. nanoseconds. * [x] `string | into duration` now accepts compound form of duration to_string() (e.g '2day 3hr`, not just '2day') * [x] `duration | into string` now works (and produces the same representation as to_string(), which may be compound). # User-Facing Changes ## duration -> string -> duration Now you can "round trip" an arbitrary duration value: convert it to a string that may include multiple time units (a "compound" value), then convert that string back into a duration. This required changes to `string | into duration` and the addition of `duration | into string'. ``` > 2day + 3hr 2day 3hr # the "to_string()" representation (in this case, a compound value) > 2day + 3hr | into string 2day 3hr # string value > 2day + 3hr | into string | into duration 2day 3hr # round-trip duration -> string -> duration ``` Note that `to nuon` and `from nuon` already round-tripped durations, but use a different string representation. ## potentially breaking changes * string rendering of a duration no longer has 'yr' or 'month' phrases. * record from `duration | into record` no longer has 'year' or 'month' fields. The excess duration is all lumped into the `week` field, which is the largest time unit you can convert to without knowing the datetime from which the duration was calculated. Scripts that depended on month or year time units on output will need to be changed. ### Examples ``` > 365day 52wk 1day ## Used to be: ## 1yr > 365day | into record ╭──────┬────╮ │ week │ 52 │ │ day │ 1 │ │ sign │ + │ ╰──────┴────╯ ## used to be: ##╭──────┬───╮ ##│ year │ 1 │ ##│ sign │ + │ ##╰──────┴───╯ > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) 56wk 6day 6hr 7min 8sec 9ms 10µs 11ns ## used to be: ## 1yr 1month 3day 6hr 7min 8sec 9ms 10µs 11ns ## which looks reasonable, but was actually only correct in 75% of the years and 25% of the months in the last 4 years. > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) | into record ╭─────────────┬────╮ │ week │ 56 │ │ day │ 6 │ │ hour │ 6 │ │ minute │ 7 │ │ second │ 8 │ │ millisecond │ 9 │ │ microsecond │ 10 │ │ nanosecond │ 11 │ │ sign │ + │ ╰─────────────┴────╯ ``` Strictly speaking, these changes could break an existing user script. Losing years and months as time units is arguably a regression in behavior. Also, the corrected duration calculation could break an existing script that was calibrated using the old algorithm. # Tests + Formatting ``` > toolkit check pr ``` - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib` # 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. --> --------- Co-authored-by: Bob Hyman <bobhy@localhost.localdomain>
2023-08-08 13:24:09 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "c707298afce11da2efef2f600116fa93ffa7a032b5d7b628aa17711ec81383ca"
Fix duration type to not report months or years (#9632) <!-- 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! --> This PR should close #8036, #9028 (in the negative) and #9118. Fix for #9118 is a bit pedantic. As reported, the issue is: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 3yr 12month 2day 18hr 9min 33sec ``` with this PR, you now get: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 208wk 1day 18hr 9min 33sec ``` Which is strictly correct, but could still fairly be called "weird date arithmetic". # Description * [x] Abide by constraint that Value::Duration remains a number of nanoseconds with no additional fields. * [x] `to_string()` only displays weeks .. nanoseconds. Duration doesn't have base date to compute months or years from. * [x] `duration | into record` likewise only has fields for weeks .. nanoseconds. * [x] `string | into duration` now accepts compound form of duration to_string() (e.g '2day 3hr`, not just '2day') * [x] `duration | into string` now works (and produces the same representation as to_string(), which may be compound). # User-Facing Changes ## duration -> string -> duration Now you can "round trip" an arbitrary duration value: convert it to a string that may include multiple time units (a "compound" value), then convert that string back into a duration. This required changes to `string | into duration` and the addition of `duration | into string'. ``` > 2day + 3hr 2day 3hr # the "to_string()" representation (in this case, a compound value) > 2day + 3hr | into string 2day 3hr # string value > 2day + 3hr | into string | into duration 2day 3hr # round-trip duration -> string -> duration ``` Note that `to nuon` and `from nuon` already round-tripped durations, but use a different string representation. ## potentially breaking changes * string rendering of a duration no longer has 'yr' or 'month' phrases. * record from `duration | into record` no longer has 'year' or 'month' fields. The excess duration is all lumped into the `week` field, which is the largest time unit you can convert to without knowing the datetime from which the duration was calculated. Scripts that depended on month or year time units on output will need to be changed. ### Examples ``` > 365day 52wk 1day ## Used to be: ## 1yr > 365day | into record ╭──────┬────╮ │ week │ 52 │ │ day │ 1 │ │ sign │ + │ ╰──────┴────╯ ## used to be: ##╭──────┬───╮ ##│ year │ 1 │ ##│ sign │ + │ ##╰──────┴───╯ > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) 56wk 6day 6hr 7min 8sec 9ms 10µs 11ns ## used to be: ## 1yr 1month 3day 6hr 7min 8sec 9ms 10µs 11ns ## which looks reasonable, but was actually only correct in 75% of the years and 25% of the months in the last 4 years. > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) | into record ╭─────────────┬────╮ │ week │ 56 │ │ day │ 6 │ │ hour │ 6 │ │ minute │ 7 │ │ second │ 8 │ │ millisecond │ 9 │ │ microsecond │ 10 │ │ nanosecond │ 11 │ │ sign │ + │ ╰─────────────┴────╯ ``` Strictly speaking, these changes could break an existing user script. Losing years and months as time units is arguably a regression in behavior. Also, the corrected duration calculation could break an existing script that was calibrated using the old algorithm. # Tests + Formatting ``` > toolkit check pr ``` - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib` # 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. --> --------- Co-authored-by: Bob Hyman <bobhy@localhost.localdomain>
2023-08-08 13:24:09 +02:00
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "rfc2047-decoder"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4da9a46587af867184f5e2f5dd2eb0e32f76054f11e890760c0f5a6130abf7e3"
dependencies = [
"base64 0.21.5",
"charset",
"chumsky",
"memchr",
"quoted_printable",
"thiserror",
]
Expose polars avro support (#10019) # Description Exposes polars avro support via dfr open and dfr to-avro --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-08-16 03:31:49 +02:00
[[package]]
name = "rle-decode-fast"
version = "1.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3582f63211428f83597b51b2ddb88e2a91a9d52d12831f9d08f5e624e8977422"
add MessagePack as a plugin protocol (#6370)
2022-08-21 13:13:38 +02:00
[[package]]
name = "rmp"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.8.12"
add MessagePack as a plugin protocol (#6370)
2022-08-21 13:13:38 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "7f9860a6cc38ed1da53456442089b4dfa35e7cedaa326df63017af88385e6b20"
add MessagePack as a plugin protocol (#6370)
2022-08-21 13:13:38 +02:00
dependencies = [
"byteorder",
"num-traits",
"paste",
]
[[package]]
name = "rmp-serde"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.1.2"
add MessagePack as a plugin protocol (#6370)
2022-08-21 13:13:38 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "bffea85eea980d8a74453e5d02a8d93028f3c34725de143085a844ebe953258a"
add MessagePack as a plugin protocol (#6370)
2022-08-21 13:13:38 +02:00
dependencies = [
"byteorder",
"rmp",
"serde",
]
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
[[package]]
name = "ropey"
version = "1.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "93411e420bcd1a75ddd1dc3caf18c23155eda2c090631a85af21ba19e97093b5"
dependencies = [
"smallvec",
"str_indices",
]
Add xml open support
2019-06-11 08:26:03 +02:00
[[package]]
name = "roxmltree"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.18.1"
Add xml open support
2019-06-11 08:26:03 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "862340e351ce1b271a378ec53f304a5558f7db87f3769dc655a8f6ecbb68b302"
Add xml open support
2019-06-11 08:26:03 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"xmlparser",
Add xml open support
2019-06-11 08:26:03 +02:00
]
Fix duration type to not report months or years (#9632) <!-- 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! --> This PR should close #8036, #9028 (in the negative) and #9118. Fix for #9118 is a bit pedantic. As reported, the issue is: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 3yr 12month 2day 18hr 9min 33sec ``` with this PR, you now get: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 208wk 1day 18hr 9min 33sec ``` Which is strictly correct, but could still fairly be called "weird date arithmetic". # Description * [x] Abide by constraint that Value::Duration remains a number of nanoseconds with no additional fields. * [x] `to_string()` only displays weeks .. nanoseconds. Duration doesn't have base date to compute months or years from. * [x] `duration | into record` likewise only has fields for weeks .. nanoseconds. * [x] `string | into duration` now accepts compound form of duration to_string() (e.g '2day 3hr`, not just '2day') * [x] `duration | into string` now works (and produces the same representation as to_string(), which may be compound). # User-Facing Changes ## duration -> string -> duration Now you can "round trip" an arbitrary duration value: convert it to a string that may include multiple time units (a "compound" value), then convert that string back into a duration. This required changes to `string | into duration` and the addition of `duration | into string'. ``` > 2day + 3hr 2day 3hr # the "to_string()" representation (in this case, a compound value) > 2day + 3hr | into string 2day 3hr # string value > 2day + 3hr | into string | into duration 2day 3hr # round-trip duration -> string -> duration ``` Note that `to nuon` and `from nuon` already round-tripped durations, but use a different string representation. ## potentially breaking changes * string rendering of a duration no longer has 'yr' or 'month' phrases. * record from `duration | into record` no longer has 'year' or 'month' fields. The excess duration is all lumped into the `week` field, which is the largest time unit you can convert to without knowing the datetime from which the duration was calculated. Scripts that depended on month or year time units on output will need to be changed. ### Examples ``` > 365day 52wk 1day ## Used to be: ## 1yr > 365day | into record ╭──────┬────╮ │ week │ 52 │ │ day │ 1 │ │ sign │ + │ ╰──────┴────╯ ## used to be: ##╭──────┬───╮ ##│ year │ 1 │ ##│ sign │ + │ ##╰──────┴───╯ > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) 56wk 6day 6hr 7min 8sec 9ms 10µs 11ns ## used to be: ## 1yr 1month 3day 6hr 7min 8sec 9ms 10µs 11ns ## which looks reasonable, but was actually only correct in 75% of the years and 25% of the months in the last 4 years. > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) | into record ╭─────────────┬────╮ │ week │ 56 │ │ day │ 6 │ │ hour │ 6 │ │ minute │ 7 │ │ second │ 8 │ │ millisecond │ 9 │ │ microsecond │ 10 │ │ nanosecond │ 11 │ │ sign │ + │ ╰─────────────┴────╯ ``` Strictly speaking, these changes could break an existing user script. Losing years and months as time units is arguably a regression in behavior. Also, the corrected duration calculation could break an existing script that was calibrated using the old algorithm. # Tests + Formatting ``` > toolkit check pr ``` - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib` # 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. --> --------- Co-authored-by: Bob Hyman <bobhy@localhost.localdomain>
2023-08-08 13:24:09 +02:00
[[package]]
name = "rstest"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.18.2"
Fix duration type to not report months or years (#9632) <!-- 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! --> This PR should close #8036, #9028 (in the negative) and #9118. Fix for #9118 is a bit pedantic. As reported, the issue is: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 3yr 12month 2day 18hr 9min 33sec ``` with this PR, you now get: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 208wk 1day 18hr 9min 33sec ``` Which is strictly correct, but could still fairly be called "weird date arithmetic". # Description * [x] Abide by constraint that Value::Duration remains a number of nanoseconds with no additional fields. * [x] `to_string()` only displays weeks .. nanoseconds. Duration doesn't have base date to compute months or years from. * [x] `duration | into record` likewise only has fields for weeks .. nanoseconds. * [x] `string | into duration` now accepts compound form of duration to_string() (e.g '2day 3hr`, not just '2day') * [x] `duration | into string` now works (and produces the same representation as to_string(), which may be compound). # User-Facing Changes ## duration -> string -> duration Now you can "round trip" an arbitrary duration value: convert it to a string that may include multiple time units (a "compound" value), then convert that string back into a duration. This required changes to `string | into duration` and the addition of `duration | into string'. ``` > 2day + 3hr 2day 3hr # the "to_string()" representation (in this case, a compound value) > 2day + 3hr | into string 2day 3hr # string value > 2day + 3hr | into string | into duration 2day 3hr # round-trip duration -> string -> duration ``` Note that `to nuon` and `from nuon` already round-tripped durations, but use a different string representation. ## potentially breaking changes * string rendering of a duration no longer has 'yr' or 'month' phrases. * record from `duration | into record` no longer has 'year' or 'month' fields. The excess duration is all lumped into the `week` field, which is the largest time unit you can convert to without knowing the datetime from which the duration was calculated. Scripts that depended on month or year time units on output will need to be changed. ### Examples ``` > 365day 52wk 1day ## Used to be: ## 1yr > 365day | into record ╭──────┬────╮ │ week │ 52 │ │ day │ 1 │ │ sign │ + │ ╰──────┴────╯ ## used to be: ##╭──────┬───╮ ##│ year │ 1 │ ##│ sign │ + │ ##╰──────┴───╯ > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) 56wk 6day 6hr 7min 8sec 9ms 10µs 11ns ## used to be: ## 1yr 1month 3day 6hr 7min 8sec 9ms 10µs 11ns ## which looks reasonable, but was actually only correct in 75% of the years and 25% of the months in the last 4 years. > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) | into record ╭─────────────┬────╮ │ week │ 56 │ │ day │ 6 │ │ hour │ 6 │ │ minute │ 7 │ │ second │ 8 │ │ millisecond │ 9 │ │ microsecond │ 10 │ │ nanosecond │ 11 │ │ sign │ + │ ╰─────────────┴────╯ ``` Strictly speaking, these changes could break an existing user script. Losing years and months as time units is arguably a regression in behavior. Also, the corrected duration calculation could break an existing script that was calibrated using the old algorithm. # Tests + Formatting ``` > toolkit check pr ``` - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib` # 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. --> --------- Co-authored-by: Bob Hyman <bobhy@localhost.localdomain>
2023-08-08 13:24:09 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "97eeab2f3c0a199bc4be135c36c924b6590b88c377d416494288c14f2db30199"
Fix duration type to not report months or years (#9632) <!-- 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! --> This PR should close #8036, #9028 (in the negative) and #9118. Fix for #9118 is a bit pedantic. As reported, the issue is: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 3yr 12month 2day 18hr 9min 33sec ``` with this PR, you now get: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 208wk 1day 18hr 9min 33sec ``` Which is strictly correct, but could still fairly be called "weird date arithmetic". # Description * [x] Abide by constraint that Value::Duration remains a number of nanoseconds with no additional fields. * [x] `to_string()` only displays weeks .. nanoseconds. Duration doesn't have base date to compute months or years from. * [x] `duration | into record` likewise only has fields for weeks .. nanoseconds. * [x] `string | into duration` now accepts compound form of duration to_string() (e.g '2day 3hr`, not just '2day') * [x] `duration | into string` now works (and produces the same representation as to_string(), which may be compound). # User-Facing Changes ## duration -> string -> duration Now you can "round trip" an arbitrary duration value: convert it to a string that may include multiple time units (a "compound" value), then convert that string back into a duration. This required changes to `string | into duration` and the addition of `duration | into string'. ``` > 2day + 3hr 2day 3hr # the "to_string()" representation (in this case, a compound value) > 2day + 3hr | into string 2day 3hr # string value > 2day + 3hr | into string | into duration 2day 3hr # round-trip duration -> string -> duration ``` Note that `to nuon` and `from nuon` already round-tripped durations, but use a different string representation. ## potentially breaking changes * string rendering of a duration no longer has 'yr' or 'month' phrases. * record from `duration | into record` no longer has 'year' or 'month' fields. The excess duration is all lumped into the `week` field, which is the largest time unit you can convert to without knowing the datetime from which the duration was calculated. Scripts that depended on month or year time units on output will need to be changed. ### Examples ``` > 365day 52wk 1day ## Used to be: ## 1yr > 365day | into record ╭──────┬────╮ │ week │ 52 │ │ day │ 1 │ │ sign │ + │ ╰──────┴────╯ ## used to be: ##╭──────┬───╮ ##│ year │ 1 │ ##│ sign │ + │ ##╰──────┴───╯ > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) 56wk 6day 6hr 7min 8sec 9ms 10µs 11ns ## used to be: ## 1yr 1month 3day 6hr 7min 8sec 9ms 10µs 11ns ## which looks reasonable, but was actually only correct in 75% of the years and 25% of the months in the last 4 years. > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) | into record ╭─────────────┬────╮ │ week │ 56 │ │ day │ 6 │ │ hour │ 6 │ │ minute │ 7 │ │ second │ 8 │ │ millisecond │ 9 │ │ microsecond │ 10 │ │ nanosecond │ 11 │ │ sign │ + │ ╰─────────────┴────╯ ``` Strictly speaking, these changes could break an existing user script. Losing years and months as time units is arguably a regression in behavior. Also, the corrected duration calculation could break an existing script that was calibrated using the old algorithm. # Tests + Formatting ``` > toolkit check pr ``` - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib` # 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. --> --------- Co-authored-by: Bob Hyman <bobhy@localhost.localdomain>
2023-08-08 13:24:09 +02:00
dependencies = [
"futures",
"futures-timer",
Bump rstest from 0.17.0 to 0.18.1 (#9782)
2023-08-08 19:11:05 +02:00
"rstest_macros",
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
"rustc_version",
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
]
Fix duration type to not report months or years (#9632) <!-- 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! --> This PR should close #8036, #9028 (in the negative) and #9118. Fix for #9118 is a bit pedantic. As reported, the issue is: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 3yr 12month 2day 18hr 9min 33sec ``` with this PR, you now get: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 208wk 1day 18hr 9min 33sec ``` Which is strictly correct, but could still fairly be called "weird date arithmetic". # Description * [x] Abide by constraint that Value::Duration remains a number of nanoseconds with no additional fields. * [x] `to_string()` only displays weeks .. nanoseconds. Duration doesn't have base date to compute months or years from. * [x] `duration | into record` likewise only has fields for weeks .. nanoseconds. * [x] `string | into duration` now accepts compound form of duration to_string() (e.g '2day 3hr`, not just '2day') * [x] `duration | into string` now works (and produces the same representation as to_string(), which may be compound). # User-Facing Changes ## duration -> string -> duration Now you can "round trip" an arbitrary duration value: convert it to a string that may include multiple time units (a "compound" value), then convert that string back into a duration. This required changes to `string | into duration` and the addition of `duration | into string'. ``` > 2day + 3hr 2day 3hr # the "to_string()" representation (in this case, a compound value) > 2day + 3hr | into string 2day 3hr # string value > 2day + 3hr | into string | into duration 2day 3hr # round-trip duration -> string -> duration ``` Note that `to nuon` and `from nuon` already round-tripped durations, but use a different string representation. ## potentially breaking changes * string rendering of a duration no longer has 'yr' or 'month' phrases. * record from `duration | into record` no longer has 'year' or 'month' fields. The excess duration is all lumped into the `week` field, which is the largest time unit you can convert to without knowing the datetime from which the duration was calculated. Scripts that depended on month or year time units on output will need to be changed. ### Examples ``` > 365day 52wk 1day ## Used to be: ## 1yr > 365day | into record ╭──────┬────╮ │ week │ 52 │ │ day │ 1 │ │ sign │ + │ ╰──────┴────╯ ## used to be: ##╭──────┬───╮ ##│ year │ 1 │ ##│ sign │ + │ ##╰──────┴───╯ > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) 56wk 6day 6hr 7min 8sec 9ms 10µs 11ns ## used to be: ## 1yr 1month 3day 6hr 7min 8sec 9ms 10µs 11ns ## which looks reasonable, but was actually only correct in 75% of the years and 25% of the months in the last 4 years. > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) | into record ╭─────────────┬────╮ │ week │ 56 │ │ day │ 6 │ │ hour │ 6 │ │ minute │ 7 │ │ second │ 8 │ │ millisecond │ 9 │ │ microsecond │ 10 │ │ nanosecond │ 11 │ │ sign │ + │ ╰─────────────┴────╯ ``` Strictly speaking, these changes could break an existing user script. Losing years and months as time units is arguably a regression in behavior. Also, the corrected duration calculation could break an existing script that was calibrated using the old algorithm. # Tests + Formatting ``` > toolkit check pr ``` - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib` # 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. --> --------- Co-authored-by: Bob Hyman <bobhy@localhost.localdomain>
2023-08-08 13:24:09 +02:00
[[package]]
name = "rstest_macros"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.18.2"
Fix duration type to not report months or years (#9632) <!-- 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! --> This PR should close #8036, #9028 (in the negative) and #9118. Fix for #9118 is a bit pedantic. As reported, the issue is: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 3yr 12month 2day 18hr 9min 33sec ``` with this PR, you now get: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 208wk 1day 18hr 9min 33sec ``` Which is strictly correct, but could still fairly be called "weird date arithmetic". # Description * [x] Abide by constraint that Value::Duration remains a number of nanoseconds with no additional fields. * [x] `to_string()` only displays weeks .. nanoseconds. Duration doesn't have base date to compute months or years from. * [x] `duration | into record` likewise only has fields for weeks .. nanoseconds. * [x] `string | into duration` now accepts compound form of duration to_string() (e.g '2day 3hr`, not just '2day') * [x] `duration | into string` now works (and produces the same representation as to_string(), which may be compound). # User-Facing Changes ## duration -> string -> duration Now you can "round trip" an arbitrary duration value: convert it to a string that may include multiple time units (a "compound" value), then convert that string back into a duration. This required changes to `string | into duration` and the addition of `duration | into string'. ``` > 2day + 3hr 2day 3hr # the "to_string()" representation (in this case, a compound value) > 2day + 3hr | into string 2day 3hr # string value > 2day + 3hr | into string | into duration 2day 3hr # round-trip duration -> string -> duration ``` Note that `to nuon` and `from nuon` already round-tripped durations, but use a different string representation. ## potentially breaking changes * string rendering of a duration no longer has 'yr' or 'month' phrases. * record from `duration | into record` no longer has 'year' or 'month' fields. The excess duration is all lumped into the `week` field, which is the largest time unit you can convert to without knowing the datetime from which the duration was calculated. Scripts that depended on month or year time units on output will need to be changed. ### Examples ``` > 365day 52wk 1day ## Used to be: ## 1yr > 365day | into record ╭──────┬────╮ │ week │ 52 │ │ day │ 1 │ │ sign │ + │ ╰──────┴────╯ ## used to be: ##╭──────┬───╮ ##│ year │ 1 │ ##│ sign │ + │ ##╰──────┴───╯ > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) 56wk 6day 6hr 7min 8sec 9ms 10µs 11ns ## used to be: ## 1yr 1month 3day 6hr 7min 8sec 9ms 10µs 11ns ## which looks reasonable, but was actually only correct in 75% of the years and 25% of the months in the last 4 years. > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) | into record ╭─────────────┬────╮ │ week │ 56 │ │ day │ 6 │ │ hour │ 6 │ │ minute │ 7 │ │ second │ 8 │ │ millisecond │ 9 │ │ microsecond │ 10 │ │ nanosecond │ 11 │ │ sign │ + │ ╰─────────────┴────╯ ``` Strictly speaking, these changes could break an existing user script. Losing years and months as time units is arguably a regression in behavior. Also, the corrected duration calculation could break an existing script that was calibrated using the old algorithm. # Tests + Formatting ``` > toolkit check pr ``` - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib` # 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. --> --------- Co-authored-by: Bob Hyman <bobhy@localhost.localdomain>
2023-08-08 13:24:09 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "d428f8247852f894ee1be110b375111b586d4fa431f6c46e64ba5a0dcccbe605"
Fix duration type to not report months or years (#9632) <!-- 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! --> This PR should close #8036, #9028 (in the negative) and #9118. Fix for #9118 is a bit pedantic. As reported, the issue is: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 3yr 12month 2day 18hr 9min 33sec ``` with this PR, you now get: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 208wk 1day 18hr 9min 33sec ``` Which is strictly correct, but could still fairly be called "weird date arithmetic". # Description * [x] Abide by constraint that Value::Duration remains a number of nanoseconds with no additional fields. * [x] `to_string()` only displays weeks .. nanoseconds. Duration doesn't have base date to compute months or years from. * [x] `duration | into record` likewise only has fields for weeks .. nanoseconds. * [x] `string | into duration` now accepts compound form of duration to_string() (e.g '2day 3hr`, not just '2day') * [x] `duration | into string` now works (and produces the same representation as to_string(), which may be compound). # User-Facing Changes ## duration -> string -> duration Now you can "round trip" an arbitrary duration value: convert it to a string that may include multiple time units (a "compound" value), then convert that string back into a duration. This required changes to `string | into duration` and the addition of `duration | into string'. ``` > 2day + 3hr 2day 3hr # the "to_string()" representation (in this case, a compound value) > 2day + 3hr | into string 2day 3hr # string value > 2day + 3hr | into string | into duration 2day 3hr # round-trip duration -> string -> duration ``` Note that `to nuon` and `from nuon` already round-tripped durations, but use a different string representation. ## potentially breaking changes * string rendering of a duration no longer has 'yr' or 'month' phrases. * record from `duration | into record` no longer has 'year' or 'month' fields. The excess duration is all lumped into the `week` field, which is the largest time unit you can convert to without knowing the datetime from which the duration was calculated. Scripts that depended on month or year time units on output will need to be changed. ### Examples ``` > 365day 52wk 1day ## Used to be: ## 1yr > 365day | into record ╭──────┬────╮ │ week │ 52 │ │ day │ 1 │ │ sign │ + │ ╰──────┴────╯ ## used to be: ##╭──────┬───╮ ##│ year │ 1 │ ##│ sign │ + │ ##╰──────┴───╯ > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) 56wk 6day 6hr 7min 8sec 9ms 10µs 11ns ## used to be: ## 1yr 1month 3day 6hr 7min 8sec 9ms 10µs 11ns ## which looks reasonable, but was actually only correct in 75% of the years and 25% of the months in the last 4 years. > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) | into record ╭─────────────┬────╮ │ week │ 56 │ │ day │ 6 │ │ hour │ 6 │ │ minute │ 7 │ │ second │ 8 │ │ millisecond │ 9 │ │ microsecond │ 10 │ │ nanosecond │ 11 │ │ sign │ + │ ╰─────────────┴────╯ ``` Strictly speaking, these changes could break an existing user script. Losing years and months as time units is arguably a regression in behavior. Also, the corrected duration calculation could break an existing script that was calibrated using the old algorithm. # Tests + Formatting ``` > toolkit check pr ``` - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib` # 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. --> --------- Co-authored-by: Bob Hyman <bobhy@localhost.localdomain>
2023-08-08 13:24:09 +02:00
dependencies = [
"cfg-if",
"glob",
"proc-macro2",
"quote",
"regex",
"relative-path",
"rustc_version",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
Fix duration type to not report months or years (#9632) <!-- 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! --> This PR should close #8036, #9028 (in the negative) and #9118. Fix for #9118 is a bit pedantic. As reported, the issue is: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 3yr 12month 2day 18hr 9min 33sec ``` with this PR, you now get: ``` > 2023-05-07T04:08:45+12:00 - 2019-05-10T09:59:12+12:00 208wk 1day 18hr 9min 33sec ``` Which is strictly correct, but could still fairly be called "weird date arithmetic". # Description * [x] Abide by constraint that Value::Duration remains a number of nanoseconds with no additional fields. * [x] `to_string()` only displays weeks .. nanoseconds. Duration doesn't have base date to compute months or years from. * [x] `duration | into record` likewise only has fields for weeks .. nanoseconds. * [x] `string | into duration` now accepts compound form of duration to_string() (e.g '2day 3hr`, not just '2day') * [x] `duration | into string` now works (and produces the same representation as to_string(), which may be compound). # User-Facing Changes ## duration -> string -> duration Now you can "round trip" an arbitrary duration value: convert it to a string that may include multiple time units (a "compound" value), then convert that string back into a duration. This required changes to `string | into duration` and the addition of `duration | into string'. ``` > 2day + 3hr 2day 3hr # the "to_string()" representation (in this case, a compound value) > 2day + 3hr | into string 2day 3hr # string value > 2day + 3hr | into string | into duration 2day 3hr # round-trip duration -> string -> duration ``` Note that `to nuon` and `from nuon` already round-tripped durations, but use a different string representation. ## potentially breaking changes * string rendering of a duration no longer has 'yr' or 'month' phrases. * record from `duration | into record` no longer has 'year' or 'month' fields. The excess duration is all lumped into the `week` field, which is the largest time unit you can convert to without knowing the datetime from which the duration was calculated. Scripts that depended on month or year time units on output will need to be changed. ### Examples ``` > 365day 52wk 1day ## Used to be: ## 1yr > 365day | into record ╭──────┬────╮ │ week │ 52 │ │ day │ 1 │ │ sign │ + │ ╰──────┴────╯ ## used to be: ##╭──────┬───╮ ##│ year │ 1 │ ##│ sign │ + │ ##╰──────┴───╯ > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) 56wk 6day 6hr 7min 8sec 9ms 10µs 11ns ## used to be: ## 1yr 1month 3day 6hr 7min 8sec 9ms 10µs 11ns ## which looks reasonable, but was actually only correct in 75% of the years and 25% of the months in the last 4 years. > (365day + 4wk + 5day + 6hr + 7min + 8sec + 9ms + 10us + 11ns) | into record ╭─────────────┬────╮ │ week │ 56 │ │ day │ 6 │ │ hour │ 6 │ │ minute │ 7 │ │ second │ 8 │ │ millisecond │ 9 │ │ microsecond │ 10 │ │ nanosecond │ 11 │ │ sign │ + │ ╰─────────────┴────╯ ``` Strictly speaking, these changes could break an existing user script. Losing years and months as time units is arguably a regression in behavior. Also, the corrected duration calculation could break an existing script that was calibrated using the old algorithm. # Tests + Formatting ``` > toolkit check pr ``` - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib` # 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. --> --------- Co-authored-by: Bob Hyman <bobhy@localhost.localdomain>
2023-08-08 13:24:09 +02:00
"unicode-ident",
]
Initial SQLite functionality (#5182) * Add SQLite functionality to open * Add in-memory SQLite tests * clippy fixes * Fix up old SQLite-related tests
2022-04-14 05:15:02 +02:00
[[package]]
name = "rusqlite"
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
version = "0.29.0"
Initial SQLite functionality (#5182) * Add SQLite functionality to open * Add in-memory SQLite tests * clippy fixes * Fix up old SQLite-related tests
2022-04-14 05:15:02 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
checksum = "549b9d036d571d42e6e85d1c1425e2ac83491075078ca9a15be021c56b1641f2"
Initial SQLite functionality (#5182) * Add SQLite functionality to open * Add in-memory SQLite tests * clippy fixes * Fix up old SQLite-related tests
2022-04-14 05:15:02 +02:00
dependencies = [
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"bitflags 2.4.1",
Initial SQLite functionality (#5182) * Add SQLite functionality to open * Add in-memory SQLite tests * clippy fixes * Fix up old SQLite-related tests
2022-04-14 05:15:02 +02:00
"fallible-iterator",
"fallible-streaming-iterator",
"hashlink",
"libsqlite3-sys",
"smallvec",
]
Add 228 json html themes for to html (#2308) * add 228 json html themes removed old assets, added new zipped asset added --list to get a list of the theme names reworked some older theme code added rust-embed and zip crate removed the dark tests * fmt * Updated, removed excess comments Changed usage a bit Updated the error handling Added some helper items in --list
2020-08-10 19:43:16 +02:00
[[package]]
name = "rust-embed"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "8.1.0"
`To html` and `to md` (#453) * MathEval Variance and Stddev * Fix tests and linting * Typo * Deal with streams when they are not tables * First draft of these commands * To MD * To md and to html * Fixed cargo and to_md * `into_abbreviated_string` instead of `into_string` * Changed how inner tables are displayed
2021-12-10 02:16:35 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "810294a8a4a0853d4118e3b94bb079905f2107c7fe979d8f0faae98765eb6378"
Add 228 json html themes for to html (#2308) * add 228 json html themes removed old assets, added new zipped asset added --list to get a list of the theme names reworked some older theme code added rust-embed and zip crate removed the dark tests * fmt * Updated, removed excess comments Changed usage a bit Updated the error handling Added some helper items in --list
2020-08-10 19:43:16 +02:00
dependencies = [
"rust-embed-impl",
"rust-embed-utils",
"walkdir",
]
[[package]]
name = "rust-embed-impl"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "8.1.0"
`To html` and `to md` (#453) * MathEval Variance and Stddev * Fix tests and linting * Typo * Deal with streams when they are not tables * First draft of these commands * To MD * To md and to html * Fixed cargo and to_md * `into_abbreviated_string` instead of `into_string` * Changed how inner tables are displayed
2021-12-10 02:16:35 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "bfc144a1273124a67b8c1d7cd19f5695d1878b31569c0512f6086f0f4676604e"
Add 228 json html themes for to html (#2308) * add 228 json html themes removed old assets, added new zipped asset added --list to get a list of the theme names reworked some older theme code added rust-embed and zip crate removed the dark tests * fmt * Updated, removed excess comments Changed usage a bit Updated the error handling Added some helper items in --list
2020-08-10 19:43:16 +02:00
dependencies = [
Update dependency rust-embed now that issue with its use of syn has been fixed. (#2880) * update the rust-embed dependency of nu-cli to 5.8.0 and undo the version pin of syn now that rust-embed-impl has been fixed * unpin syn version in chart plugin
2021-01-07 02:33:39 +01:00
"proc-macro2",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"quote",
Add 228 json html themes for to html (#2308) * add 228 json html themes removed old assets, added new zipped asset added --list to get a list of the theme names reworked some older theme code added rust-embed and zip crate removed the dark tests * fmt * Updated, removed excess comments Changed usage a bit Updated the error handling Added some helper items in --list
2020-08-10 19:43:16 +02:00
"rust-embed-utils",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
Add 228 json html themes for to html (#2308) * add 228 json html themes removed old assets, added new zipped asset added --list to get a list of the theme names reworked some older theme code added rust-embed and zip crate removed the dark tests * fmt * Updated, removed excess comments Changed usage a bit Updated the error handling Added some helper items in --list
2020-08-10 19:43:16 +02:00
"walkdir",
]
[[package]]
name = "rust-embed-utils"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "8.1.0"
`To html` and `to md` (#453) * MathEval Variance and Stddev * Fix tests and linting * Typo * Deal with streams when they are not tables * First draft of these commands * To MD * To md and to html * Fixed cargo and to_md * `into_abbreviated_string` instead of `into_string` * Changed how inner tables are displayed
2021-12-10 02:16:35 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "816ccd4875431253d6bb54b804bcff4369cbde9bae33defde25fdf6c2ef91d40"
`To html` and `to md` (#453) * MathEval Variance and Stddev * Fix tests and linting * Typo * Deal with streams when they are not tables * First draft of these commands * To MD * To md and to html * Fixed cargo and to_md * `into_abbreviated_string` instead of `into_string` * Changed how inner tables are displayed
2021-12-10 02:16:35 +01:00
dependencies = [
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
"sha2",
Add 228 json html themes for to html (#2308) * add 228 json html themes removed old assets, added new zipped asset added --list to get a list of the theme names reworked some older theme code added rust-embed and zip crate removed the dark tests * fmt * Updated, removed excess comments Changed usage a bit Updated the error handling Added some helper items in --list
2020-08-10 19:43:16 +02:00
"walkdir",
]
Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from (#8009) # Description Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from # Tests + Formatting Added a test to support addition of the rust-ini crate. `cargo test --package nu-command --lib -- formats::from::ini::tests --nocapture` Executed all tests. `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-09 12:47:45 +01:00
[[package]]
name = "rust-ini"
Bump rust-ini from 0.19.0 to 0.20.0 (#10882)
2023-10-30 12:56:13 +01:00
version = "0.20.0"
Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from (#8009) # Description Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from # Tests + Formatting Added a test to support addition of the rust-ini crate. `cargo test --package nu-command --lib -- formats::from::ini::tests --nocapture` Executed all tests. `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-09 12:47:45 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump rust-ini from 0.19.0 to 0.20.0 (#10882)
2023-10-30 12:56:13 +01:00
checksum = "3e0698206bcb8882bf2a9ecb4c1e7785db57ff052297085a6efd4fe42302068a"
Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from (#8009) # Description Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from # Tests + Formatting Added a test to support addition of the rust-ini crate. `cargo test --package nu-command --lib -- formats::from::ini::tests --nocapture` Executed all tests. `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-09 12:47:45 +01:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from (#8009) # Description Added fix for #7981 - Replaced crate serde_ini with rust-ini for package nu-command/from # Tests + Formatting Added a test to support addition of the rust-ini crate. `cargo test --package nu-command --lib -- formats::from::ini::tests --nocapture` Executed all tests. `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-09 12:47:45 +01:00
"ordered-multimap",
]
removed rustyline config duplication (#2306) * removed rustyline config duplication set other rustyline defaults if line_editor section doesn't exist updated keyseq_timeout to -1 if emacs mode is chosen * change checking rustyline config to if lets * removed some unneccessary code
2020-08-05 23:34:28 +02:00
[[package]]
name = "rust_decimal"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "1.33.1"
removed rustyline config duplication (#2306) * removed rustyline config duplication set other rustyline defaults if line_editor section doesn't exist updated keyseq_timeout to -1 if emacs mode is chosen * change checking rustyline config to if lets * removed some unneccessary code
2020-08-05 23:34:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "06676aec5ccb8fc1da723cc8c0f9a46549f21ebb8753d3915c6c41db1e7f1dc4"
removed rustyline config duplication (#2306) * removed rustyline config duplication set other rustyline defaults if line_editor section doesn't exist updated keyseq_timeout to -1 if emacs mode is chosen * change checking rustyline config to if lets * removed some unneccessary code
2020-08-05 23:34:28 +02:00
dependencies = [
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"arrayvec 0.7.4",
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
"num-traits",
removed rustyline config duplication (#2306) * removed rustyline config duplication set other rustyline defaults if line_editor section doesn't exist updated keyseq_timeout to -1 if emacs mode is chosen * change checking rustyline config to if lets * removed some unneccessary code
2020-08-05 23:34:28 +02:00
]
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
[[package]]
name = "rustc-demangle"
version = "0.1.23"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d626bb9dae77e28219937af045c257c28bfd3f69333c512553507f5f9798cb76"
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
[[package]]
name = "rustc-hash"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "08d43f7aa6b08d49f382cde6a7982047c3426db949b1424bc4b7ec9ae12c6ce2"
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
[[package]]
Fix clippy warnings (#4176)
2021-12-02 19:05:38 +01:00
name = "rustc_version"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bfa0f585226d2e68097d4f95d113b15b83a82e819ab25717ec0590d9584ef366"
dependencies = [
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
"semver",
Update reedline to race-condition-free history (#955)
2022-02-06 01:16:21 +01:00
]
Bump tempfile from 3.4.0 to 3.5.0 (#8719) Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.4.0 to 3.5.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Stebalien/tempfile/blob/master/NEWS">tempfile's changelog</a>.</em></p> <blockquote> <h1>3.5.0</h1> <ul> <li>Update rustix from 0.36 to 0.37.1. This makes wasi work on rust stable</li> <li>Update <code>windows-sys</code>, <code>redox_syscall</code></li> <li>BREAKING: Remove the implementation of <code>Write for &amp;NamedTempFile&lt;F&gt; where &amp;F: Write</code>. Unfortunately, this can cause compile issues in unrelated code (<a href="https://redirect.github.com/Stebalien/tempfile/issues/224">Stebalien/tempfile#224</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/Stebalien/tempfile/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tempfile&package-manager=cargo&previous-version=3.4.0&new-version=3.5.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-06 22:39:31 +02:00
[[package]]
name = "rustix"
Bump `rustix` patch versions (#11044) We have three different `rustix` minor versions. For two of them with their previous patch versions a security advisory has been released: https://github.com/advisories/GHSA-c827-hfw6-qwvm Bump the patch versions, to resolve the potential vulnerability. At the moment we haven't assessed the potential impact on nushell, whether we are exposed to the underlying issue.
2023-11-13 15:09:37 +01:00
version = "0.37.27"
Bump tempfile from 3.4.0 to 3.5.0 (#8719) Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.4.0 to 3.5.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Stebalien/tempfile/blob/master/NEWS">tempfile's changelog</a>.</em></p> <blockquote> <h1>3.5.0</h1> <ul> <li>Update rustix from 0.36 to 0.37.1. This makes wasi work on rust stable</li> <li>Update <code>windows-sys</code>, <code>redox_syscall</code></li> <li>BREAKING: Remove the implementation of <code>Write for &amp;NamedTempFile&lt;F&gt; where &amp;F: Write</code>. Unfortunately, this can cause compile issues in unrelated code (<a href="https://redirect.github.com/Stebalien/tempfile/issues/224">Stebalien/tempfile#224</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/Stebalien/tempfile/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tempfile&package-manager=cargo&previous-version=3.4.0&new-version=3.5.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-06 22:39:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump `rustix` patch versions (#11044) We have three different `rustix` minor versions. For two of them with their previous patch versions a security advisory has been released: https://github.com/advisories/GHSA-c827-hfw6-qwvm Bump the patch versions, to resolve the potential vulnerability. At the moment we haven't assessed the potential impact on nushell, whether we are exposed to the underlying issue.
2023-11-13 15:09:37 +01:00
checksum = "fea8ca367a3a01fe35e6943c400addf443c0f57670e6ec51196f71a4b8762dd2"
Bump tempfile from 3.4.0 to 3.5.0 (#8719) Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.4.0 to 3.5.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Stebalien/tempfile/blob/master/NEWS">tempfile's changelog</a>.</em></p> <blockquote> <h1>3.5.0</h1> <ul> <li>Update rustix from 0.36 to 0.37.1. This makes wasi work on rust stable</li> <li>Update <code>windows-sys</code>, <code>redox_syscall</code></li> <li>BREAKING: Remove the implementation of <code>Write for &amp;NamedTempFile&lt;F&gt; where &amp;F: Write</code>. Unfortunately, this can cause compile issues in unrelated code (<a href="https://redirect.github.com/Stebalien/tempfile/issues/224">Stebalien/tempfile#224</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/Stebalien/tempfile/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tempfile&package-manager=cargo&previous-version=3.4.0&new-version=3.5.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-06 22:39:31 +02:00
dependencies = [
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
"bitflags 1.3.2",
Bump libproc from 0.13.0 to 0.14.0 (#9640)
2023-07-10 07:10:36 +02:00
"errno",
Bump tempfile from 3.4.0 to 3.5.0 (#8719) Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.4.0 to 3.5.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Stebalien/tempfile/blob/master/NEWS">tempfile's changelog</a>.</em></p> <blockquote> <h1>3.5.0</h1> <ul> <li>Update rustix from 0.36 to 0.37.1. This makes wasi work on rust stable</li> <li>Update <code>windows-sys</code>, <code>redox_syscall</code></li> <li>BREAKING: Remove the implementation of <code>Write for &amp;NamedTempFile&lt;F&gt; where &amp;F: Write</code>. Unfortunately, this can cause compile issues in unrelated code (<a href="https://redirect.github.com/Stebalien/tempfile/issues/224">Stebalien/tempfile#224</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/Stebalien/tempfile/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tempfile&package-manager=cargo&previous-version=3.4.0&new-version=3.5.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-06 22:39:31 +02:00
"io-lifetimes",
"libc",
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
"linux-raw-sys 0.3.8",
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
"windows-sys 0.48.0",
Bump procfs from 0.14.1 to 0.15.1 (#8233) Bumps [procfs](https://github.com/eminence/procfs) from 0.14.1 to 0.15.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/eminence/procfs/releases">procfs's releases</a>.</em></p> <blockquote> <h2>v0.15.1</h2> <h2>New features</h2> <ul> <li>Change Stat::comm documentation by <a href="https://github.com/rust1248"><code>@​rust1248</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/251">eminence/procfs#251</a></li> <li>Add docs and a as_str method to MMPermission by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/252">eminence/procfs#252</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/rust1248"><code>@​rust1248</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/251">eminence/procfs#251</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/eminence/procfs/compare/v0.15.0...v0.15.1">https://github.com/eminence/procfs/compare/v0.15.0...v0.15.1</a></p> <h2>v0.15.0</h2> <h2>New Features</h2> <ul> <li>Add /proc/iomem by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/216">eminence/procfs#216</a></li> <li>Add new functions to read various net files for a specific process by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/226">eminence/procfs#226</a></li> <li>add /proc/kpageflags by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/233">eminence/procfs#233</a></li> <li>Enable oppportunistic fd counting fast path by <a href="https://github.com/bobrik"><code>@​bobrik</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/234">eminence/procfs#234</a></li> <li>add /proc/kpagecount by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/232">eminence/procfs#232</a></li> <li>Add new <code>/proc/meminfo</code> fields. by <a href="https://github.com/afranchuk"><code>@​afranchuk</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/238">eminence/procfs#238</a></li> <li>impl Hash for kernel version by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/240">eminence/procfs#240</a></li> </ul> <h2>Bug fixes</h2> <ul> <li>fix chrono::Local::timestamp deprecated in chrono 0.4.23 by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/220">eminence/procfs#220</a></li> <li>Fix some minor documentation issues by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/225">eminence/procfs#225</a></li> <li>Fixes the reported path when a task's function returns an error by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/230">eminence/procfs#230</a></li> <li>fix shm size type by <a href="https://github.com/tatref"><code>@​tatref</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/243">eminence/procfs#243</a></li> </ul> <h2>Breaking changes</h2> <ul> <li>ticks_per_second and page_size are infallible by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/235">eminence/procfs#235</a></li> <li>parse uid for /proc/net/{tcp,udp} by <a href="https://github.com/trinity-1686a"><code>@​trinity-1686a</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/231">eminence/procfs#231</a></li> <li>Refactor and expose memory map processing. by <a href="https://github.com/afranchuk"><code>@​afranchuk</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/237">eminence/procfs#237</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/trinity-1686a"><code>@​trinity-1686a</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/231">eminence/procfs#231</a></li> <li><a href="https://github.com/afranchuk"><code>@​afranchuk</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/238">eminence/procfs#238</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/eminence/procfs/compare/v0.14.2...v0.15.0">https://github.com/eminence/procfs/compare/v0.14.2...v0.15.0</a></p> <h2>MSRV Note</h2> <p>This <code>v0.15</code> release is only tested against the latest stable rust compiler, but is known to work with older versions (down to rust 1.48). Support for these older compilers may break in <code>procfs</code> patch releases. See also <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/223">#223</a></p> <h2>v0.14.2</h2> <h2>New Features</h2> <ul> <li>Process: Namespace: Use openat instead of building a path by <a href="https://github.com/arilou"><code>@​arilou</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/192">eminence/procfs#192</a></li> <li>add serde serialize/deserialize derives for public types by <a href="https://github.com/eliad-wiz"><code>@​eliad-wiz</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/193">eminence/procfs#193</a></li> <li>Disabling default features on the <code>chrono</code> crate by <a href="https://github.com/Will-Low"><code>@​Will-Low</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/210">eminence/procfs#210</a></li> <li>Implement smaps_rollup by <a href="https://github.com/TaborKelly"><code>@​TaborKelly</code></a> in <a href="https://github-redirect.dependabot.com/eminence/procfs/pull/214">eminence/procfs#214</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/eminence/procfs/commit/16ccc15aa13d502379d9d55b779ddd969325eb26"><code>16ccc15</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/253">#253</a> from eminence/v0_15_1</li> <li><a href="https://github.com/eminence/procfs/commit/4b5b61a89d1720497202af0df4fe3fbee213c3ef"><code>4b5b61a</code></a> Version 0.15.1</li> <li><a href="https://github.com/eminence/procfs/commit/b7f66d5a8c7676054fa5aa58dd04351e5d5a7fc5"><code>b7f66d5</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/252">#252</a> from eminence/mmperms</li> <li><a href="https://github.com/eminence/procfs/commit/af961235ff6399aaeedf0c8504f55a114c36eed4"><code>af96123</code></a> Add docs and a as_str method to MMPermission</li> <li><a href="https://github.com/eminence/procfs/commit/6c6ddbd42e71748157d29062ac4d721fa5176b2a"><code>6c6ddbd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/251">#251</a> from rust1248/task/fix-comm-docs</li> <li><a href="https://github.com/eminence/procfs/commit/7e7afab4f89fc905240f44e0e740cec5344f52b9"><code>7e7afab</code></a> Change Stat::comm documentation</li> <li><a href="https://github.com/eminence/procfs/commit/391bd13a0ae5d4266d073b0c5540563f6034555e"><code>391bd13</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/247">#247</a> from eminence/statat_nofollow</li> <li><a href="https://github.com/eminence/procfs/commit/d0a7c09304eca6fb99f7b298e8c3f28a198f9af8"><code>d0a7c09</code></a> Don't use SYMLINK_NOFOLLOW in a statat call</li> <li><a href="https://github.com/eminence/procfs/commit/940c16324250bd5110572f51b91ac2b028af7a19"><code>940c163</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/eminence/procfs/issues/248">#248</a> from eminence/criterion_update</li> <li><a href="https://github.com/eminence/procfs/commit/0e31f6c8ee34a93375edbc0ea970eea3b137cccd"><code>0e31f6c</code></a> Update criterion dev-depencency</li> <li>Additional commits viewable in <a href="https://github.com/eminence/procfs/compare/v0.14.1...v0.15.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=procfs&package-manager=cargo&previous-version=0.14.1&new-version=0.15.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2023-02-27 08:53:01 +01:00
]
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
[[package]]
name = "rustix"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "0.38.28"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "72e572a5e8ca657d7366229cdde4bd14c4eb5499a9573d4d366fe1b599daa316"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
dependencies = [
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"bitflags 2.4.1",
Bump libproc from 0.13.0 to 0.14.0 (#9640)
2023-07-10 07:10:36 +02:00
"errno",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"libc",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"linux-raw-sys 0.4.12",
"windows-sys 0.52.0",
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
]
Obligatory reedline bump (#914) - Keybinding related improvements - internals - Vi insert should know more keybindings
2022-02-03 02:24:24 +01:00
[[package]]
name = "rustversion"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.0.14"
Obligatory reedline bump (#914) - Keybinding related improvements - internals - Vi insert should know more keybindings
2022-02-03 02:24:24 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "7ffc183a10b4478d04cbbbfc96d0873219d962dd5accaff2ffbd4ceb7df837f4"
Obligatory reedline bump (#914) - Keybinding related improvements - internals - Vi insert should know more keybindings
2022-02-03 02:24:24 +01:00
Add 'from json'
2021-10-01 07:11:49 +02:00
[[package]]
name = "ryu"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "1.0.16"
Add 'from json'
2021-10-01 07:11:49 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "f98d2aa92eebf49b69786be48e4477826b256916e84a57ff2a4f21923b48eb4c"
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "same-file"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 07:11:42 +01:00
version = "1.0.6"
Bat
2019-05-18 03:24:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 07:11:42 +01:00
checksum = "93fc1dc3aaa9bfed95e02e6eadabb4baf7e3078b0bd1b4d7b6b0b68378900502"
Bat
2019-05-18 03:24:13 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"winapi-util",
Bat
2019-05-18 03:24:13 +02:00
]
Add opening urls
2019-06-08 20:09:17 +02:00
[[package]]
name = "schannel"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.1.22"
Add opening urls
2019-06-08 20:09:17 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "0c3733bf4cf7ea0880754e19cb5a462007c4a8c1914bff372ccc95b464f1df88"
Add opening urls
2019-06-08 20:09:17 +02:00
dependencies = [
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"windows-sys 0.48.0",
Add opening urls
2019-06-08 20:09:17 +02:00
]
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 15:47:30 +02:00
[[package]]
name = "scopeguard"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.2.0"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 15:47:30 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "94143f37725109f92c262ed2cf5e59bce7498c01bcc1502d7b9afe439a4e9f49"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 15:47:30 +02:00
add table selector for downloading web tables (#4004) * add table selector for downloading web tables * type-o * updated debug mode to inspect mode
2021-09-16 16:02:30 +02:00
[[package]]
name = "scraper"
Bump scraper from 0.17.1 to 0.18.1 (#10879)
2023-10-30 12:53:26 +01:00
version = "0.18.1"
add table selector for downloading web tables (#4004) * add table selector for downloading web tables * type-o * updated debug mode to inspect mode
2021-09-16 16:02:30 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump scraper from 0.17.1 to 0.18.1 (#10879)
2023-10-30 12:53:26 +01:00
checksum = "585480e3719b311b78a573db1c9d9c4c1f8010c2dee4cc59c2efe58ea4dbc3e1"
add table selector for downloading web tables (#4004) * add table selector for downloading web tables * type-o * updated debug mode to inspect mode
2021-09-16 16:02:30 +02:00
dependencies = [
Update `unicode-linebreak` to `0.1.5` (#9814) # Description This deduplicates `ahash` as it was previously an outdated build-dependency of `unicode-linebreak` Should provide a small benefit to initial from scratch compile. # User-Facing Changes None
2023-07-30 22:17:36 +02:00
"ahash",
add table selector for downloading web tables (#4004) * add table selector for downloading web tables * type-o * updated debug mode to inspect mode
2021-09-16 16:02:30 +02:00
"cssparser",
"ego-tree",
"html5ever",
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
"once_cell",
add table selector for downloading web tables (#4004) * add table selector for downloading web tables * type-o * updated debug mode to inspect mode
2021-09-16 16:02:30 +02:00
"selectors",
"tendril",
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
[[package]]
name = "security-framework"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "2.9.2"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "05b64fb303737d99b81884b2c63433e9ae28abebe5eb5045dcdd175dc2ecf4de"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
dependencies = [
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-26 17:32:48 +02:00
"bitflags 1.3.2",
Temporarily(?) switch from heim+uom to sysinfo (#2954) * Switch from heim to sysinfo * WIP * more cleanup * fmt * lint
2021-01-20 08:18:38 +01:00
"core-foundation",
"core-foundation-sys",
Fix the versions up a bit to prevent breakage (#1602) * Fix the versions up a bit to prevent breakage * fix up the quickcheck test to not fail on parse error
2020-04-18 05:31:57 +02:00
"libc",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"security-framework-sys",
]
[[package]]
name = "security-framework-sys"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "2.9.1"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "e932934257d3b408ed8f30db49d85ea163bfe74961f017f405b025af298f0c7a"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
dependencies = [
Temporarily(?) switch from heim+uom to sysinfo (#2954) * Switch from heim to sysinfo * WIP * more cleanup * fmt * lint
2021-01-20 08:18:38 +01:00
"core-foundation-sys",
Add a --full mode to ps (#1507) * Add a --full mode to ps * Use a slightly older heim
2020-03-20 08:53:49 +01:00
"libc",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
]
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
[[package]]
name = "selectors"
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
version = "0.25.0"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
checksum = "4eb30575f3638fc8f6815f448d50cb1a2e255b0897985c8c59f4d37b72a07b06"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
dependencies = [
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"bitflags 2.4.1",
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
"cssparser",
"derive_more",
"fxhash",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"log",
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"new_debug_unreachable",
"phf 0.10.1",
"phf_codegen 0.10.0",
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
"precomputed-hash",
"servo_arc",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"smallvec",
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
]
updated dependencies (#2857) Same as #2786 Co-authored-by: sousajo <sousajo@pop-os.localdomain> Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-07 01:38:22 +01:00
[[package]]
name = "semver"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "1.0.20"
updated dependencies (#2857) Same as #2786 Co-authored-by: sousajo <sousajo@pop-os.localdomain> Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-07 01:38:22 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "836fa6a3e1e547f9a2c4040802ec865b5d85f4014efe00555d7090a3dcaa1090"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
[[package]]
name = "seq-macro"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.3.5"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "a3f0bf26fd526d2a95683cd0f87bf103b8539e2ca1ef48ce002d67aad59aa0b4"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
Lots of misc improvements
2019-06-03 09:41:28 +02:00
[[package]]
name = "serde"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "1.0.193"
Lots of misc improvements
2019-06-03 09:41:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "25dd9975e68d0cb5aa1120c288333fc98731bd1dd12f561e468ea4728c042b89"
Bump deps and add serde_bytes support
2019-07-15 20:34:44 +02:00
dependencies = [
Remove old nushell/merge engine-q
2022-02-07 20:54:06 +01:00
"serde_derive",
Bump deps and add serde_bytes support
2019-07-15 20:34:44 +02:00
]
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "serde_derive"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "1.0.193"
Bat
2019-05-18 03:24:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "43576ca501357b9b071ac53cdc7da8ef0cbd9493d8df094cd821777ea6e894d3"
Bat
2019-05-18 03:24:13 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"proc-macro2",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
Bat
2019-05-18 03:24:13 +02:00
]
[[package]]
name = "serde_json"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "1.0.108"
Bat
2019-05-18 03:24:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "3d1c7e3eac408d115102c4c24ad393e0821bb3a5df4d506a80f85f7a742a526b"
Bat
2019-05-18 03:24:13 +02:00
dependencies = [
Bump scraper from 0.14.0 to 0.15.0 (#8331) Bumps [scraper](https://github.com/causal-agent/scraper) from 0.14.0 to 0.15.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/causal-agent/scraper/releases">scraper's releases</a>.</em></p> <blockquote> <h2>0.15.0</h2> <h2>What's Changed</h2> <ul> <li>Bump cssparser to 0.28 and selectors to 0.23. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li>Create dependabot.yml by <a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li>Re-export Element trait from selectors crate by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/98">causal-agent/scraper#98</a></li> <li>build(deps): fix unchecked lock and update deps by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li>Re-export selectors' CaseSensitivity enum as it is part of our public API. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/108">causal-agent/scraper#108</a></li> <li>perf(element): add one sweep element creation by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/109">causal-agent/scraper#109</a></li> <li>Added feature flag <code>atomic</code> to make use of atomic <code>StrTendril</code> type. by <a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li><a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li><a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li><a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/causal-agent/scraper/commit/3cb7e9a3202fc6f8b80820135ad071916bc2908b"><code>3cb7e9a</code></a> Version 0.15.0</li> <li><a href="https://github.com/causal-agent/scraper/commit/06f395efe0fb4e9c31cdbd81a9f9e41802572b33"><code>06f395e</code></a> Apply clippy suggestion</li> <li><a href="https://github.com/causal-agent/scraper/commit/ec91bf1ebc9921ca2adeddf93555081912c33334"><code>ec91bf1</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/102">#102</a> from jaboatman/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/4b7fb13446f5ab4400b1fdfb3092b71b3157af9a"><code>4b7fb13</code></a> Merge remote-tracking branch 'upstream/master'</li> <li><a href="https://github.com/causal-agent/scraper/commit/aa479ea170b7f2b463ccba85de0c802318d19abe"><code>aa479ea</code></a> perf(element): add one sweep element creation (<a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/109">#109</a>)</li> <li><a href="https://github.com/causal-agent/scraper/commit/9a6a638db208682593d83bef53c29052336c0487"><code>9a6a638</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/108">#108</a> from adamreichold/also-re-export-case-sensitivity</li> <li><a href="https://github.com/causal-agent/scraper/commit/794b5eef87aa1009a31d4d29093269a04e7d80fa"><code>794b5ee</code></a> Re-export selectors' CaseSensitivity enum as it is part of our public API.</li> <li><a href="https://github.com/causal-agent/scraper/commit/6abb8cd625af5ea4f5a59530f03436aa448f7c56"><code>6abb8cd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/107">#107</a> from j-mendez/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/c3dd2600dcd4c17424a307c2f82cfcab41943014"><code>c3dd260</code></a> chore(minor): fix element classes map format</li> <li><a href="https://github.com/causal-agent/scraper/commit/b7955b9049ccf5b685f53854d88cca322aa80bac"><code>b7955b9</code></a> perf(selectors): add lazy classes map</li> <li>Additional commits viewable in <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=scraper&package-manager=cargo&previous-version=0.14.0&new-version=0.15.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-06 04:37:22 +01:00
"itoa",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"ryu",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"serde",
Lots of misc improvements
2019-06-03 09:41:28 +02:00
]
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
[[package]]
name = "serde_repr"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.1.17"
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "3081f5ffbb02284dda55132aa26daecedd7372a42417bbbab6f14ab7d6bb9145"
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
dependencies = [
"proc-macro2",
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
]
Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command (#7990) # Description Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command # Tests + Formatting Added two tests to support the toml upgrade. - `cargo test --package nu-command --lib -- formats::from::toml::tests --nocapture` Executed all tests. - `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-06 21:15:14 +01:00
[[package]]
name = "serde_spanned"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.6.4"
Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command (#7990) # Description Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command # Tests + Formatting Added two tests to support the toml upgrade. - `cargo test --package nu-command --lib -- formats::from::toml::tests --nocapture` Executed all tests. - `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-06 21:15:14 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "12022b835073e5b11e90a14f86838ceb1c8fb0325b72416845c487ac0fa95e80"
Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command (#7990) # Description Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command # Tests + Formatting Added two tests to support the toml upgrade. - `cargo test --package nu-command --lib -- formats::from::toml::tests --nocapture` Executed all tests. - `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-06 21:15:14 +01:00
dependencies = [
"serde",
]
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
[[package]]
name = "serde_urlencoded"
merge main
2022-02-08 14:28:21 +01:00
version = "0.7.1"
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
merge main
2022-02-08 14:28:21 +01:00
checksum = "d3491c14715ca2294c4d6a88f15e84739788c1d030eed8c110436aafdaa2f3fd"
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
dependencies = [
"form_urlencoded",
Bump scraper from 0.14.0 to 0.15.0 (#8331) Bumps [scraper](https://github.com/causal-agent/scraper) from 0.14.0 to 0.15.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/causal-agent/scraper/releases">scraper's releases</a>.</em></p> <blockquote> <h2>0.15.0</h2> <h2>What's Changed</h2> <ul> <li>Bump cssparser to 0.28 and selectors to 0.23. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li>Create dependabot.yml by <a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li>Re-export Element trait from selectors crate by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/98">causal-agent/scraper#98</a></li> <li>build(deps): fix unchecked lock and update deps by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li>Re-export selectors' CaseSensitivity enum as it is part of our public API. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/108">causal-agent/scraper#108</a></li> <li>perf(element): add one sweep element creation by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/109">causal-agent/scraper#109</a></li> <li>Added feature flag <code>atomic</code> to make use of atomic <code>StrTendril</code> type. by <a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li><a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li><a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li><a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/causal-agent/scraper/commit/3cb7e9a3202fc6f8b80820135ad071916bc2908b"><code>3cb7e9a</code></a> Version 0.15.0</li> <li><a href="https://github.com/causal-agent/scraper/commit/06f395efe0fb4e9c31cdbd81a9f9e41802572b33"><code>06f395e</code></a> Apply clippy suggestion</li> <li><a href="https://github.com/causal-agent/scraper/commit/ec91bf1ebc9921ca2adeddf93555081912c33334"><code>ec91bf1</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/102">#102</a> from jaboatman/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/4b7fb13446f5ab4400b1fdfb3092b71b3157af9a"><code>4b7fb13</code></a> Merge remote-tracking branch 'upstream/master'</li> <li><a href="https://github.com/causal-agent/scraper/commit/aa479ea170b7f2b463ccba85de0c802318d19abe"><code>aa479ea</code></a> perf(element): add one sweep element creation (<a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/109">#109</a>)</li> <li><a href="https://github.com/causal-agent/scraper/commit/9a6a638db208682593d83bef53c29052336c0487"><code>9a6a638</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/108">#108</a> from adamreichold/also-re-export-case-sensitivity</li> <li><a href="https://github.com/causal-agent/scraper/commit/794b5eef87aa1009a31d4d29093269a04e7d80fa"><code>794b5ee</code></a> Re-export selectors' CaseSensitivity enum as it is part of our public API.</li> <li><a href="https://github.com/causal-agent/scraper/commit/6abb8cd625af5ea4f5a59530f03436aa448f7c56"><code>6abb8cd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/107">#107</a> from j-mendez/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/c3dd2600dcd4c17424a307c2f82cfcab41943014"><code>c3dd260</code></a> chore(minor): fix element classes map format</li> <li><a href="https://github.com/causal-agent/scraper/commit/b7955b9049ccf5b685f53854d88cca322aa80bac"><code>b7955b9</code></a> perf(selectors): add lazy classes map</li> <li>Additional commits viewable in <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=scraper&package-manager=cargo&previous-version=0.14.0&new-version=0.15.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-06 04:37:22 +01:00
"itoa",
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
"ryu",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"serde",
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
]
Lots of misc improvements
2019-06-03 09:41:28 +02:00
[[package]]
name = "serde_yaml"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.9.27"
Lots of misc improvements
2019-06-03 09:41:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "3cc7a1570e38322cfe4154732e5110f887ea57e22b76f4bfd32b5bdd3368666c"
Lots of misc improvements
2019-06-03 09:41:28 +02:00
dependencies = [
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"indexmap",
Bump scraper from 0.14.0 to 0.15.0 (#8331) Bumps [scraper](https://github.com/causal-agent/scraper) from 0.14.0 to 0.15.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/causal-agent/scraper/releases">scraper's releases</a>.</em></p> <blockquote> <h2>0.15.0</h2> <h2>What's Changed</h2> <ul> <li>Bump cssparser to 0.28 and selectors to 0.23. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li>Create dependabot.yml by <a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li>Re-export Element trait from selectors crate by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/98">causal-agent/scraper#98</a></li> <li>build(deps): fix unchecked lock and update deps by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li>Re-export selectors' CaseSensitivity enum as it is part of our public API. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/108">causal-agent/scraper#108</a></li> <li>perf(element): add one sweep element creation by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/109">causal-agent/scraper#109</a></li> <li>Added feature flag <code>atomic</code> to make use of atomic <code>StrTendril</code> type. by <a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li><a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li><a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li><a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/causal-agent/scraper/commit/3cb7e9a3202fc6f8b80820135ad071916bc2908b"><code>3cb7e9a</code></a> Version 0.15.0</li> <li><a href="https://github.com/causal-agent/scraper/commit/06f395efe0fb4e9c31cdbd81a9f9e41802572b33"><code>06f395e</code></a> Apply clippy suggestion</li> <li><a href="https://github.com/causal-agent/scraper/commit/ec91bf1ebc9921ca2adeddf93555081912c33334"><code>ec91bf1</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/102">#102</a> from jaboatman/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/4b7fb13446f5ab4400b1fdfb3092b71b3157af9a"><code>4b7fb13</code></a> Merge remote-tracking branch 'upstream/master'</li> <li><a href="https://github.com/causal-agent/scraper/commit/aa479ea170b7f2b463ccba85de0c802318d19abe"><code>aa479ea</code></a> perf(element): add one sweep element creation (<a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/109">#109</a>)</li> <li><a href="https://github.com/causal-agent/scraper/commit/9a6a638db208682593d83bef53c29052336c0487"><code>9a6a638</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/108">#108</a> from adamreichold/also-re-export-case-sensitivity</li> <li><a href="https://github.com/causal-agent/scraper/commit/794b5eef87aa1009a31d4d29093269a04e7d80fa"><code>794b5ee</code></a> Re-export selectors' CaseSensitivity enum as it is part of our public API.</li> <li><a href="https://github.com/causal-agent/scraper/commit/6abb8cd625af5ea4f5a59530f03436aa448f7c56"><code>6abb8cd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/107">#107</a> from j-mendez/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/c3dd2600dcd4c17424a307c2f82cfcab41943014"><code>c3dd260</code></a> chore(minor): fix element classes map format</li> <li><a href="https://github.com/causal-agent/scraper/commit/b7955b9049ccf5b685f53854d88cca322aa80bac"><code>b7955b9</code></a> perf(selectors): add lazy classes map</li> <li>Additional commits viewable in <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=scraper&package-manager=cargo&previous-version=0.14.0&new-version=0.15.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-06 04:37:22 +01:00
"itoa",
merge main
2022-02-08 14:28:21 +01:00
"ryu",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"serde",
update a few nushell dependencies (#6291) * update a few nushell dependencies * update a test
2022-08-10 21:56:15 +02:00
"unsafe-libyaml",
Lots of misc improvements
2019-06-03 09:41:28 +02:00
]
Extract .nu-env tests and more granularity (#3078) The autoenv logic mutates environment variables in the running session as it operates and decides what to do for trusted directories containing `.nu-env` files. Few of the ways to interact with it were all in a single test function. We separate out all the ways that were done in the single test function to document it better. This will greatly help once we start refactoring our way out from setting environment variables this way to just setting them to `Scope`. This is part of an on-going effort to keep variables (`PATH` and `ENV`) in our `Scope` and rely on it for everything related to variables. We expect to move away from setting (`std::*`) envrironment variables in the current running process. This is non-trivial since we need to handle cases from vars coming in from the outside world, prioritize, and also compare to the ones we have both stored in memory and in configuration files. Also to send out our in-memory (in `Scope`) variables properly to external programs once we no longer rely on `std::env` vars from the running process.
2021-02-19 02:24:27 +01:00
[[package]]
name = "serial_test"
Bump serial_test from 1.0.0 to 2.0.0 (#9358)
2023-06-07 15:59:49 +02:00
version = "2.0.0"
Extract .nu-env tests and more granularity (#3078) The autoenv logic mutates environment variables in the running session as it operates and decides what to do for trusted directories containing `.nu-env` files. Few of the ways to interact with it were all in a single test function. We separate out all the ways that were done in the single test function to document it better. This will greatly help once we start refactoring our way out from setting environment variables this way to just setting them to `Scope`. This is part of an on-going effort to keep variables (`PATH` and `ENV`) in our `Scope` and rely on it for everything related to variables. We expect to move away from setting (`std::*`) envrironment variables in the current running process. This is non-trivial since we need to handle cases from vars coming in from the outside world, prioritize, and also compare to the ones we have both stored in memory and in configuration files. Also to send out our in-memory (in `Scope`) variables properly to external programs once we no longer rely on `std::env` vars from the running process.
2021-02-19 02:24:27 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump serial_test from 1.0.0 to 2.0.0 (#9358)
2023-06-07 15:59:49 +02:00
checksum = "0e56dd856803e253c8f298af3f4d7eb0ae5e23a737252cd90bb4f3b435033b2d"
Extract .nu-env tests and more granularity (#3078) The autoenv logic mutates environment variables in the running session as it operates and decides what to do for trusted directories containing `.nu-env` files. Few of the ways to interact with it were all in a single test function. We separate out all the ways that were done in the single test function to document it better. This will greatly help once we start refactoring our way out from setting environment variables this way to just setting them to `Scope`. This is part of an on-going effort to keep variables (`PATH` and `ENV`) in our `Scope` and rely on it for everything related to variables. We expect to move away from setting (`std::*`) envrironment variables in the current running process. This is non-trivial since we need to handle cases from vars coming in from the outside world, prioritize, and also compare to the ones we have both stored in memory and in configuration files. Also to send out our in-memory (in `Scope`) variables properly to external programs once we no longer rely on `std::env` vars from the running process.
2021-02-19 02:24:27 +01:00
dependencies = [
Bump serial_test from 0.8.0 to 0.10.0 (#7769)
2023-01-16 03:06:03 +01:00
"dashmap",
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
"futures",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"lazy_static",
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
"log",
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
"parking_lot",
Extract .nu-env tests and more granularity (#3078) The autoenv logic mutates environment variables in the running session as it operates and decides what to do for trusted directories containing `.nu-env` files. Few of the ways to interact with it were all in a single test function. We separate out all the ways that were done in the single test function to document it better. This will greatly help once we start refactoring our way out from setting environment variables this way to just setting them to `Scope`. This is part of an on-going effort to keep variables (`PATH` and `ENV`) in our `Scope` and rely on it for everything related to variables. We expect to move away from setting (`std::*`) envrironment variables in the current running process. This is non-trivial since we need to handle cases from vars coming in from the outside world, prioritize, and also compare to the ones we have both stored in memory and in configuration files. Also to send out our in-memory (in `Scope`) variables properly to external programs once we no longer rely on `std::env` vars from the running process.
2021-02-19 02:24:27 +01:00
"serial_test_derive",
]
[[package]]
name = "serial_test_derive"
Bump serial_test from 1.0.0 to 2.0.0 (#9358)
2023-06-07 15:59:49 +02:00
version = "2.0.0"
Extract .nu-env tests and more granularity (#3078) The autoenv logic mutates environment variables in the running session as it operates and decides what to do for trusted directories containing `.nu-env` files. Few of the ways to interact with it were all in a single test function. We separate out all the ways that were done in the single test function to document it better. This will greatly help once we start refactoring our way out from setting environment variables this way to just setting them to `Scope`. This is part of an on-going effort to keep variables (`PATH` and `ENV`) in our `Scope` and rely on it for everything related to variables. We expect to move away from setting (`std::*`) envrironment variables in the current running process. This is non-trivial since we need to handle cases from vars coming in from the outside world, prioritize, and also compare to the ones we have both stored in memory and in configuration files. Also to send out our in-memory (in `Scope`) variables properly to external programs once we no longer rely on `std::env` vars from the running process.
2021-02-19 02:24:27 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump serial_test from 1.0.0 to 2.0.0 (#9358)
2023-06-07 15:59:49 +02:00
checksum = "91d129178576168c589c9ec973feedf7d3126c01ac2bf08795109aa35b69fb8f"
Extract .nu-env tests and more granularity (#3078) The autoenv logic mutates environment variables in the running session as it operates and decides what to do for trusted directories containing `.nu-env` files. Few of the ways to interact with it were all in a single test function. We separate out all the ways that were done in the single test function to document it better. This will greatly help once we start refactoring our way out from setting environment variables this way to just setting them to `Scope`. This is part of an on-going effort to keep variables (`PATH` and `ENV`) in our `Scope` and rely on it for everything related to variables. We expect to move away from setting (`std::*`) envrironment variables in the current running process. This is non-trivial since we need to handle cases from vars coming in from the outside world, prioritize, and also compare to the ones we have both stored in memory and in configuration files. Also to send out our in-memory (in `Scope`) variables properly to external programs once we no longer rely on `std::env` vars from the running process.
2021-02-19 02:24:27 +01:00
dependencies = [
"proc-macro2",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
Extract .nu-env tests and more granularity (#3078) The autoenv logic mutates environment variables in the running session as it operates and decides what to do for trusted directories containing `.nu-env` files. Few of the ways to interact with it were all in a single test function. We separate out all the ways that were done in the single test function to document it better. This will greatly help once we start refactoring our way out from setting environment variables this way to just setting them to `Scope`. This is part of an on-going effort to keep variables (`PATH` and `ENV`) in our `Scope` and rely on it for everything related to variables. We expect to move away from setting (`std::*`) envrironment variables in the current running process. This is non-trivial since we need to handle cases from vars coming in from the outside world, prioritize, and also compare to the ones we have both stored in memory and in configuration files. Also to send out our in-memory (in `Scope`) variables properly to external programs once we no longer rely on `std::env` vars from the running process.
2021-02-19 02:24:27 +01:00
]
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
[[package]]
name = "servo_arc"
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
version = "0.3.0"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
checksum = "d036d71a959e00c77a63538b90a6c2390969f9772b096ea837205c6bd0491a44"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
dependencies = [
"stable_deref_trait",
]
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
[[package]]
name = "sha2"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.10.8"
Port `hash`, `hash md5` and `hash sha256` commands (#464) `hash` by itself is only printing the help message. The other two are simply using the same generic implementation.
2021-12-11 00:14:28 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "793db75ad2bcafc3ffa7c68b215fee268f537982cd901d132f89c6343f3a3dc8"
Port `hash`, `hash md5` and `hash sha256` commands (#464) `hash` by itself is only printing the help message. The other two are simply using the same generic implementation.
2021-12-11 00:14:28 +01:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Port `hash`, `hash md5` and `hash sha256` commands (#464) `hash` by itself is only printing the help message. The other two are simply using the same generic implementation.
2021-12-11 00:14:28 +01:00
"cpufeatures",
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
"digest",
Bump some of our dependencies (#1809)
2020-05-17 00:34:10 +02:00
]
Bump a few source compatible nu-command dependencies (#3724) Signed-off-by: Daniel Egger <daniel@eggers-club.de>
2021-07-05 09:16:34 +02:00
[[package]]
name = "shadow-rs"
Bump shadow-rs from 0.24.1 to 0.25.0 (#11282) Bumps [shadow-rs](https://github.com/baoyachi/shadow-rs) from 0.24.1 to 0.25.0. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/baoyachi/shadow-rs/commit/f08828be452aae3c78cf55c1c6762ae3b9782389"><code>f08828b</code></a> Update Cargo.toml</li> <li><a href="https://github.com/baoyachi/shadow-rs/commit/a3cc1a118f2bf4b1015b5ef2f3cac6565ea8c766"><code>a3cc1a1</code></a> Update README.md</li> <li><a href="https://github.com/baoyachi/shadow-rs/commit/96fdafc738a282f9307beb2648c1d1cf49d8db87"><code>96fdafc</code></a> Merge pull request <a href="https://redirect.github.com/baoyachi/shadow-rs/issues/144">#144</a> from baoyachi/wasm_example</li> <li><a href="https://github.com/baoyachi/shadow-rs/commit/24d3bd82c0fe361994de68fd6d4ebbc9bb01b02b"><code>24d3bd8</code></a> fix</li> <li><a href="https://github.com/baoyachi/shadow-rs/commit/aab9bf2d4d2f8e3912418deed204c421cfd55575"><code>aab9bf2</code></a> Update check.yml</li> <li><a href="https://github.com/baoyachi/shadow-rs/commit/1d4e4557303016acda399e6eb9debe4427ff5d66"><code>1d4e455</code></a> add wasm example</li> <li>See full diff in <a href="https://github.com/baoyachi/shadow-rs/compare/v0.24.1...v0.25.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=shadow-rs&package-manager=cargo&previous-version=0.24.1&new-version=0.25.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-12-20 10:49:03 +01:00
version = "0.25.0"
Bump a few source compatible nu-command dependencies (#3724) Signed-off-by: Daniel Egger <daniel@eggers-club.de>
2021-07-05 09:16:34 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump shadow-rs from 0.24.1 to 0.25.0 (#11282) Bumps [shadow-rs](https://github.com/baoyachi/shadow-rs) from 0.24.1 to 0.25.0. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/baoyachi/shadow-rs/commit/f08828be452aae3c78cf55c1c6762ae3b9782389"><code>f08828b</code></a> Update Cargo.toml</li> <li><a href="https://github.com/baoyachi/shadow-rs/commit/a3cc1a118f2bf4b1015b5ef2f3cac6565ea8c766"><code>a3cc1a1</code></a> Update README.md</li> <li><a href="https://github.com/baoyachi/shadow-rs/commit/96fdafc738a282f9307beb2648c1d1cf49d8db87"><code>96fdafc</code></a> Merge pull request <a href="https://redirect.github.com/baoyachi/shadow-rs/issues/144">#144</a> from baoyachi/wasm_example</li> <li><a href="https://github.com/baoyachi/shadow-rs/commit/24d3bd82c0fe361994de68fd6d4ebbc9bb01b02b"><code>24d3bd8</code></a> fix</li> <li><a href="https://github.com/baoyachi/shadow-rs/commit/aab9bf2d4d2f8e3912418deed204c421cfd55575"><code>aab9bf2</code></a> Update check.yml</li> <li><a href="https://github.com/baoyachi/shadow-rs/commit/1d4e4557303016acda399e6eb9debe4427ff5d66"><code>1d4e455</code></a> add wasm example</li> <li>See full diff in <a href="https://github.com/baoyachi/shadow-rs/compare/v0.24.1...v0.25.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=shadow-rs&package-manager=cargo&previous-version=0.24.1&new-version=0.25.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-12-20 10:49:03 +01:00
checksum = "615d846f7174a0850dca101bca72f6913e3376a64c5fda2b965d7fc3d1ff60cb"
Bump a few source compatible nu-command dependencies (#3724) Signed-off-by: Daniel Egger <daniel@eggers-club.de>
2021-07-05 09:16:34 +02:00
dependencies = [
update shadow-rs, update git2, remove indexmap from `version` (#5086)
2022-04-04 16:59:59 +02:00
"const_format",
Remove 'arboard' (#4174)
2021-12-01 20:48:03 +01:00
"is_debug",
Don't use `oldtime` feature of chrono (#9577) <!-- 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 `chrono` crate enables `oldtime` feature by default, which has a vulnerability (https://rustsec.org/advisories/RUSTSEC-2020-0071). This PR tries to remove `time` v0.1.45 completely from nu and add an audit CI to check for security vulnerabilities. :hand: Wait for the following PRs: - [x] https://github.com/nushell/reedline/pull/599 - [x] https://github.com/bspeice/dtparse/pull/44 - [x] https://github.com/Byron/trash-rs/pull/75 - [x] https://gitlab.com/imp/chrono-humanize-rs/-/merge_requests/15 # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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. --> --------- Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-25 10:54:01 +02:00
"time",
Bump a few source compatible nu-command dependencies (#3724) Signed-off-by: Daniel Egger <daniel@eggers-club.de>
2021-07-05 09:16:34 +02:00
]
Bump dialoguer from 0.9.0 to 0.10.3 (#7765)
2023-01-16 03:04:47 +01:00
[[package]]
name = "shell-words"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "24188a676b6ae68c3b2cb3a01be17fbf7240ce009799bb56d5b1409051e78fde"
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
[[package]]
name = "shlex"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.2.0"
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "a7cee0529a6d40f580e7a5e6c495c8fbfe21b7b52795ed4bb5e62cdf92bc6380"
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
Fix VCS markers not showing up in textview (#3530) Changes: * Bug fix - bat adds markers only when a file path is passed and it can use git2 on it. It doesn't add markers when bytes are passed. Hence, the code is adjusted accordingly. The sideeffect is files being opened multiple times and its content being unnecessarily loaded in memory. * Refactoring of the crate - Config is extracted to its struct file. Repetitive blocks of code are dried and nested conditionals are flattened.
2021-06-03 08:25:28 +02:00
[[package]]
engine-q merge
2022-02-07 20:11:34 +01:00
name = "signal-hook"
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 02:22:25 +02:00
version = "0.3.17"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 02:22:25 +02:00
checksum = "8621587d4798caf8eb44879d42e56b9a93ea5dcd315a6487c357130095b62801"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
dependencies = [
"libc",
"signal-hook-registry",
]
[[package]]
name = "signal-hook-mio"
updated cargo.lock with cargo update (#5201)
2022-04-15 13:04:15 +02:00
version = "0.2.3"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
updated cargo.lock with cargo update (#5201)
2022-04-15 13:04:15 +02:00
checksum = "29ad2e15f37ec9a6cc544097b78a1ec90001e9f71b81338ca39f430adaca99af"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
dependencies = [
"libc",
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"mio",
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
"signal-hook",
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 03:51:46 +01:00
]
[[package]]
name = "signal-hook-registry"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "1.4.1"
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 03:51:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "d8229b473baa5980ac72ef434c4415e70c4b5e71b423043adb4ba059f89c99a1"
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 03:51:46 +01:00
dependencies = [
"libc",
]
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
[[package]]
name = "simd-json"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.13.4"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "e5a3720326b20bf5b95b72dbbd133caae7e0dcf71eae8f6e6656e71a7e5c9aaa"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
dependencies = [
Update `unicode-linebreak` to `0.1.5` (#9814) # Description This deduplicates `ahash` as it was previously an outdated build-dependency of `unicode-linebreak` Should provide a small benefit to initial from scratch compile. # User-Facing Changes None
2023-07-30 22:17:36 +02:00
"ahash",
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
"getrandom",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"halfbrown",
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 16:27:37 +01:00
"lexical-core",
update dfr to polars 0.30.0 (#9424) # Description Update the polars dependency for dataframes to stay on-version. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 19:05:45 +02:00
"once_cell",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"ref-cast",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"serde",
"serde_json",
"simdutf8",
"value-trait",
]
Bump to 0.40 (#4129)
2021-11-16 09:53:03 +01:00
[[package]]
name = "simdutf8"
updated cargo.lock with cargo update (#5201)
2022-04-15 13:04:15 +02:00
version = "0.1.4"
Bump to 0.40 (#4129)
2021-11-16 09:53:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
updated cargo.lock with cargo update (#5201)
2022-04-15 13:04:15 +02:00
checksum = "f27f6278552951f1f2b8cf9da965d10969b2efdea95a6ec47987ab46edfe263a"
Bump to 0.40 (#4129)
2021-11-16 09:53:03 +01:00
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
[[package]]
name = "similar"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "2.3.0"
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "2aeaf503862c419d66959f5d7ca015337d864e9c49485d771b732e2a20453597"
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
Replace pretty_env_logger with simplelog (#6274) Fixes #5963 Signed-off-by: nibon7 <nibon7@163.com>
2022-08-09 18:44:37 +02:00
[[package]]
name = "simplelog"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "0.12.1"
Replace pretty_env_logger with simplelog (#6274) Fixes #5963 Signed-off-by: nibon7 <nibon7@163.com>
2022-08-09 18:44:37 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "acee08041c5de3d5048c8b3f6f13fafb3026b24ba43c6a695a0c76179b844369"
Replace pretty_env_logger with simplelog (#6274) Fixes #5963 Signed-off-by: nibon7 <nibon7@163.com>
2022-08-09 18:44:37 +02:00
dependencies = [
"log",
"termcolor",
Don't use `oldtime` feature of chrono (#9577) <!-- 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 `chrono` crate enables `oldtime` feature by default, which has a vulnerability (https://rustsec.org/advisories/RUSTSEC-2020-0071). This PR tries to remove `time` v0.1.45 completely from nu and add an audit CI to check for security vulnerabilities. :hand: Wait for the following PRs: - [x] https://github.com/nushell/reedline/pull/599 - [x] https://github.com/bspeice/dtparse/pull/44 - [x] https://github.com/Byron/trash-rs/pull/75 - [x] https://gitlab.com/imp/chrono-humanize-rs/-/merge_requests/15 # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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. --> --------- Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-25 10:54:01 +02:00
"time",
Replace pretty_env_logger with simplelog (#6274) Fixes #5963 Signed-off-by: nibon7 <nibon7@163.com>
2022-08-09 18:44:37 +02:00
]
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
[[package]]
name = "siphasher"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.3.11"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "38b58827f4464d87d377d175e90bf58eb00fd8716ff0a62f80356b5e61555d0d"
Add a simple scope variable
2021-11-02 04:08:05 +01:00
Small restructuring
2019-05-23 06:30:43 +02:00
[[package]]
name = "slab"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.4.9"
Revert "Unify use of the `surf` crate (#3855)" (#3871) This reverts commit 7f7af2bbaa90332377a9eea63e4e7e78cb834694.
2021-07-30 23:04:01 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "8f92a496fb766b417c996b9c5e57daf2f7ad3b0bebe1ccfca4856390e3d3bb67"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
dependencies = [
"autocfg",
]
Revert "Unify use of the `surf` crate (#3855)" (#3871) This reverts commit 7f7af2bbaa90332377a9eea63e4e7e78cb834694.
2021-07-30 23:04:01 +02:00
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
[[package]]
name = "smallvec"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "1.11.2"
Bat
2019-05-18 03:24:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "4dccd0940a2dcdf68d092b8cbab7dc0ad8fa938bf95787e1b916b0e3d0e8e970"
Bat
2019-05-18 03:24:13 +02:00
Polars upgrade 0.23 (#6303) * more lazy expressions * upgrade polars and correct functions * arg-where example * cargo clippy * restore modified filter files * correct string addition with str * correct string addition with str * correct message in test
2022-08-12 14:10:36 +02:00
[[package]]
name = "smartstring"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3fb72c633efbaa2dd666986505016c32c3044395ceaf881518399d2f4127ee29"
dependencies = [
"autocfg",
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"serde",
Polars upgrade 0.23 (#6303) * more lazy expressions * upgrade polars and correct functions * arg-where example * cargo clippy * restore modified filter files * correct string addition with str * correct string addition with str * correct message in test
2022-08-12 14:10:36 +02:00
"static_assertions",
"version_check",
]
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
[[package]]
name = "smawk"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.3.2"
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "b7c388c1b5e93756d0c740965c41e8822f866621d41acbdf6336a6a168f8840c"
Clean up lexer (#2956) * Document the lexer and lightly improve its names The bulk of this pull request adds a substantial amount of new inline documentation for the lexer. Along the way, I made a few minor changes to the names in the lexer, most of which were internal. The main change that affects other files is renaming `group` to `block`, since the function is actually parsing a block (a list of groups). * Further clean up the lexer - Consolidate the logic of the various token builders into a single type - Improve and clean up the event-driven BlockParser - Clean up comment parsing. Comments now contain their original leading whitespace as well as trailing whitespace, and know how to move some leading whitespace back into the body based on how the lexer decides to dedent the comments. This preserves the original whitespace information while still making it straight-forward to eliminate leading whitespace in help comments. * Update meta.rs * WIP * fix clippy * remove unwraps * remove unwraps Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com> Co-authored-by: Jonathan Turner <jonathan.d.turner@gmail.com>
2021-02-04 08:20:21 +01:00
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
[[package]]
name = "snap"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "1.1.1"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "1b6b67fb9a61334225b5b790716f609cd58395f895b3fe8b328786812a40bc3b"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
Revert "Unify use of the `surf` crate (#3855)" (#3871) This reverts commit 7f7af2bbaa90332377a9eea63e4e7e78cb834694.
2021-07-30 23:04:01 +02:00
[[package]]
name = "socket2"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.4.10"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "9f7916fc008ca5542385b89a3d3ce689953c143e9304a9bf8beec1de48994c0d"
Port fetch (with fixes) (#660) * Port fetch to engine-q * Fix check for path as a string * Add a timeout flag and fix some span issues * Add a temporary fetch command that returns byte streams. Got rid of async stuff as we're using the blocking feature of tokio * More tweaks for the bytestream * Rewrite fetch using ByteStreams * buffer read on bytes directly Co-authored-by: Stefan Stanciulescu <contact@stefanstanciulescu.com>
2022-01-04 03:01:18 +01:00
dependencies = [
"libc",
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"winapi",
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
]
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
[[package]]
name = "socket2"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.5.5"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "7b5fac59a5cb5dd637972e5fca70daf0523c9067fcdc4842f053dae04a18f8e9"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
dependencies = [
"libc",
"windows-sys 0.48.0",
]
Add 'detect columns' command (#4127) * Add 'detect columns' command * Fix warnings
2021-11-15 23:29:54 +01:00
[[package]]
name = "spin"
Bump spin from 0.9.5 to 0.9.8 (#8730) Bumps [spin](https://github.com/mvdnes/spin-rs) from 0.9.5 to 0.9.8. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/mvdnes/spin-rs/blob/master/CHANGELOG.md">spin's changelog</a>.</em></p> <blockquote> <h1>[0.9.8] - 2023-04-03</h1> <h3>Fixed</h3> <ul> <li>Unsoundness in <code>Once::try_call_once</code> caused by an <code>Err(_)</code> result</li> </ul> <h1>[0.9.7] - 2023-03-27</h1> <h3>Fixed</h3> <ul> <li>Relaxed accidentally restricted <code>Send</code>/<code>Sync</code> bounds for <code>Mutex</code> guards</li> </ul> <h1>[0.9.6] - 2023-03-13</h1> <h3>Fixed</h3> <ul> <li>Relaxed accidentally restricted <code>Send</code>/<code>Sync</code> bounds for <code>RwLock</code> guards</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/mvdnes/spin-rs/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=spin&package-manager=cargo&previous-version=0.9.5&new-version=0.9.8)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/nushell/nushell/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 20:58:32 +02:00
version = "0.9.8"
Add 'detect columns' command (#4127) * Add 'detect columns' command * Fix warnings
2021-11-15 23:29:54 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump spin from 0.9.5 to 0.9.8 (#8730) Bumps [spin](https://github.com/mvdnes/spin-rs) from 0.9.5 to 0.9.8. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/mvdnes/spin-rs/blob/master/CHANGELOG.md">spin's changelog</a>.</em></p> <blockquote> <h1>[0.9.8] - 2023-04-03</h1> <h3>Fixed</h3> <ul> <li>Unsoundness in <code>Once::try_call_once</code> caused by an <code>Err(_)</code> result</li> </ul> <h1>[0.9.7] - 2023-03-27</h1> <h3>Fixed</h3> <ul> <li>Relaxed accidentally restricted <code>Send</code>/<code>Sync</code> bounds for <code>Mutex</code> guards</li> </ul> <h1>[0.9.6] - 2023-03-13</h1> <h3>Fixed</h3> <ul> <li>Relaxed accidentally restricted <code>Send</code>/<code>Sync</code> bounds for <code>RwLock</code> guards</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/mvdnes/spin-rs/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=spin&package-manager=cargo&previous-version=0.9.5&new-version=0.9.8)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/nushell/nushell/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 20:58:32 +02:00
checksum = "6980e8d7511241f8acf4aebddbb1ff938df5eebe98691418c4468d0b72a96a67"
Add 'detect columns' command (#4127) * Add 'detect columns' command * Fix warnings
2021-11-15 23:29:54 +01:00
dependencies = [
"lock_api",
]
Database commands (#5307) * database commands * db commands * filesystem opens sqlite file * clippy error * corrected error in ci file * removes matrix flag from ci * flax matrix for clippy * add conditional compile for tests * add conditional compile for tests * correct order of command * correct error msg * correct typo
2022-04-24 11:29:21 +02:00
[[package]]
name = "sqlparser"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.39.0"
Database commands (#5307) * database commands * db commands * filesystem opens sqlite file * clippy error * corrected error in ci file * removes matrix flag from ci * flax matrix for clippy * add conditional compile for tests * add conditional compile for tests * correct order of command * correct error msg * correct typo
2022-04-24 11:29:21 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "743b4dc2cbde11890ccb254a8fc9d537fa41b36da00de2a1c5e9848c9bc42bd7"
Database commands (#5307) * database commands * db commands * filesystem opens sqlite file * clippy error * corrected error in ci file * removes matrix flag from ci * flax matrix for clippy * add conditional compile for tests * add conditional compile for tests * correct order of command * correct error msg * correct typo
2022-04-24 11:29:21 +02:00
dependencies = [
"log",
]
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
[[package]]
name = "stable_deref_trait"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a8f112729512f8e442d81f95a8a7ddf2b7c6b8a1a6f509a95864142b30cab2d3"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "stacker"
version = "0.1.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c886bd4480155fd3ef527d45e9ac8dd7118a898a46530b7b94c3e21866259fce"
dependencies = [
"cc",
"cfg-if",
"libc",
"psm",
"winapi",
]
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
[[package]]
name = "static_assertions"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a2eb9349b6444b326872e140eb1cf5e7c522154d69e7a0ffb0fb81c06b37543f"
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
[[package]]
name = "str_indices"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.4.3"
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "e9557cb6521e8d009c51a8666f09356f4b817ba9ba0981a305bd86aee47bd35c"
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
[[package]]
Bump to 0.40 (#4129)
2021-11-16 09:53:03 +01:00
name = "streaming-decompression"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
version = "0.1.2"
Bump to 0.40 (#4129)
2021-11-16 09:53:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
checksum = "bf6cc3b19bfb128a8ad11026086e31d3ce9ad23f8ea37354b31383a187c44cf3"
Bump to 0.40 (#4129)
2021-11-16 09:53:03 +01:00
dependencies = [
"fallible-streaming-iterator",
]
[[package]]
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
name = "streaming-iterator"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "0.1.9"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "2b2231b7c3057d5e4ad0156fb3dc807d900806020c5ffa3ee6ff2c8c76fb8520"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
[[package]]
name = "strength_reduce"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "0.2.4"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "fe895eb47f22e2ddd4dabc02bce419d2e643c8e3b585c78158b349195bc24d82"
Update to polars 0.16 (#4013) * update to polars 0.16 * enabled features for polars
2021-09-15 21:10:12 +02:00
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
[[package]]
name = "string_cache"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "0.8.7"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "f91138e76242f575eb1d3b38b4f1362f10d3a43f47d182a5b359af488a02293b"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
dependencies = [
"new_debug_unreachable",
updated cargo.lock with cargo update (#5201)
2022-04-15 13:04:15 +02:00
"once_cell",
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
"parking_lot",
merge main
2022-02-08 14:28:21 +01:00
"phf_shared 0.10.0",
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
"precomputed-hash",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"serde",
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
]
[[package]]
name = "string_cache_codegen"
updated cargo.lock with cargo update (#5201)
2022-04-15 13:04:15 +02:00
version = "0.5.2"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
updated cargo.lock with cargo update (#5201)
2022-04-15 13:04:15 +02:00
checksum = "6bb30289b722be4ff74a408c3cc27edeaad656e06cb1fe8fa9231fa59c728988"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
dependencies = [
updated cargo.lock with cargo update (#5201)
2022-04-15 13:04:15 +02:00
"phf_generator 0.10.0",
"phf_shared 0.10.0",
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
"proc-macro2",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"quote",
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
]
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 21:02:26 +01:00
[[package]]
name = "strip-ansi-escapes"
update `strip-ansi-escapes` to 0.2.0 and the latest reedline (#9970) # Description This PR fixes the semver issues with `strip-ansi-escapes` and updates it to 0.2.0 as well as updating to the latest reedline which just landed an identical patch. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `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-08-09 19:33:07 +02:00
version = "0.2.0"
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 21:02:26 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update `strip-ansi-escapes` to 0.2.0 and the latest reedline (#9970) # Description This PR fixes the semver issues with `strip-ansi-escapes` and updates it to 0.2.0 as well as updating to the latest reedline which just landed an identical patch. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `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-08-09 19:33:07 +02:00
checksum = "55ff8ef943b384c414f54aefa961dd2bd853add74ec75e7ac74cf91dba62bcfa"
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 21:02:26 +01:00
dependencies = [
update `strip-ansi-escapes` to use new api (#9958) # Description This PR updates `strip-ansi-escapes` to support their new API. This also updates nushell to the latest reedline after the same fix https://github.com/nushell/reedline/pull/617 closes #9957 # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `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-08-08 22:20:37 +02:00
"vte 0.11.1",
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 21:02:26 +01:00
]
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
[[package]]
name = "strsim"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "73473c0e59e6d5812c5dfe2a064a6444949f089e20eec9a2e5506596494e4623"
Update reedline dev version lock (#9644) - See nushell/reedline#600 - updates to `strum 0.25` which uses the newer more widespread `syn 2.0` - this deduplicates `syn` for a default build. - Unlocks #9639
2023-07-10 13:04:49 +02:00
[[package]]
name = "strum"
version = "0.25.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "290d54ea6f91c969195bdbcd7442c8c2a2ba87da8bf60a7ee86a235d4bc1e125"
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 02:22:25 +02:00
dependencies = [
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"strum_macros",
Update `crossterm`/`ratatui`/dev-`reedline` (#10137) # Description This updates most crates to 0.27 `crossterm`. To do so we need the most recent `ratatui` `reedline` can now update as well. See https://github.com/nushell/reedline/pull/625 Sadly this introduces some crate duplication again as there are some other dependency updates. Furthermore we have another crate depending on 0.26.1 crossterm (`comfy-table` that some how gets pulled in by polars) # User-Facing Changes 2 additional mouse events detected by `input listen` # Tests + Formatting None
2023-09-04 02:22:25 +02:00
]
Update reedline dev version lock (#9644) - See nushell/reedline#600 - updates to `strum 0.25` which uses the newer more widespread `syn 2.0` - this deduplicates `syn` for a default build. - Unlocks #9639
2023-07-10 13:04:49 +02:00
Obligatory reedline bump (#914) - Keybinding related improvements - internals - Vi insert should know more keybindings
2022-02-03 02:24:24 +01:00
[[package]]
name = "strum_macros"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.25.3"
Obligatory reedline bump (#914) - Keybinding related improvements - internals - Vi insert should know more keybindings
2022-02-03 02:24:24 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "23dc1fa9ac9c169a78ba62f0b841814b7abae11bdd047b9c58f893439e309ea0"
Obligatory reedline bump (#914) - Keybinding related improvements - internals - Vi insert should know more keybindings
2022-02-03 02:24:24 +01:00
dependencies = [
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"heck",
Obligatory reedline bump (#914) - Keybinding related improvements - internals - Vi insert should know more keybindings
2022-02-03 02:24:24 +01:00
"proc-macro2",
"quote",
"rustversion",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
Update reedline dev version lock (#9644) - See nushell/reedline#600 - updates to `strum 0.25` which uses the newer more widespread `syn 2.0` - this deduplicates `syn` for a default build. - Unlocks #9639
2023-07-10 13:04:49 +02:00
]
updated fetch to surf2.2 and feature h1-client-rustls (#3120)
2021-03-03 19:18:11 +01:00
[[package]]
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
name = "supports-color"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "2.1.0"
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "d6398cde53adc3c4557306a96ce67b302968513830a77a95b2b17305d9719a89"
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
dependencies = [
Bump miette from 5.5.0 to 5.6.0 (#8531) Bumps [miette](https://github.com/zkat/miette) from 5.5.0 to 5.6.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zkat/miette/blob/main/CHANGELOG.md">miette's changelog</a>.</em></p> <blockquote> <h2>5.6.0 (2023-03-14)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>ci:</strong> configure clippy-specific MSRV (<a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747">b658fc02</a>)</li> <li><strong>graphical:</strong> Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>) (<a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0">3497508a</a>)</li> <li><strong>atty:</strong> Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>) (<a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e">443d240f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>protocol:</strong> implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>) (<a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d">ed486c95</a>)</li> </ul> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/zkat/miette/commit/78fe18e6990feacc8bdaeeb10e1439a12c111e6e"><code>78fe18e</code></a> chore: Release</li> <li><a href="https://github.com/zkat/miette/commit/2335b25ee7d22bd4ef4e1ef1dd9527fe2accd2be"><code>2335b25</code></a> docs: update changelog</li> <li><a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e"><code>443d240</code></a> fix(atty): Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>)</li> <li><a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d"><code>ed486c9</code></a> feat(protocol): implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>)</li> <li><a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0"><code>3497508</code></a> fix(graphical): Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>)</li> <li><a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747"><code>b658fc0</code></a> fix(ci): configure clippy-specific MSRV</li> <li><a href="https://github.com/zkat/miette/commit/ebc61b5cf809e4215ca92c32d892cfc4ffb05fa9"><code>ebc61b5</code></a> docs: Mention miette::miette! macro under &quot;... in application code&quot; (<a href="https://redirect.github.com/zkat/miette/issues/233">#233</a>)</li> <li><a href="https://github.com/zkat/miette/commit/14f952dc91b9f27b7ae1e9e03b89744bcc682fa2"><code>14f952d</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li><a href="https://github.com/zkat/miette/commit/128c0a1fae0b578b2de5c8967b87df0d89cd1c54"><code>128c0a1</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li>See full diff in <a href="https://github.com/zkat/miette/compare/miette-derive-v5.5.0...miette-derive-v5.6.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=miette&package-manager=cargo&previous-version=5.5.0&new-version=5.6.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-24 10:55:25 +01:00
"is-terminal",
deps: bump to miette 3.0 mainline
2021-09-23 01:49:39 +02:00
"is_ci",
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
]
[[package]]
name = "supports-hyperlinks"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
version = "2.1.0"
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
checksum = "f84231692eb0d4d41e4cdd0cabfdd2e6cd9e255e65f80c9aa7c98dd502b4233d"
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
dependencies = [
Bump miette from 5.5.0 to 5.6.0 (#8531) Bumps [miette](https://github.com/zkat/miette) from 5.5.0 to 5.6.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zkat/miette/blob/main/CHANGELOG.md">miette's changelog</a>.</em></p> <blockquote> <h2>5.6.0 (2023-03-14)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>ci:</strong> configure clippy-specific MSRV (<a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747">b658fc02</a>)</li> <li><strong>graphical:</strong> Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>) (<a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0">3497508a</a>)</li> <li><strong>atty:</strong> Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>) (<a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e">443d240f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>protocol:</strong> implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>) (<a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d">ed486c95</a>)</li> </ul> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/zkat/miette/commit/78fe18e6990feacc8bdaeeb10e1439a12c111e6e"><code>78fe18e</code></a> chore: Release</li> <li><a href="https://github.com/zkat/miette/commit/2335b25ee7d22bd4ef4e1ef1dd9527fe2accd2be"><code>2335b25</code></a> docs: update changelog</li> <li><a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e"><code>443d240</code></a> fix(atty): Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>)</li> <li><a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d"><code>ed486c9</code></a> feat(protocol): implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>)</li> <li><a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0"><code>3497508</code></a> fix(graphical): Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>)</li> <li><a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747"><code>b658fc0</code></a> fix(ci): configure clippy-specific MSRV</li> <li><a href="https://github.com/zkat/miette/commit/ebc61b5cf809e4215ca92c32d892cfc4ffb05fa9"><code>ebc61b5</code></a> docs: Mention miette::miette! macro under &quot;... in application code&quot; (<a href="https://redirect.github.com/zkat/miette/issues/233">#233</a>)</li> <li><a href="https://github.com/zkat/miette/commit/14f952dc91b9f27b7ae1e9e03b89744bcc682fa2"><code>14f952d</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li><a href="https://github.com/zkat/miette/commit/128c0a1fae0b578b2de5c8967b87df0d89cd1c54"><code>128c0a1</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li>See full diff in <a href="https://github.com/zkat/miette/compare/miette-derive-v5.5.0...miette-derive-v5.6.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=miette&package-manager=cargo&previous-version=5.5.0&new-version=5.6.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-24 10:55:25 +01:00
"is-terminal",
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
]
[[package]]
name = "supports-unicode"
Bump miette from 5.5.0 to 5.6.0 (#8531) Bumps [miette](https://github.com/zkat/miette) from 5.5.0 to 5.6.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zkat/miette/blob/main/CHANGELOG.md">miette's changelog</a>.</em></p> <blockquote> <h2>5.6.0 (2023-03-14)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>ci:</strong> configure clippy-specific MSRV (<a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747">b658fc02</a>)</li> <li><strong>graphical:</strong> Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>) (<a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0">3497508a</a>)</li> <li><strong>atty:</strong> Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>) (<a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e">443d240f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>protocol:</strong> implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>) (<a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d">ed486c95</a>)</li> </ul> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/zkat/miette/commit/78fe18e6990feacc8bdaeeb10e1439a12c111e6e"><code>78fe18e</code></a> chore: Release</li> <li><a href="https://github.com/zkat/miette/commit/2335b25ee7d22bd4ef4e1ef1dd9527fe2accd2be"><code>2335b25</code></a> docs: update changelog</li> <li><a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e"><code>443d240</code></a> fix(atty): Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>)</li> <li><a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d"><code>ed486c9</code></a> feat(protocol): implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>)</li> <li><a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0"><code>3497508</code></a> fix(graphical): Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>)</li> <li><a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747"><code>b658fc0</code></a> fix(ci): configure clippy-specific MSRV</li> <li><a href="https://github.com/zkat/miette/commit/ebc61b5cf809e4215ca92c32d892cfc4ffb05fa9"><code>ebc61b5</code></a> docs: Mention miette::miette! macro under &quot;... in application code&quot; (<a href="https://redirect.github.com/zkat/miette/issues/233">#233</a>)</li> <li><a href="https://github.com/zkat/miette/commit/14f952dc91b9f27b7ae1e9e03b89744bcc682fa2"><code>14f952d</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li><a href="https://github.com/zkat/miette/commit/128c0a1fae0b578b2de5c8967b87df0d89cd1c54"><code>128c0a1</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li>See full diff in <a href="https://github.com/zkat/miette/compare/miette-derive-v5.5.0...miette-derive-v5.6.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=miette&package-manager=cargo&previous-version=5.5.0&new-version=5.6.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-24 10:55:25 +01:00
version = "2.0.0"
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump miette from 5.5.0 to 5.6.0 (#8531) Bumps [miette](https://github.com/zkat/miette) from 5.5.0 to 5.6.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zkat/miette/blob/main/CHANGELOG.md">miette's changelog</a>.</em></p> <blockquote> <h2>5.6.0 (2023-03-14)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>ci:</strong> configure clippy-specific MSRV (<a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747">b658fc02</a>)</li> <li><strong>graphical:</strong> Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>) (<a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0">3497508a</a>)</li> <li><strong>atty:</strong> Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>) (<a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e">443d240f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>protocol:</strong> implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>) (<a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d">ed486c95</a>)</li> </ul> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/zkat/miette/commit/78fe18e6990feacc8bdaeeb10e1439a12c111e6e"><code>78fe18e</code></a> chore: Release</li> <li><a href="https://github.com/zkat/miette/commit/2335b25ee7d22bd4ef4e1ef1dd9527fe2accd2be"><code>2335b25</code></a> docs: update changelog</li> <li><a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e"><code>443d240</code></a> fix(atty): Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>)</li> <li><a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d"><code>ed486c9</code></a> feat(protocol): implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>)</li> <li><a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0"><code>3497508</code></a> fix(graphical): Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>)</li> <li><a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747"><code>b658fc0</code></a> fix(ci): configure clippy-specific MSRV</li> <li><a href="https://github.com/zkat/miette/commit/ebc61b5cf809e4215ca92c32d892cfc4ffb05fa9"><code>ebc61b5</code></a> docs: Mention miette::miette! macro under &quot;... in application code&quot; (<a href="https://redirect.github.com/zkat/miette/issues/233">#233</a>)</li> <li><a href="https://github.com/zkat/miette/commit/14f952dc91b9f27b7ae1e9e03b89744bcc682fa2"><code>14f952d</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li><a href="https://github.com/zkat/miette/commit/128c0a1fae0b578b2de5c8967b87df0d89cd1c54"><code>128c0a1</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li>See full diff in <a href="https://github.com/zkat/miette/compare/miette-derive-v5.5.0...miette-derive-v5.6.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=miette&package-manager=cargo&previous-version=5.5.0&new-version=5.6.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-24 10:55:25 +01:00
checksum = "4b6c2cb240ab5dd21ed4906895ee23fe5a48acdbd15a3ce388e7b62a9b66baf7"
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
dependencies = [
Bump miette from 5.5.0 to 5.6.0 (#8531) Bumps [miette](https://github.com/zkat/miette) from 5.5.0 to 5.6.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zkat/miette/blob/main/CHANGELOG.md">miette's changelog</a>.</em></p> <blockquote> <h2>5.6.0 (2023-03-14)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>ci:</strong> configure clippy-specific MSRV (<a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747">b658fc02</a>)</li> <li><strong>graphical:</strong> Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>) (<a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0">3497508a</a>)</li> <li><strong>atty:</strong> Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>) (<a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e">443d240f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>protocol:</strong> implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>) (<a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d">ed486c95</a>)</li> </ul> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/zkat/miette/commit/78fe18e6990feacc8bdaeeb10e1439a12c111e6e"><code>78fe18e</code></a> chore: Release</li> <li><a href="https://github.com/zkat/miette/commit/2335b25ee7d22bd4ef4e1ef1dd9527fe2accd2be"><code>2335b25</code></a> docs: update changelog</li> <li><a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e"><code>443d240</code></a> fix(atty): Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>)</li> <li><a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d"><code>ed486c9</code></a> feat(protocol): implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>)</li> <li><a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0"><code>3497508</code></a> fix(graphical): Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>)</li> <li><a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747"><code>b658fc0</code></a> fix(ci): configure clippy-specific MSRV</li> <li><a href="https://github.com/zkat/miette/commit/ebc61b5cf809e4215ca92c32d892cfc4ffb05fa9"><code>ebc61b5</code></a> docs: Mention miette::miette! macro under &quot;... in application code&quot; (<a href="https://redirect.github.com/zkat/miette/issues/233">#233</a>)</li> <li><a href="https://github.com/zkat/miette/commit/14f952dc91b9f27b7ae1e9e03b89744bcc682fa2"><code>14f952d</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li><a href="https://github.com/zkat/miette/commit/128c0a1fae0b578b2de5c8967b87df0d89cd1c54"><code>128c0a1</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li>See full diff in <a href="https://github.com/zkat/miette/compare/miette-derive-v5.5.0...miette-derive-v5.6.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=miette&package-manager=cargo&previous-version=5.5.0&new-version=5.6.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-24 10:55:25 +01:00
"is-terminal",
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
]
updated fetch to surf2.2 and feature h1-client-rustls (#3120)
2021-03-03 19:18:11 +01:00
xpath command for nushell (#2656) * xpath prototype * new xpath engine is finally working * nearly there * closer * working with list, started to add test, code cleanup * broken again * working again - time for some cleanup * cleaned up code, added error handling and test * update example, fix clippy * removed commented char
2020-10-12 15:03:00 +02:00
[[package]]
name = "sxd-document"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "94d82f37be9faf1b10a82c4bd492b74f698e40082f0f40de38ab275f31d42078"
dependencies = [
"peresil",
"typed-arena",
]
[[package]]
name = "sxd-xpath"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "36e39da5d30887b5690e29de4c5ebb8ddff64ebd9933f98a01daaa4fd11b36ea"
dependencies = [
"peresil",
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
"quick-error 1.2.3",
xpath command for nushell (#2656) * xpath prototype * new xpath engine is finally working * nearly there * closer * working with list, started to add test, code cleanup * broken again * working again - time for some cleanup * cleaned up code, added error handling and test * update example, fix clippy * removed commented char
2020-10-12 15:03:00 +02:00
"sxd-document",
]
Feature/def signature with comments (#2905) * Put parse_definition related funcs into own module * Add failing lexer test * Implement Parsing of definition signature This commit applied changes how the signature of a function is parsed. Before there was a little bit of "quick-and-dirty" string-matching/parsing involved. Now, a signature is a little bit more properly parsed. The grammar of a definition signature understood by these parsing-functions is as follows: `[ (parameter | flag | <eol>)* ]` where parameter is: `name (<:> type)? (<,> | <eol> | (#Comment <eol>))?` flag is: `--name (-shortform)? (<:> type)? (<,> | <eol> | (#Comment <eol>))?` (Note: After the last item no <,> has to come.) Note: It is now possible to pass comments to flags and parameters Example: [ d:int # The required d parameter --x (-x):string # The all powerful x flag --y (-y):int # The accompanying y flag ] (Sadly there seems to be a bug (Or is this expected behaviour?) in the lexer, because of which `--x(-x)` would be treated as one baseline token and is therefore not correctly recognized as 2. For now a space has to be inserted) During the implementation of the module, 2 question arose: Should flag/parameter names be allowed to be type names? Example case: ```shell def f [ string ] { echo $string } ``` Currently an error is thrown * Fix clippy lints * Remove wrong comment * Add spacing * Add Cargo.lock
2021-01-11 18:53:58 +01:00
[[package]]
name = "syn"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "1.0.109"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "72b64191b275b66ffe2469e8af2c1cfe3bafa67b529ead792a6d0160888b4237"
objectshell initial commit
2019-05-10 18:59:12 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"proc-macro2",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"quote",
cargo update (#5639)
2022-05-25 19:13:14 +02:00
"unicode-ident",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Bump miette from 5.6.0 to 5.7.0 (#8720)
2023-04-06 22:39:54 +02:00
[[package]]
name = "syn"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "2.0.40"
Bump miette from 5.6.0 to 5.7.0 (#8720)
2023-04-06 22:39:54 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "13fa70a4ee923979ffb522cacce59d34421ebdea5625e1073c4326ef9d2dd42e"
Bump miette from 5.6.0 to 5.7.0 (#8720)
2023-04-06 22:39:54 +02:00
dependencies = [
"proc-macro2",
"quote",
"unicode-ident",
]
WIP: Add vcard/ical support (#1504) * Initial from-ical implementation * Initial from-vcard implementation * Rename from-ics and from-vcf for autoconvert * Remove redundant clones * Add from-vcf and from-ics tests Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2020-03-20 20:35:09 +01:00
[[package]]
add locale for ls size (#3497) * add locale for ls size * updated to work when it's not an exact match like de_DE when it needs de
2021-05-27 01:02:24 +02:00
name = "sys-locale"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.3.1"
add locale for ls size (#3497) * add locale for ls size * updated to work when it's not an exact match like de_DE when it needs de
2021-05-27 01:02:24 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "e801cf239ecd6ccd71f03d270d67dd53d13e90aab208bf4b8fe4ad957ea949b0"
add locale for ls size (#3497) * add locale for ls size * updated to work when it's not an exact match like de_DE when it needs de
2021-05-27 01:02:24 +02:00
dependencies = [
"libc",
]
remove unused dependencies (#9230) # Description This is a test PR to see if we can remove dependencies. The crates to remove was generated from cargo machete. If ci works, I'll update the PR to remove deps instead of comment them out. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 18:37:20 +02:00
[[package]]
name = "sysinfo"
Bump `sysinfo` to 0.29.11 (#11166) I discovered [a condition in which `sysinfo` would segfault](https://github.com/GuillaumeGomez/sysinfo/issues/1154), thereby causing nushell to segfault when the `sys` command was run (perhaps the cause of [this](https://github.com/nushell/nushell/issues/10987)). The segfault was fixed in `sysinfo`, I'm just bumping the version here.
2023-11-27 16:37:47 +01:00
version = "0.29.11"
remove unused dependencies (#9230) # Description This is a test PR to see if we can remove dependencies. The crates to remove was generated from cargo machete. If ci works, I'll update the PR to remove deps instead of comment them out. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 18:37:20 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump `sysinfo` to 0.29.11 (#11166) I discovered [a condition in which `sysinfo` would segfault](https://github.com/GuillaumeGomez/sysinfo/issues/1154), thereby causing nushell to segfault when the `sys` command was run (perhaps the cause of [this](https://github.com/nushell/nushell/issues/10987)). The segfault was fixed in `sysinfo`, I'm just bumping the version here.
2023-11-27 16:37:47 +01:00
checksum = "cd727fc423c2060f6c92d9534cef765c65a6ed3f428a03d7def74a8c4348e666"
SQLite History MVP with timestamp, duration, working directory, exit status metadata (#5721) This PR adds support for an SQLite history via nushell/reedline#401 The SQLite history is enabled by setting history_file_format: "sqlite" in config.nu. * somewhat working sqlite history * Hook up history command * Fix error in SQlitebacked with empty lines When entering an empty line there previously was the "No command run" error with `SqliteBackedHistory` during addition of the metadata May be considered a temporary fix Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2022-06-14 22:53:33 +02:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
SQLite History MVP with timestamp, duration, working directory, exit status metadata (#5721) This PR adds support for an SQLite history via nushell/reedline#401 The SQLite history is enabled by setting history_file_format: "sqlite" in config.nu. * somewhat working sqlite history * Hook up history command * Fix error in SQlitebacked with empty lines When entering an empty line there previously was the "No command run" error with `SqliteBackedHistory` during addition of the metadata May be considered a temporary fix Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2022-06-14 22:53:33 +02:00
"core-foundation-sys",
"libc",
Use nt-api 4 on Windows (#6949) * Bump nushell-sytem dep to ntapi 0.4 0.3.7 trigger a warning about code being incompatible with future rust versions. This is resolved in 0.4 https://github.com/MSxDOS/ntapi/issues/11 * Upgrade Cargo.lock for ntapi 0.4
2022-10-30 14:29:41 +01:00
"ntapi",
SQLite History MVP with timestamp, duration, working directory, exit status metadata (#5721) This PR adds support for an SQLite history via nushell/reedline#401 The SQLite history is enabled by setting history_file_format: "sqlite" in config.nu. * somewhat working sqlite history * Hook up history command * Fix error in SQlitebacked with empty lines When entering an empty line there previously was the "No command run" error with `SqliteBackedHistory` during addition of the metadata May be considered a temporary fix Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2022-06-14 22:53:33 +02:00
"once_cell",
"rayon",
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"winapi",
SQLite History MVP with timestamp, duration, working directory, exit status metadata (#5721) This PR adds support for an SQLite history via nushell/reedline#401 The SQLite history is enabled by setting history_file_format: "sqlite" in config.nu. * somewhat working sqlite history * Hook up history command * Fix error in SQlitebacked with empty lines When entering an empty line there previously was the "No command run" error with `SqliteBackedHistory` during addition of the metadata May be considered a temporary fix Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2022-06-14 22:53:33 +02:00
]
Give tabled a try (#5969) * Drop in replacement from nu-table to tabled. Must act the same way as original nu-table. Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Fix some issues Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump ansi-str version Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update to latest Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix footer issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header style Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Use latest tabled/ansi-str * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy warnings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-06 21:57:40 +02:00
[[package]]
name = "tabled"
Add an option to set header on border (style) (#9920) fix #9796 Sorry that you've had the issues. I've actually encountered them yesterday too (seems like they have appeared after some refactoring in the middle) but was not able to fix that rapid. Created a bunch of tests. cc: @fdncred Note: This option will be certainly slower then a default ones. (could be fixed but ... maybe later). Maybe it shall be cited somewhere. PS: Haven't tested on a wrapped/expanded tables. --------- Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-08-04 20:50:47 +02:00
version = "0.14.0"
nu-table/ Bump tabled version (#6097) Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-22 17:33:29 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add an option to set header on border (style) (#9920) fix #9796 Sorry that you've had the issues. I've actually encountered them yesterday too (seems like they have appeared after some refactoring in the middle) but was not able to fix that rapid. Created a bunch of tests. cc: @fdncred Note: This option will be certainly slower then a default ones. (could be fixed but ... maybe later). Maybe it shall be cited somewhere. PS: Haven't tested on a wrapped/expanded tables. --------- Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-08-04 20:50:47 +02:00
checksum = "dfe9c3632da101aba5131ed63f9eed38665f8b3c68703a6bb18124835c1a5d22"
Give tabled a try (#5969) * Drop in replacement from nu-table to tabled. Must act the same way as original nu-table. Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Fix some issues Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump ansi-str version Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update to latest Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix footer issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header style Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Use latest tabled/ansi-str * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy warnings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-06 21:57:40 +02:00
dependencies = [
Remove duplicated dependency on `ansi-str 0.7` (#9641) # Description `tabled`/`papergrid` already use `ansi-str 0.8` while `nu-explore` itself was still depending on `0.7`. Single fix necessary to adapt to the new API. cc @zhiburt # User-Facing Changes None
2023-07-10 09:24:08 +02:00
"ansi-str",
Bump `tabled` dependency to 0.11 (#8922) close? #8060 Quite a bit of refactoring took place. I believe a few improvements to collapse/expand were made. I've tried to track any performance regressions and seems like it is fine. I've noticed something different now with default configuration path or something in this regard? So I might missed something while testing because of this. Requires some oversight. --------- Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2023-04-26 20:56:10 +02:00
"ansitok",
Give tabled a try (#5969) * Drop in replacement from nu-table to tabled. Must act the same way as original nu-table. Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Fix some issues Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump ansi-str version Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update to latest Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix footer issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix header style Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Use latest tabled/ansi-str * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy warnings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-07-06 21:57:40 +02:00
"papergrid",
"unicode-width",
]
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
[[package]]
name = "target-features"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.1.5"
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "cfb5fa503293557c5158bd215fdc225695e567a77e453f5d4452a50a193969bd"
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
Add opening urls
2019-06-08 20:09:17 +02:00
[[package]]
name = "tempfile"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "3.8.1"
Add opening urls
2019-06-08 20:09:17 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "7ef1adac450ad7f4b3c28589471ade84f25f731a7a0fe30d71dfa9f60fd808e5"
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
merge main
2022-02-08 14:28:21 +01:00
"fastrand",
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"redox_syscall",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"rustix 0.38.28",
Bump tempfile from 3.5.0 to 3.6.0 (#9591)
2023-07-03 11:49:48 +02:00
"windows-sys 0.48.0",
Add opening urls
2019-06-08 20:09:17 +02:00
]
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
[[package]]
name = "tendril"
updated cargo.lock with cargo update (#5201)
2022-04-15 13:04:15 +02:00
version = "0.4.3"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
updated cargo.lock with cargo update (#5201)
2022-04-15 13:04:15 +02:00
checksum = "d24a120c5fc464a3458240ee02c299ebcb9d67b5249c8848b09d639dca8d7bb0"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
dependencies = [
"futf",
"mac",
"utf-8",
]
A real parser (lalrpop)
2019-05-26 08:54:41 +02:00
[[package]]
name = "termcolor"
corrected history menu (#4814)
2022-03-10 21:58:11 +01:00
version = "1.1.3"
A real parser (lalrpop)
2019-05-26 08:54:41 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
corrected history menu (#4814)
2022-03-10 21:58:11 +01:00
checksum = "bab24d30b911b2376f3a13cc2cd443142f0c81dda04c118693e35b3835757755"
A real parser (lalrpop)
2019-05-26 08:54:41 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"winapi-util",
A real parser (lalrpop)
2019-05-26 08:54:41 +02:00
]
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
[[package]]
name = "terminal_size"
Dataframe commands (#3502) * Sample command * Join command with checks * More dataframes commands * Groupby and aggregate commands * Missing feature dataframe flag * Renamed file * New commands for dataframes * error parser and df reference * filter command for dataframes * removed name from nu_dataframe * commands to save to parquet and csv
2021-06-03 08:23:14 +02:00
version = "0.1.17"
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Dataframe commands (#3502) * Sample command * Join command with checks * More dataframes commands * Groupby and aggregate commands * Missing feature dataframe flag * Renamed file * New commands for dataframes * error parser and df reference * filter command for dataframes * removed name from nu_dataframe * commands to save to parquet and csv
2021-06-03 08:23:14 +02:00
checksum = "633c1a546cee861a1a6d0dc69ebeca693bf4296661ba7852b9d21d159e0506df"
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
dependencies = [
"libc",
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"winapi",
WIP: output `ls` as a grid vs table
2021-10-05 15:43:20 +02:00
]
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
[[package]]
name = "terminal_size"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
version = "0.2.6"
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
checksum = "8e6bf6f19e9f8ed8d4048dc22981458ebcf406d67e94cd422e5ecd73d63b3237"
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
dependencies = [
Bump `rustix` patch versions (#11044) We have three different `rustix` minor versions. For two of them with their previous patch versions a security advisory has been released: https://github.com/advisories/GHSA-c827-hfw6-qwvm Bump the patch versions, to resolve the potential vulnerability. At the moment we haven't assessed the potential impact on nushell, whether we are exposed to the underlying issue.
2023-11-13 15:09:37 +01:00
"rustix 0.37.27",
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
"windows-sys 0.48.0",
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
]
Bump terminal_size from 0.2.6 to 0.3.0 (#10409) Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.6 to 0.3.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/eminence/terminal-size/releases">terminal_size's releases</a>.</em></p> <blockquote> <h2>v0.3.0</h2> <h2>What's Changed</h2> <ul> <li>Check all streams (out/err/in) to find one that has a tty and size by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://redirect.github.com/eminence/terminal-size/pull/58">eminence/terminal-size#58</a> <ul> <li>Note that this is a subtle change in behavior, since the <code>terminal_size()</code> function will now return success in cases more cases than before</li> </ul> </li> <li>Update to rustix 0.38 by <a href="https://github.com/chenx97"><code>@​chenx97</code></a> in <a href="https://redirect.github.com/eminence/terminal-size/pull/57">eminence/terminal-size#57</a> <ul> <li>This change bumps the MSRV from 1.48.0 to 1.63.0</li> </ul> </li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/eminence/terminal-size/compare/v0.2.6...v0.3.0">https://github.com/eminence/terminal-size/compare/v0.2.6...v0.3.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/eminence/terminal-size/commit/2983b7bf18531bbd2face938d2889f4590f9cb56"><code>2983b7b</code></a> Release v0.3.0</li> <li><a href="https://github.com/eminence/terminal-size/commit/27a4459b22594e804a608d0d29d194d2c6e454e3"><code>27a4459</code></a> Merge pull request <a href="https://redirect.github.com/eminence/terminal-size/issues/57">#57</a> from chenx97/rustix-0.38</li> <li><a href="https://github.com/eminence/terminal-size/commit/c24c1c34e51408c70136c9e6cff79d6d60f8aeed"><code>c24c1c3</code></a> Bump MSRV to 1.63.0</li> <li><a href="https://github.com/eminence/terminal-size/commit/78e13c77d7de86cf6d95dfaaf3ff71fec95d0cb4"><code>78e13c7</code></a> Update to rustix 0.38</li> <li><a href="https://github.com/eminence/terminal-size/commit/18c58b1ed5e4306826226d95e835ffd32f8c5926"><code>18c58b1</code></a> Merge pull request <a href="https://redirect.github.com/eminence/terminal-size/issues/58">#58</a> from eminence/check_all_streams</li> <li><a href="https://github.com/eminence/terminal-size/commit/08f0e73926c11adc3105dbf4eb84dd8c9e6c873a"><code>08f0e73</code></a> Check all streams (out/err/in) to find one that has a tty and size</li> <li>See full diff in <a href="https://github.com/eminence/terminal-size/compare/v0.2.6...v0.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=terminal_size&package-manager=cargo&previous-version=0.2.6&new-version=0.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-09-18 07:50:17 +02:00
[[package]]
name = "terminal_size"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "21bebf2b7c9e0a515f6e0f8c51dc0f8e4696391e6f1ff30379559f8365fb0df7"
dependencies = [
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"rustix 0.38.28",
Bump terminal_size from 0.2.6 to 0.3.0 (#10409) Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.6 to 0.3.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/eminence/terminal-size/releases">terminal_size's releases</a>.</em></p> <blockquote> <h2>v0.3.0</h2> <h2>What's Changed</h2> <ul> <li>Check all streams (out/err/in) to find one that has a tty and size by <a href="https://github.com/eminence"><code>@​eminence</code></a> in <a href="https://redirect.github.com/eminence/terminal-size/pull/58">eminence/terminal-size#58</a> <ul> <li>Note that this is a subtle change in behavior, since the <code>terminal_size()</code> function will now return success in cases more cases than before</li> </ul> </li> <li>Update to rustix 0.38 by <a href="https://github.com/chenx97"><code>@​chenx97</code></a> in <a href="https://redirect.github.com/eminence/terminal-size/pull/57">eminence/terminal-size#57</a> <ul> <li>This change bumps the MSRV from 1.48.0 to 1.63.0</li> </ul> </li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/eminence/terminal-size/compare/v0.2.6...v0.3.0">https://github.com/eminence/terminal-size/compare/v0.2.6...v0.3.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/eminence/terminal-size/commit/2983b7bf18531bbd2face938d2889f4590f9cb56"><code>2983b7b</code></a> Release v0.3.0</li> <li><a href="https://github.com/eminence/terminal-size/commit/27a4459b22594e804a608d0d29d194d2c6e454e3"><code>27a4459</code></a> Merge pull request <a href="https://redirect.github.com/eminence/terminal-size/issues/57">#57</a> from chenx97/rustix-0.38</li> <li><a href="https://github.com/eminence/terminal-size/commit/c24c1c34e51408c70136c9e6cff79d6d60f8aeed"><code>c24c1c3</code></a> Bump MSRV to 1.63.0</li> <li><a href="https://github.com/eminence/terminal-size/commit/78e13c77d7de86cf6d95dfaaf3ff71fec95d0cb4"><code>78e13c7</code></a> Update to rustix 0.38</li> <li><a href="https://github.com/eminence/terminal-size/commit/18c58b1ed5e4306826226d95e835ffd32f8c5926"><code>18c58b1</code></a> Merge pull request <a href="https://redirect.github.com/eminence/terminal-size/issues/58">#58</a> from eminence/check_all_streams</li> <li><a href="https://github.com/eminence/terminal-size/commit/08f0e73926c11adc3105dbf4eb84dd8c9e6c873a"><code>08f0e73</code></a> Check all streams (out/err/in) to find one that has a tty and size</li> <li>See full diff in <a href="https://github.com/eminence/terminal-size/compare/v0.2.6...v0.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=terminal_size&package-manager=cargo&previous-version=0.2.6&new-version=0.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-09-18 07:50:17 +02:00
"windows-sys 0.48.0",
]
add rm command + stubs for open and save
2021-10-10 06:13:15 +02:00
[[package]]
name = "termtree"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
version = "0.4.1"
add rm command + stubs for open and save
2021-10-10 06:13:15 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
checksum = "3369f5ac52d5eb6ab48c6b4ffdc8efbcad6b89c765749064ba298f2c68a16a76"
add rm command + stubs for open and save
2021-10-10 06:13:15 +02:00
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
[[package]]
name = "textwrap"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "0.15.2"
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "b7b3e525a49ec206798b40326a44121291b530c963cfb01018f63e135bac543d"
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
dependencies = [
"smawk",
"unicode-linebreak",
"unicode-width",
Cat with wings (#1993) * WIP - Modified textview to use bat crate * use input_from_bytes_with_name instead of input_file * removed old paging added prettyprint on else blocks duplicated too much code hard coded defaults Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-16 23:17:32 +02:00
]
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
[[package]]
name = "thiserror"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "1.0.50"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "f9a7210f5c9a7156bb50aa36aed4c95afb51df0df00713949448cf9e97d382d2"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
dependencies = [
"thiserror-impl",
]
[[package]]
name = "thiserror-impl"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "1.0.50"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "266b2e40bc00e5a6c09c3584011e08b06f123c00362c92b975ba9843aaaa14b8"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
dependencies = [
"proc-macro2",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 07:45:27 +01:00
]
Fuzzy completion matching (#5320) * Implement fuzzy match algorithm for suggestions * Use MatchingAlgorithm for custom completions
2022-04-24 23:43:18 +02:00
[[package]]
name = "thread_local"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "1.1.7"
Fuzzy completion matching (#5320) * Implement fuzzy match algorithm for suggestions * Use MatchingAlgorithm for custom completions
2022-04-24 23:43:18 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "3fdd6f064ccff2d6567adcb3873ca630700f00b5ad3f060c25b5dcfd9a4ce152"
Fuzzy completion matching (#5320) * Implement fuzzy match algorithm for suggestions * Use MatchingAlgorithm for custom completions
2022-04-24 23:43:18 +02:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Fuzzy completion matching (#5320) * Implement fuzzy match algorithm for suggestions * Use MatchingAlgorithm for custom completions
2022-04-24 23:43:18 +02:00
"once_cell",
]
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
[[package]]
name = "time"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.3.30"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "c4a34ab300f2dee6e562c10a046fc05e358b29f9bf92277f30c3c8d82275f6f5"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
dependencies = [
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
"deranged",
Bump scraper from 0.14.0 to 0.15.0 (#8331) Bumps [scraper](https://github.com/causal-agent/scraper) from 0.14.0 to 0.15.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/causal-agent/scraper/releases">scraper's releases</a>.</em></p> <blockquote> <h2>0.15.0</h2> <h2>What's Changed</h2> <ul> <li>Bump cssparser to 0.28 and selectors to 0.23. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li>Create dependabot.yml by <a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li>Re-export Element trait from selectors crate by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/98">causal-agent/scraper#98</a></li> <li>build(deps): fix unchecked lock and update deps by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li>Re-export selectors' CaseSensitivity enum as it is part of our public API. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/108">causal-agent/scraper#108</a></li> <li>perf(element): add one sweep element creation by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/109">causal-agent/scraper#109</a></li> <li>Added feature flag <code>atomic</code> to make use of atomic <code>StrTendril</code> type. by <a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li><a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li><a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li><a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/causal-agent/scraper/commit/3cb7e9a3202fc6f8b80820135ad071916bc2908b"><code>3cb7e9a</code></a> Version 0.15.0</li> <li><a href="https://github.com/causal-agent/scraper/commit/06f395efe0fb4e9c31cdbd81a9f9e41802572b33"><code>06f395e</code></a> Apply clippy suggestion</li> <li><a href="https://github.com/causal-agent/scraper/commit/ec91bf1ebc9921ca2adeddf93555081912c33334"><code>ec91bf1</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/102">#102</a> from jaboatman/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/4b7fb13446f5ab4400b1fdfb3092b71b3157af9a"><code>4b7fb13</code></a> Merge remote-tracking branch 'upstream/master'</li> <li><a href="https://github.com/causal-agent/scraper/commit/aa479ea170b7f2b463ccba85de0c802318d19abe"><code>aa479ea</code></a> perf(element): add one sweep element creation (<a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/109">#109</a>)</li> <li><a href="https://github.com/causal-agent/scraper/commit/9a6a638db208682593d83bef53c29052336c0487"><code>9a6a638</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/108">#108</a> from adamreichold/also-re-export-case-sensitivity</li> <li><a href="https://github.com/causal-agent/scraper/commit/794b5eef87aa1009a31d4d29093269a04e7d80fa"><code>794b5ee</code></a> Re-export selectors' CaseSensitivity enum as it is part of our public API.</li> <li><a href="https://github.com/causal-agent/scraper/commit/6abb8cd625af5ea4f5a59530f03436aa448f7c56"><code>6abb8cd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/107">#107</a> from j-mendez/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/c3dd2600dcd4c17424a307c2f82cfcab41943014"><code>c3dd260</code></a> chore(minor): fix element classes map format</li> <li><a href="https://github.com/causal-agent/scraper/commit/b7955b9049ccf5b685f53854d88cca322aa80bac"><code>b7955b9</code></a> perf(selectors): add lazy classes map</li> <li>Additional commits viewable in <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=scraper&package-manager=cargo&previous-version=0.14.0&new-version=0.15.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-06 04:37:22 +01:00
"itoa",
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
"libc",
"num_threads",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"powerfmt",
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
"serde",
"time-core",
Replace pretty_env_logger with simplelog (#6274) Fixes #5963 Signed-off-by: nibon7 <nibon7@163.com>
2022-08-09 18:44:37 +02:00
"time-macros",
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
]
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
[[package]]
name = "time-core"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.1.2"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "ef927ca75afb808a4d64dd374f00a2adf8d0fcff8e7b184af886c3c87ec4a3f3"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
Replace pretty_env_logger with simplelog (#6274) Fixes #5963 Signed-off-by: nibon7 <nibon7@163.com>
2022-08-09 18:44:37 +02:00
[[package]]
name = "time-macros"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.2.15"
Replace pretty_env_logger with simplelog (#6274) Fixes #5963 Signed-off-by: nibon7 <nibon7@163.com>
2022-08-09 18:44:37 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "4ad70d68dba9e1f8aceda7aa6711965dfec1cac869f311a51bd08b3a2ccbce20"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
dependencies = [
"time-core",
]
Replace pretty_env_logger with simplelog (#6274) Fixes #5963 Signed-off-by: nibon7 <nibon7@163.com>
2022-08-09 18:44:37 +02:00
update ini dependency (#9426) # Description This PR updates the ini dependency. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-06-13 20:33:00 +02:00
[[package]]
name = "tiny-keccak"
version = "2.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2c9d3793400a45f954c52e73d068316d76b6f4e36977e3fcebb13a2721e80237"
dependencies = [
"crunchy",
]
Plugin: Add benchmark for different encoding protocol (#6384) * add MessagePack as a plugin protocol * tmp merge from remote * add benchmark * use less benchmark group, and add README for analysing benchmark result * update README * update README * rewrite * remove comment * rename * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-08-23 18:49:51 +02:00
[[package]]
name = "tinytemplate"
version = "1.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "be4d6b5f19ff7664e8c98d03e2139cb510db9b0a60b55f8e8709b689d939b6bc"
dependencies = [
"serde",
"serde_json",
]
Make mode subcommand: math mode (#2043) * Update calculate to return a table when Value is a table * impl mode subcommand for math * add tests for math mode subcommand * add table/row tests for math mode subcommand * fix formatting
2020-06-24 19:57:27 +02:00
[[package]]
name = "tinyvec"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
version = "1.6.0"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
checksum = "87cc5ceb3875bb20c2890005a4e226a4651264a5c75edb2421b52861a0a0cb50"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
dependencies = [
"tinyvec_macros",
]
[[package]]
name = "tinyvec_macros"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "0.1.1"
Make mode subcommand: math mode (#2043) * Update calculate to return a table when Value is a table * impl mode subcommand for math * add tests for math mode subcommand * add table/row tests for math mode subcommand * fix formatting
2020-06-24 19:57:27 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "1f3ccbac311fea05f86f61904b462b55fb3df8837a366dfc601a0161d0532f20"
Make mode subcommand: math mode (#2043) * Update calculate to return a table when Value is a table * impl mode subcommand for math * add tests for math mode subcommand * add table/row tests for math mode subcommand * fix formatting
2020-06-24 19:57:27 +02:00
Date utility commands (#2780) * updated & added date related commands based on the new design * added proper error handling when date format string is invalid * fixed format issue * fixed an issue caused due to the change in primitive Date type * added `date list-timezone` command to list all supported time zones and updated `date to-timezone` accordingly
2020-12-12 19:18:03 +01:00
[[package]]
name = "titlecase"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "2.2.1"
Date utility commands (#2780) * updated & added date related commands based on the new design * added proper error handling when date format string is invalid * fixed format issue * fixed an issue caused due to the change in primitive Date type * added `date list-timezone` command to list all supported time zones and updated `date to-timezone` accordingly
2020-12-12 19:18:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "38397a8cdb017cfeb48bf6c154d6de975ac69ffeed35980fde199d2ee0842042"
Date utility commands (#2780) * updated & added date related commands based on the new design * added proper error handling when date format string is invalid * fixed format issue * fixed an issue caused due to the change in primitive Date type * added `date list-timezone` command to list all supported time zones and updated `date to-timezone` accordingly
2020-12-12 19:18:03 +01:00
dependencies = [
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
"joinery",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"lazy_static",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"regex",
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
]
Revert "Unify use of the `surf` crate (#3855)" (#3871) This reverts commit 7f7af2bbaa90332377a9eea63e4e7e78cb834694.
2021-07-30 23:04:01 +02:00
[[package]]
name = "tokio"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "1.35.0"
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "841d45b238a16291a4e1584e61820b8ae57d696cc5015c459c229ccc6990cc1c"
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
dependencies = [
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
"backtrace",
Port fetch (with fixes) (#660) * Port fetch to engine-q * Fix check for path as a string * Add a timeout flag and fix some span issues * Add a temporary fetch command that returns byte streams. Got rid of async stuff as we're using the blocking feature of tokio * More tweaks for the bytestream * Rewrite fetch using ByteStreams * buffer read on bytes directly Co-authored-by: Stefan Stanciulescu <contact@stefanstanciulescu.com>
2022-01-04 03:01:18 +01:00
"bytes",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"libc",
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"mio",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"num_cpus",
Updating polars and sqlparser versions (#10114) Polars and SQLParser upgrade. I have exposed features that have been added to polars as command args where appropriate. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: sholderbach <sholderbach@users.noreply.github.com>
2023-08-30 00:13:34 +02:00
"parking_lot",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"pin-project-lite",
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
"signal-hook-registry",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"socket2 0.5.5",
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
"tokio-macros",
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
"windows-sys 0.48.0",
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
]
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
[[package]]
name = "tokio-macros"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "2.2.0"
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "5b8a1e28f2deaa14e508979454cb3a223b10b938b45af148bc0986de36f1923b"
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
dependencies = [
"proc-macro2",
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
Add unit tests for HTTP commands. (#8267) # Description Following the comment from @fdncred: https://github.com/nushell/nushell/pull/8144#issuecomment-1442514338. I added some unit tests for HTTP commands. The tests are not exhaustive, but at least, this is a first good step IMO. # User-Facing Changes None. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-02 20:05:18 +01:00
]
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
[[package]]
name = "tokio-util"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.7.10"
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "5419f34732d9eb6ee4c3578b7989078579b7f039cbbb9ca2c4da015749371e15"
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
dependencies = [
Port fetch (with fixes) (#660) * Port fetch to engine-q * Fix check for path as a string * Add a timeout flag and fix some span issues * Add a temporary fetch command that returns byte streams. Got rid of async stuff as we're using the blocking feature of tokio * More tweaks for the bytestream * Rewrite fetch using ByteStreams * buffer read on bytes directly Co-authored-by: Stefan Stanciulescu <contact@stefanstanciulescu.com>
2022-01-04 03:01:18 +01:00
"bytes",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"futures-core",
"futures-sink",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"pin-project-lite",
"tokio",
updated cargo.lock with cargo update (#5201)
2022-04-15 13:04:15 +02:00
"tracing",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
]
Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command (#7990) # Description Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command # Tests + Formatting Added two tests to support the toml upgrade. - `cargo test --package nu-command --lib -- formats::from::toml::tests --nocapture` Executed all tests. - `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-06 21:15:14 +01:00
[[package]]
name = "toml"
Bump toml from 0.7.6 to 0.8.0 (#10408) Bumps [toml](https://github.com/toml-rs/toml) from 0.7.6 to 0.8.0. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/toml-rs/toml/commit/310f6ee9c5e80dd6da545d400b358b1bd5895dd4"><code>310f6ee</code></a> chore: Release</li> <li><a href="https://github.com/toml-rs/toml/commit/90da8bc4254152c4a783a098e09c8ac341dc60c7"><code>90da8bc</code></a> docs: Update changelog</li> <li><a href="https://github.com/toml-rs/toml/commit/f3e120f1a052af5ec31a4577138a914e76a52f33"><code>f3e120f</code></a> Merge pull request <a href="https://redirect.github.com/toml-rs/toml/issues/608">#608</a> from epage/enum</li> <li><a href="https://github.com/toml-rs/toml/commit/58a7101f68ecacc7de1f711f1c25c7ea458c9fdd"><code>58a7101</code></a> fix(serde): Support struct variants as table of a table</li> <li><a href="https://github.com/toml-rs/toml/commit/88a4dba3123600016b2388439750198b6c57db13"><code>88a4dba</code></a> fix(serde): Support tuple variants as table of an array</li> <li><a href="https://github.com/toml-rs/toml/commit/cf06b83424921c7ca902bba9fa18d66088af764d"><code>cf06b83</code></a> test(serde): Verify both Table and Value serializers</li> <li><a href="https://github.com/toml-rs/toml/commit/4ffa44ec16155fa73120538eb993dd489552f3ea"><code>4ffa44e</code></a> test(serde): Make parameter order more consistent</li> <li><a href="https://github.com/toml-rs/toml/commit/2b7c34c900aa2622660af495e126a75b71916cba"><code>2b7c34c</code></a> test(serde): Focus on string serialization first</li> <li><a href="https://github.com/toml-rs/toml/commit/e2a6a1ceceb87e222ab1ed13309948157a4492d1"><code>e2a6a1c</code></a> test(serde): Verify existing variant behavior</li> <li><a href="https://github.com/toml-rs/toml/commit/3f3e8329bb205f889dfbf02c2ccabc4d784271a3"><code>3f3e832</code></a> chore: Release</li> <li>Additional commits viewable in <a href="https://github.com/toml-rs/toml/compare/toml-v0.7.6...toml-v0.8.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=toml&package-manager=cargo&previous-version=0.7.6&new-version=0.8.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-09-18 07:50:30 +02:00
version = "0.7.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dd79e69d3b627db300ff956027cc6c3798cef26d22526befdfcd12feeb6d2257"
dependencies = [
"serde",
"serde_spanned",
"toml_datetime",
"toml_edit 0.19.15",
]
[[package]]
name = "toml"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.8.8"
Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command (#7990) # Description Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command # Tests + Formatting Added two tests to support the toml upgrade. - `cargo test --package nu-command --lib -- formats::from::toml::tests --nocapture` Executed all tests. - `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-06 21:15:14 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "a1a195ec8c9da26928f773888e0742ca3ca1040c6cd859c919c9f59c1954ab35"
Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command (#7990) # Description Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command # Tests + Formatting Added two tests to support the toml upgrade. - `cargo test --package nu-command --lib -- formats::from::toml::tests --nocapture` Executed all tests. - `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-06 21:15:14 +01:00
dependencies = [
"serde",
"serde_spanned",
"toml_datetime",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"toml_edit 0.21.0",
Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command (#7990) # Description Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command # Tests + Formatting Added two tests to support the toml upgrade. - `cargo test --package nu-command --lib -- formats::from::toml::tests --nocapture` Executed all tests. - `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-06 21:15:14 +01:00
]
[[package]]
name = "toml_datetime"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.6.5"
Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command (#7990) # Description Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command # Tests + Formatting Added two tests to support the toml upgrade. - `cargo test --package nu-command --lib -- formats::from::toml::tests --nocapture` Executed all tests. - `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-06 21:15:14 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "3550f4e9685620ac18a50ed434eb3aec30db8ba93b0287467bca5826ea25baf1"
Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command (#7990) # Description Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command # Tests + Formatting Added two tests to support the toml upgrade. - `cargo test --package nu-command --lib -- formats::from::toml::tests --nocapture` Executed all tests. - `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-06 21:15:14 +01:00
dependencies = [
"serde",
]
[[package]]
name = "toml_edit"
Bump toml from 0.7.6 to 0.8.0 (#10408) Bumps [toml](https://github.com/toml-rs/toml) from 0.7.6 to 0.8.0. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/toml-rs/toml/commit/310f6ee9c5e80dd6da545d400b358b1bd5895dd4"><code>310f6ee</code></a> chore: Release</li> <li><a href="https://github.com/toml-rs/toml/commit/90da8bc4254152c4a783a098e09c8ac341dc60c7"><code>90da8bc</code></a> docs: Update changelog</li> <li><a href="https://github.com/toml-rs/toml/commit/f3e120f1a052af5ec31a4577138a914e76a52f33"><code>f3e120f</code></a> Merge pull request <a href="https://redirect.github.com/toml-rs/toml/issues/608">#608</a> from epage/enum</li> <li><a href="https://github.com/toml-rs/toml/commit/58a7101f68ecacc7de1f711f1c25c7ea458c9fdd"><code>58a7101</code></a> fix(serde): Support struct variants as table of a table</li> <li><a href="https://github.com/toml-rs/toml/commit/88a4dba3123600016b2388439750198b6c57db13"><code>88a4dba</code></a> fix(serde): Support tuple variants as table of an array</li> <li><a href="https://github.com/toml-rs/toml/commit/cf06b83424921c7ca902bba9fa18d66088af764d"><code>cf06b83</code></a> test(serde): Verify both Table and Value serializers</li> <li><a href="https://github.com/toml-rs/toml/commit/4ffa44ec16155fa73120538eb993dd489552f3ea"><code>4ffa44e</code></a> test(serde): Make parameter order more consistent</li> <li><a href="https://github.com/toml-rs/toml/commit/2b7c34c900aa2622660af495e126a75b71916cba"><code>2b7c34c</code></a> test(serde): Focus on string serialization first</li> <li><a href="https://github.com/toml-rs/toml/commit/e2a6a1ceceb87e222ab1ed13309948157a4492d1"><code>e2a6a1c</code></a> test(serde): Verify existing variant behavior</li> <li><a href="https://github.com/toml-rs/toml/commit/3f3e8329bb205f889dfbf02c2ccabc4d784271a3"><code>3f3e832</code></a> chore: Release</li> <li>Additional commits viewable in <a href="https://github.com/toml-rs/toml/compare/toml-v0.7.6...toml-v0.8.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=toml&package-manager=cargo&previous-version=0.7.6&new-version=0.8.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-09-18 07:50:30 +02:00
version = "0.19.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1b5bb770da30e5cbfde35a2d7b9b8a2c4b8ef89548a7a6aeab5c9a576e3e7421"
dependencies = [
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"indexmap",
Bump toml from 0.7.6 to 0.8.0 (#10408) Bumps [toml](https://github.com/toml-rs/toml) from 0.7.6 to 0.8.0. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/toml-rs/toml/commit/310f6ee9c5e80dd6da545d400b358b1bd5895dd4"><code>310f6ee</code></a> chore: Release</li> <li><a href="https://github.com/toml-rs/toml/commit/90da8bc4254152c4a783a098e09c8ac341dc60c7"><code>90da8bc</code></a> docs: Update changelog</li> <li><a href="https://github.com/toml-rs/toml/commit/f3e120f1a052af5ec31a4577138a914e76a52f33"><code>f3e120f</code></a> Merge pull request <a href="https://redirect.github.com/toml-rs/toml/issues/608">#608</a> from epage/enum</li> <li><a href="https://github.com/toml-rs/toml/commit/58a7101f68ecacc7de1f711f1c25c7ea458c9fdd"><code>58a7101</code></a> fix(serde): Support struct variants as table of a table</li> <li><a href="https://github.com/toml-rs/toml/commit/88a4dba3123600016b2388439750198b6c57db13"><code>88a4dba</code></a> fix(serde): Support tuple variants as table of an array</li> <li><a href="https://github.com/toml-rs/toml/commit/cf06b83424921c7ca902bba9fa18d66088af764d"><code>cf06b83</code></a> test(serde): Verify both Table and Value serializers</li> <li><a href="https://github.com/toml-rs/toml/commit/4ffa44ec16155fa73120538eb993dd489552f3ea"><code>4ffa44e</code></a> test(serde): Make parameter order more consistent</li> <li><a href="https://github.com/toml-rs/toml/commit/2b7c34c900aa2622660af495e126a75b71916cba"><code>2b7c34c</code></a> test(serde): Focus on string serialization first</li> <li><a href="https://github.com/toml-rs/toml/commit/e2a6a1ceceb87e222ab1ed13309948157a4492d1"><code>e2a6a1c</code></a> test(serde): Verify existing variant behavior</li> <li><a href="https://github.com/toml-rs/toml/commit/3f3e8329bb205f889dfbf02c2ccabc4d784271a3"><code>3f3e832</code></a> chore: Release</li> <li>Additional commits viewable in <a href="https://github.com/toml-rs/toml/compare/toml-v0.7.6...toml-v0.8.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=toml&package-manager=cargo&previous-version=0.7.6&new-version=0.8.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-09-18 07:50:30 +02:00
"serde",
"serde_spanned",
"toml_datetime",
"winnow",
]
[[package]]
name = "toml_edit"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.21.0"
Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command (#7990) # Description Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command # Tests + Formatting Added two tests to support the toml upgrade. - `cargo test --package nu-command --lib -- formats::from::toml::tests --nocapture` Executed all tests. - `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-06 21:15:14 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "d34d383cd00a163b4a5b85053df514d45bc330f6de7737edfe0a93311d1eaa03"
Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command (#7990) # Description Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command # Tests + Formatting Added two tests to support the toml upgrade. - `cargo test --package nu-command --lib -- formats::from::toml::tests --nocapture` Executed all tests. - `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-06 21:15:14 +01:00
dependencies = [
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"indexmap",
Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command (#7990) # Description Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command # Tests + Formatting Added two tests to support the toml upgrade. - `cargo test --package nu-command --lib -- formats::from::toml::tests --nocapture` Executed all tests. - `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-06 21:15:14 +01:00
"serde",
"serde_spanned",
"toml_datetime",
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
"winnow",
Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command (#7990) # Description Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command # Tests + Formatting Added two tests to support the toml upgrade. - `cargo test --package nu-command --lib -- formats::from::toml::tests --nocapture` Executed all tests. - `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-06 21:15:14 +01:00
]
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
[[package]]
name = "tower-service"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
version = "0.3.2"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
checksum = "b6bc1c9ce2b5135ac7f93c72918fc37feb872bdc6a5533a8b85eb4b86bfdae52"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
[[package]]
name = "tracing"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.1.40"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "c3523ab5a71916ccf420eebdf5521fcef02141234bbc0b8a49f2fdc4544364ef"
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
dependencies = [
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"pin-project-lite",
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
"tracing-core",
]
[[package]]
name = "tracing-core"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.1.32"
Revert "Unify use of the `surf` crate (#3855)" (#3871) This reverts commit 7f7af2bbaa90332377a9eea63e4e7e78cb834694.
2021-07-30 23:04:01 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "c06d3da6113f116aaee68e4d601191614c9053067f9ab7f6edbcb161237daa54"
Revert "Unify use of the `surf` crate (#3855)" (#3871) This reverts commit 7f7af2bbaa90332377a9eea63e4e7e78cb834694.
2021-07-30 23:04:01 +02:00
dependencies = [
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
"once_cell",
Revert "Unify use of the `surf` crate (#3855)" (#3871) This reverts commit 7f7af2bbaa90332377a9eea63e4e7e78cb834694.
2021-07-30 23:04:01 +02:00
]
#194 Added trash crate and send files to the trash using a flag
2019-10-19 00:41:24 +02:00
[[package]]
name = "trash"
updates `trash` dependency to 3.1.2 (#10965) # Description This PR updates the trash dependency from 3.1.0 to 3.1.2 for better support on FreeBSD. closes #10961 # 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-11-05 22:00:13 +01:00
version = "3.1.2"
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
updates `trash` dependency to 3.1.2 (#10965) # Description This PR updates the trash dependency from 3.1.0 to 3.1.2 for better support on FreeBSD. closes #10961 # 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-11-05 22:00:13 +01:00
checksum = "8c646008e5144d988005bec12b1e56f5e0a951e957176686815eba8b025e0418"
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
dependencies = [
Remove 'arboard' (#4174)
2021-12-01 20:48:03 +01:00
"chrono",
"libc",
"log",
"objc",
merge main
2022-02-08 14:28:21 +01:00
"once_cell",
Remove 'arboard' (#4174)
2021-12-01 20:48:03 +01:00
"scopeguard",
"url",
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
"windows 0.44.0",
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
]
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
[[package]]
name = "try-lock"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "0.2.5"
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "e421abadd41a4225275504ea4d6566923418b7f05506fbc9c0fe86ba7396114b"
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
Bar Chart baseline. (#2621) Bar Chart ready.
2020-09-30 20:27:52 +02:00
[[package]]
--no-edit
2019-11-04 16:47:03 +01:00
name = "typed-arena"
version = "1.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
checksum = "a9b2228007eba4120145f785df0f6c92ea538f5a3635a612ecf4e334c8c1446d"
--no-edit
2019-11-04 16:47:03 +01:00
add some battery stats
2019-08-11 05:01:09 +02:00
[[package]]
name = "typenum"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.17.0"
add some battery stats
2019-08-11 05:01:09 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "42ff0bf0c66b8238c6f3b578df37d0b7848e55df8577b3f74f92a69acceeb825"
WIP
2021-10-25 06:01:02 +02:00
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
[[package]]
name = "typetag"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "0.2.14"
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "196976efd4a62737b3a2b662cda76efb448d099b1049613d7a5d72743c611ce0"
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
dependencies = [
"erased-serde",
"inventory",
"once_cell",
"serde",
"typetag-impl",
]
[[package]]
name = "typetag-impl"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "0.2.14"
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "2eea6765137e2414c44c7b1e07c73965a118a72c46148e1e168b3fc9d3ccf3aa"
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
dependencies = [
"proc-macro2",
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
]
add some battery stats
2019-08-11 05:01:09 +02:00
allow parsing of human readable datetimes (#11051) # Description This PR adds the ability to parse human readable datetime strings as part of the `into datetime` command. I added a new `-n`/`--list-human` parameter that produces this list to give the user an idea of what is supported. ```nushell ❯ into datetime --list-human ╭#─┬parseable human datetime examples┬───result───╮ │0 │Today 18:30 │in 8 hours │ │1 │2022-11-07 13:25:30 │a year ago │ │2 │15:20 Friday │in 3 days │ │3 │This Friday 17:00 │in 3 days │ │4 │13:25, Next Tuesday │in a week │ │5 │Last Friday at 19:45 │3 days ago │ │6 │In 3 days │in 2 days │ │7 │In 2 hours │in 2 hours │ │8 │10 hours and 5 minutes ago │10 hours ago│ │9 │1 years ago │a year ago │ │10│A year ago │a year ago │ │11│A month ago │a month ago │ │12│A week ago │a week ago │ │13│A day ago │a day ago │ │14│An hour ago │an hour ago │ │15│A minute ago │a minute ago│ │16│A second ago │now │ │17│Now │now │ ╰#─┴parseable human datetime examples┴───result───╯ ``` Or with `$env.config.datetime_format.table` set. ```nushell ❯ into datetime --list-human ╭#─┬parseable human datetime examples┬──────result───────╮ │0 │Today 18:30 │11/14/23 06:30:00PM│ │1 │2022-11-07 13:25:30 │11/07/22 01:25:30PM│ │2 │15:20 Friday │11/17/23 03:20:00PM│ │3 │This Friday 17:00 │11/17/23 05:00:00PM│ │4 │13:25, Next Tuesday │11/21/23 01:25:00PM│ │5 │Last Friday at 19:45 │11/10/23 07:45:00PM│ │6 │In 3 days │11/17/23 10:12:54AM│ │7 │In 2 hours │11/14/23 12:12:54PM│ │8 │10 hours and 5 minutes ago │11/14/23 12:07:54AM│ │9 │1 years ago │11/13/22 10:12:54AM│ │10│A year ago │11/13/22 10:12:54AM│ │11│A month ago │10/15/23 11:12:54AM│ │12│A week ago │11/07/23 10:12:54AM│ │13│A day ago │11/13/23 10:12:54AM│ │14│An hour ago │11/14/23 09:12:54AM│ │15│A minute ago │11/14/23 10:11:54AM│ │16│A second ago │11/14/23 10:12:53AM│ │17│Now │11/14/23 10:12:54AM│ ╰#─┴parseable human datetime examples┴──────result───────╯ ``` # 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-11-16 00:43:37 +01:00
[[package]]
name = "ucd-trie"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ed646292ffc8188ef8ea4d1e0e0150fb15a5c2e12ad9b8fc191ae7a8a7f3c4b9"
Add umask to unix --full list
2019-11-19 06:46:47 +01:00
[[package]]
name = "umask"
Bump umask from 2.0.0 to 2.1.0 (#8835)
2023-04-14 14:15:22 +02:00
version = "2.1.0"
Add umask to unix --full list
2019-11-19 06:46:47 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump umask from 2.0.0 to 2.1.0 (#8835)
2023-04-14 14:15:22 +02:00
checksum = "ec9a46c2549e35c054e0ffe281a3a6ec0007793db4df106604d37ed3f4d73d1c"
dependencies = [
"thiserror",
]
Add umask to unix --full list
2019-11-19 06:46:47 +01:00
add `--mime-type(-m)` to `ls` in the `type` column (#7616) # Description This PR adds the `mime-type` to the `type` column if you add the `--mime-type(-m)` flag to `ls`. <img width="853" alt="Screenshot 2022-12-27 at 11 43 20 AM" src="https://user-images.githubusercontent.com/343840/209705499-27fe40fe-0356-4d9d-97f2-4b2dc52e0963.png"> <img width="781" alt="Screenshot 2022-12-27 at 11 45 53 AM" src="https://user-images.githubusercontent.com/343840/209705509-4d677389-fd68-401e-a7af-3fc6052743b6.png"> # User-Facing Changes If you specify the `-m` flag, you get the "guessed at" mime type. The guess is based on the file name and uses this crate https://docs.rs/mime_guess/latest/mime_guess/ for the guessing. Part of issue #7612 and and #7524 There's some debate on if the `mime-type` should be added to the `type` column or if there should be a separate `mime` column. I tend to lean on the side of `type` since it's technically a type and it's only in that column if you ask it to be there. Also, I'd prefer to reuse a column rather than having a list of sprawling columns. Also, as @KodiCraft suggested, there is precedence as with `ls -d` where the summed size is in the size column. I could go either way and if someone wants to create a `mime` column, we'd probably accept it. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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.
2022-12-27 19:46:23 +01:00
[[package]]
name = "unicase"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "2.7.0"
add `--mime-type(-m)` to `ls` in the `type` column (#7616) # Description This PR adds the `mime-type` to the `type` column if you add the `--mime-type(-m)` flag to `ls`. <img width="853" alt="Screenshot 2022-12-27 at 11 43 20 AM" src="https://user-images.githubusercontent.com/343840/209705499-27fe40fe-0356-4d9d-97f2-4b2dc52e0963.png"> <img width="781" alt="Screenshot 2022-12-27 at 11 45 53 AM" src="https://user-images.githubusercontent.com/343840/209705509-4d677389-fd68-401e-a7af-3fc6052743b6.png"> # User-Facing Changes If you specify the `-m` flag, you get the "guessed at" mime type. The guess is based on the file name and uses this crate https://docs.rs/mime_guess/latest/mime_guess/ for the guessing. Part of issue #7612 and and #7524 There's some debate on if the `mime-type` should be added to the `type` column or if there should be a separate `mime` column. I tend to lean on the side of `type` since it's technically a type and it's only in that column if you ask it to be there. Also, I'd prefer to reuse a column rather than having a list of sprawling columns. Also, as @KodiCraft suggested, there is precedence as with `ls -d` where the summed size is in the size column. I could go either way and if someone wants to create a `mime` column, we'd probably accept it. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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.
2022-12-27 19:46:23 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "f7d2d4dafb69621809a81864c9c1b864479e1235c0dd4e199924b9742439ed89"
add `--mime-type(-m)` to `ls` in the `type` column (#7616) # Description This PR adds the `mime-type` to the `type` column if you add the `--mime-type(-m)` flag to `ls`. <img width="853" alt="Screenshot 2022-12-27 at 11 43 20 AM" src="https://user-images.githubusercontent.com/343840/209705499-27fe40fe-0356-4d9d-97f2-4b2dc52e0963.png"> <img width="781" alt="Screenshot 2022-12-27 at 11 45 53 AM" src="https://user-images.githubusercontent.com/343840/209705509-4d677389-fd68-401e-a7af-3fc6052743b6.png"> # User-Facing Changes If you specify the `-m` flag, you get the "guessed at" mime type. The guess is based on the file name and uses this crate https://docs.rs/mime_guess/latest/mime_guess/ for the guessing. Part of issue #7612 and and #7524 There's some debate on if the `mime-type` should be added to the `type` column or if there should be a separate `mime` column. I tend to lean on the side of `type` since it's technically a type and it's only in that column if you ask it to be there. Also, I'd prefer to reuse a column rather than having a list of sprawling columns. Also, as @KodiCraft suggested, there is precedence as with `ls -d` where the summed size is in the size column. I could go either way and if someone wants to create a `mime` column, we'd probably accept it. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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.
2022-12-27 19:46:23 +01:00
dependencies = [
"version_check",
Add opening urls
2019-06-08 20:09:17 +02:00
]
Add git branch to prompt
2019-06-01 23:11:28 +02:00
[[package]]
name = "unicode-bidi"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "0.3.14"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "6f2528f27a9eb2b21e69c95319b30bd0efd85d09c379741b0f78ea1d86be2416"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
[[package]]
name = "unicode-ident"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "1.0.12"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "3354b9ac3fae1ff6755cb6db53683adb661634f67557942dea4facebec0fee4b"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
[[package]]
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
name = "unicode-linebreak"
Update `unicode-linebreak` to `0.1.5` (#9814) # Description This deduplicates `ahash` as it was previously an outdated build-dependency of `unicode-linebreak` Should provide a small benefit to initial from scratch compile. # User-Facing Changes None
2023-07-30 22:17:36 +02:00
version = "0.1.5"
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `unicode-linebreak` to `0.1.5` (#9814) # Description This deduplicates `ahash` as it was previously an outdated build-dependency of `unicode-linebreak` Should provide a small benefit to initial from scratch compile. # User-Facing Changes None
2023-07-30 22:17:36 +02:00
checksum = "3b09c83c3c29d37506a3e260c08c03743a6bb66a9cd432c6934ab501a190571f"
replace codespan-reporting with miette 3.0
2021-09-20 23:37:26 +02:00
introducing `gstat`, a new command to get the git status (#443) * wip - preliminary checking * updated to latest pluging * i think it's all working now, except bare words * clippy
2021-12-06 18:28:11 +01:00
[[package]]
Add git branch to prompt
2019-06-01 23:11:28 +02:00
name = "unicode-normalization"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
version = "0.1.22"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
checksum = "5c5713f0fc4b5db668a2ac63cdb7bb4469d8c9fed047b1d0292cc7b0ce2ba921"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
dependencies = [
Make mode subcommand: math mode (#2043) * Update calculate to return a table when Value is a table * impl mode subcommand for math * add tests for math mode subcommand * add table/row tests for math mode subcommand * fix formatting
2020-06-24 19:57:27 +02:00
"tinyvec",
Add git branch to prompt
2019-06-01 23:11:28 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "unicode-segmentation"
`string | fill` counts clusters, not graphemes; and doesn't count ANSI escape codes (#8134) Enhancement of new `fill` command (#7846) to handle content including ANSI escape codes for formatting or multi-code-point Unicode grapheme clusters. In both of these cases, the content is (many) bytes longer than its visible length, and `fill` was counting the extra bytes so not adding enough fill characters. # Description This script: ```rust # the teacher emoji `\u{1F9D1}\u{200D}\u{1F3EB}` is 3 code points, but only 1 print position wide. echo "This output should be 3 print positions wide, with leading and trailing `+`" $"\u{1F9D1}\u{200D}\u{1F3EB}" | fill -c "+" -w 3 -a "c" echo "This output should be 3 print positions wide, with leading and trailing `+`" $"(ansi green)a(ansi reset)" | fill -c "+" -w 3 -a c echo "" ``` Was producing this output: ```rust This output should be 3 print positions wide, with leading and trailing `+` 🧑‍🏫 This output should be 3 print positions wide, with leading and trailing `+` a ``` After this PR, it produces this output: ```rust This output should be 3 print positions wide, with leading and trailing `+` +🧑‍🏫+ This output should be 3 print positions wide, with leading and trailing `+` +a+ ``` # User-Facing Changes Users may have to undo fixes they may have introduced to work around the former behavior. I have one such in my prompt string that I can now revert. # Tests + Formatting Don't forget to add tests that cover your changes. -- Done Make sure you've run and fixed any issues with these commands: - [x] `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [x] `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - [x] `cargo test --workspace` to check that all tests pass # After Submitting `fill` command not documented in the book, and it still talks about `str lpad/rpad`. I'll fix. Note added dependency on a new library `print-positions`, which is an iterator that yields a complete print position (cluster + Ansi sequence) per call. Should this be vendored?
2023-02-20 13:32:20 +01:00
version = "1.10.1"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
`string | fill` counts clusters, not graphemes; and doesn't count ANSI escape codes (#8134) Enhancement of new `fill` command (#7846) to handle content including ANSI escape codes for formatting or multi-code-point Unicode grapheme clusters. In both of these cases, the content is (many) bytes longer than its visible length, and `fill` was counting the extra bytes so not adding enough fill characters. # Description This script: ```rust # the teacher emoji `\u{1F9D1}\u{200D}\u{1F3EB}` is 3 code points, but only 1 print position wide. echo "This output should be 3 print positions wide, with leading and trailing `+`" $"\u{1F9D1}\u{200D}\u{1F3EB}" | fill -c "+" -w 3 -a "c" echo "This output should be 3 print positions wide, with leading and trailing `+`" $"(ansi green)a(ansi reset)" | fill -c "+" -w 3 -a c echo "" ``` Was producing this output: ```rust This output should be 3 print positions wide, with leading and trailing `+` 🧑‍🏫 This output should be 3 print positions wide, with leading and trailing `+` a ``` After this PR, it produces this output: ```rust This output should be 3 print positions wide, with leading and trailing `+` +🧑‍🏫+ This output should be 3 print positions wide, with leading and trailing `+` +a+ ``` # User-Facing Changes Users may have to undo fixes they may have introduced to work around the former behavior. I have one such in my prompt string that I can now revert. # Tests + Formatting Don't forget to add tests that cover your changes. -- Done Make sure you've run and fixed any issues with these commands: - [x] `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [x] `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - [x] `cargo test --workspace` to check that all tests pass # After Submitting `fill` command not documented in the book, and it still talks about `str lpad/rpad`. I'll fix. Note added dependency on a new library `print-positions`, which is an iterator that yields a complete print position (cluster + Ansi sequence) per call. Should this be vendored?
2023-02-20 13:32:20 +01:00
checksum = "1dd624098567895118886609431a7c3b8f516e41d30e0643f03d94592a147e36"
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "unicode-width"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.1.11"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "e51733f11c9c4f72aa0c160008246859e340b00807569a0da0e7a1079b27ba85"
objectshell initial commit
2019-05-10 18:59:12 +02:00
bump deps
2019-07-29 09:46:24 +02:00
[[package]]
name = "unicode-xid"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
version = "0.2.4"
bump deps
2019-07-29 09:46:24 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
checksum = "f962df74c8c05a667b5ee8bcf162993134c104e96440b663c8daa176dc772d8c"
bump deps
2019-07-29 09:46:24 +02:00
update a few nushell dependencies (#6291) * update a few nushell dependencies * update a test
2022-08-10 21:56:15 +02:00
[[package]]
name = "unsafe-libyaml"
Bump unsafe-libyaml from 0.2.9 to 0.2.10 (#11391)
2023-12-21 19:49:12 +01:00
version = "0.2.10"
update a few nushell dependencies (#6291) * update a few nushell dependencies * update a test
2022-08-10 21:56:15 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump unsafe-libyaml from 0.2.9 to 0.2.10 (#11391)
2023-12-21 19:49:12 +01:00
checksum = "ab4c90930b95a82d00dc9e9ac071b4991924390d46cbd0dfe566148667605e4b"
update a few nushell dependencies (#6291) * update a few nushell dependencies * update a test
2022-08-10 21:56:15 +02:00
changes Reqwest to Ureq. (#8320) # Description _(Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes.)_ This pull request removes `Reqwest` and replaces it with `Ureq` to remove some of our dependencies, giving us faster compile times as well as smaller binaries. `Ureq` does not have an async runtime included so we do not need build heavy dependencies such as `Tokio`. From older tests I had the number of build units be reduced from `430 -> 392`. The default of `Ureq` uses `Rustls` but it has been configured to instead use `native_tls` which should work exactly the same as the `tls` works now. I removed `content-length` from the http commands as after refactoring i did not see a reason to have it available, correct me if this is something we should preserve. In the medium, to long term, we should maybe consider changing to `rustls` to have the same `tls` on all platforms. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-05 23:48:13 +01:00
[[package]]
name = "ureq"
Bump ureq from 2.8.0 to 2.9.1 (#11163)
2023-11-29 18:48:18 +01:00
version = "2.9.1"
changes Reqwest to Ureq. (#8320) # Description _(Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes.)_ This pull request removes `Reqwest` and replaces it with `Ureq` to remove some of our dependencies, giving us faster compile times as well as smaller binaries. `Ureq` does not have an async runtime included so we do not need build heavy dependencies such as `Tokio`. From older tests I had the number of build units be reduced from `430 -> 392`. The default of `Ureq` uses `Rustls` but it has been configured to instead use `native_tls` which should work exactly the same as the `tls` works now. I removed `content-length` from the http commands as after refactoring i did not see a reason to have it available, correct me if this is something we should preserve. In the medium, to long term, we should maybe consider changing to `rustls` to have the same `tls` on all platforms. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-05 23:48:13 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump ureq from 2.8.0 to 2.9.1 (#11163)
2023-11-29 18:48:18 +01:00
checksum = "f8cdd25c339e200129fe4de81451814e5228c9b771d57378817d6117cc2b3f97"
changes Reqwest to Ureq. (#8320) # Description _(Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes.)_ This pull request removes `Reqwest` and replaces it with `Ureq` to remove some of our dependencies, giving us faster compile times as well as smaller binaries. `Ureq` does not have an async runtime included so we do not need build heavy dependencies such as `Tokio`. From older tests I had the number of build units be reduced from `430 -> 392`. The default of `Ureq` uses `Rustls` but it has been configured to instead use `native_tls` which should work exactly the same as the `tls` works now. I removed `content-length` from the http commands as after refactoring i did not see a reason to have it available, correct me if this is something we should preserve. In the medium, to long term, we should maybe consider changing to `rustls` to have the same `tls` on all platforms. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-05 23:48:13 +01:00
dependencies = [
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
"base64 0.21.5",
changes Reqwest to Ureq. (#8320) # Description _(Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes.)_ This pull request removes `Reqwest` and replaces it with `Ureq` to remove some of our dependencies, giving us faster compile times as well as smaller binaries. `Ureq` does not have an async runtime included so we do not need build heavy dependencies such as `Tokio`. From older tests I had the number of build units be reduced from `430 -> 392`. The default of `Ureq` uses `Rustls` but it has been configured to instead use `native_tls` which should work exactly the same as the `tls` works now. I removed `content-length` from the http commands as after refactoring i did not see a reason to have it available, correct me if this is something we should preserve. In the medium, to long term, we should maybe consider changing to `rustls` to have the same `tls` on all platforms. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-03-05 23:48:13 +01:00
"encoding_rs",
"flate2",
"log",
"native-tls",
"once_cell",
"serde",
"serde_json",
"url",
]
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
[[package]]
name = "url"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "2.5.0"
bump deps
2019-07-29 09:46:24 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "31e6302e3bb753d46e83516cae55ae196fc0c309407cf11ab35cc51a4c2a4633"
bump deps
2019-07-29 09:46:24 +02:00
dependencies = [
Fix new clippy warnings (#2760) * Fix new clippy warnings * Fork serde-hjson and bring in * Fork serde-hjson and bring in * Fix clippy lint again
2020-11-22 01:37:16 +01:00
"form_urlencoded",
"idna",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"percent-encoding",
Integrated Language Server (#10723) # Description This commit integrates a language server into nushell so that IDEs don't have to convert CLI option back and forth. - fixes https://github.com/nushell/vscode-nushell-lang/issues/117 - fixes https://github.com/jokeyrhyme/nuls/issues/8 Tracking tasks - [x] [textDocument/hover](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover) -> `nu --ide-hover` - [x] [textDocument/completion](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion) -> `nu --ide-complete` - [x] [textDocument/definition](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition) -> `nu --ide-goto-def` - ~~[ ] [textDocument/didChange](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didChange), [textDocument/didClose](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didClose), and [textDocument/didOpen](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_didOpen)~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/inlayHint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [textDocument/publishDiagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) -> `nu --ide-check`~~ (will be done in a follow-up PR) - ~~[ ] [workspace/configuration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration)~~ (will be done in a follow-up PR) - ~~[ ] [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfiguration)~~ (will be done in a follow-up PR) # User-Facing Changes The command line options `--lsp` will start a LSP server. # 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-11-02 16:18:57 +01:00
"serde",
bump deps
2019-07-29 09:46:24 +02:00
]
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
[[package]]
name = "utf-8"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
version = "0.7.6"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
checksum = "09cc8ee72d2a9becf2f2febe0205bbed8fc6615b7cb429ad062dc7b7ddd036a9"
web scraping with css selectors (#2725) * first step of making selector * wip * wip tests working * probably good enough for a first pass * oops, missed something. * and something else... * grrrr version errors
2020-11-03 22:46:42 +01:00
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
[[package]]
name = "utf8-width"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.1.7"
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "86bd8d4e895da8537e5315b8254664e6b769c4ff3db18321b297a1e7004392e3"
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
Bump a lot of deps (#1560)
2020-04-07 09:51:17 +02:00
[[package]]
name = "utf8parse"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
version = "0.2.1"
Bump a lot of deps (#1560)
2020-04-07 09:51:17 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
checksum = "711b9620af191e0cdc7468a8d14e709c3dcdb115b36f838e601583af800a370a"
Bump a lot of deps (#1560)
2020-04-07 09:51:17 +02:00
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
[[package]]
name = "uu_cp"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.0.23"
Pin `uu_cp` to the `0.0.22` release. (#10725)
2023-10-15 21:19:34 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "4c8e090cfcfa51cb224d247e05938d25718a7203c6f8c0f0de7b3b031d99dcea"
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
dependencies = [
"clap",
"filetime",
"indicatif",
"libc",
"quick-error 2.0.1",
"uucore",
"walkdir",
"xattr",
]
Add `umkdir` command (#10785) A `mkdir` command, which uses `uu_mkdir` as backend. close #10515.
2023-10-30 13:59:48 +01:00
[[package]]
name = "uu_mkdir"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.0.23"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dcbf657c9e738d16ebc5c161a611ff25327c1fb599645afb2831062efb23c851"
dependencies = [
"clap",
"uucore",
]
[[package]]
name = "uu_mktemp"
version = "0.0.23"
Add `umkdir` command (#10785) A `mkdir` command, which uses `uu_mkdir` as backend. close #10515.
2023-10-30 13:59:48 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "154531208d9ec160629bf9545a56ad9df38e964e547e0a17ee9d75aeec9831cb"
Add `umkdir` command (#10785) A `mkdir` command, which uses `uu_mkdir` as backend. close #10515.
2023-10-30 13:59:48 +01:00
dependencies = [
"clap",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
"rand",
"tempfile",
Add `umkdir` command (#10785) A `mkdir` command, which uses `uu_mkdir` as backend. close #10515.
2023-10-30 13:59:48 +01:00
"uucore",
]
implement whoami using uutils (#10488) <!-- 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. --> Implements `whoami` using the `whoami` command from uutils as backend. This is a draft because it depends on https://github.com/uutils/coreutils/pull/5310 and a new release of uutils needs to be made (and the paths in `Cargo.toml` should be updated). At this point, this is more of a proof of concept 😄 Additionally, this implements a (simple and naive) conversion from the uutils `UResult` to the nushell `ShellError`, which should help with the integration of other utils, too. I can split that off into a separate PR if desired. I put this command in the "platform" category. If it should go somewhere else, let me know! The tests will currently fail, because I've used a local path to uutils. Once the PR on the uutils side is merged, I'll update it to a git path so that it can be tested and runs on more machines than just mine. # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> New `whoami` command. This might break some users who expect the system `whoami` command. However, the result of this new command should be very close, just with a nicer help message, at least for Linux users. The default `whoami` on Windows is quite different from this implementation: https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/whoami # 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-10-25 16:53:52 +02:00
[[package]]
name = "uu_whoami"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.0.23"
implement whoami using uutils (#10488) <!-- 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. --> Implements `whoami` using the `whoami` command from uutils as backend. This is a draft because it depends on https://github.com/uutils/coreutils/pull/5310 and a new release of uutils needs to be made (and the paths in `Cargo.toml` should be updated). At this point, this is more of a proof of concept 😄 Additionally, this implements a (simple and naive) conversion from the uutils `UResult` to the nushell `ShellError`, which should help with the integration of other utils, too. I can split that off into a separate PR if desired. I put this command in the "platform" category. If it should go somewhere else, let me know! The tests will currently fail, because I've used a local path to uutils. Once the PR on the uutils side is merged, I'll update it to a git path so that it can be tested and runs on more machines than just mine. # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> New `whoami` command. This might break some users who expect the system `whoami` command. However, the result of this new command should be very close, just with a nicer help message, at least for Linux users. The default `whoami` on Windows is quite different from this implementation: https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/whoami # 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-10-25 16:53:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "70589dc3b41f34cbfe1fb22b8f20fcac233fa4565409905f12dd06780b18374d"
implement whoami using uutils (#10488) <!-- 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. --> Implements `whoami` using the `whoami` command from uutils as backend. This is a draft because it depends on https://github.com/uutils/coreutils/pull/5310 and a new release of uutils needs to be made (and the paths in `Cargo.toml` should be updated). At this point, this is more of a proof of concept 😄 Additionally, this implements a (simple and naive) conversion from the uutils `UResult` to the nushell `ShellError`, which should help with the integration of other utils, too. I can split that off into a separate PR if desired. I put this command in the "platform" category. If it should go somewhere else, let me know! The tests will currently fail, because I've used a local path to uutils. Once the PR on the uutils side is merged, I'll update it to a git path so that it can be tested and runs on more machines than just mine. # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> New `whoami` command. This might break some users who expect the system `whoami` command. However, the result of this new command should be very close, just with a nicer help message, at least for Linux users. The default `whoami` on Windows is quite different from this implementation: https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/whoami # 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-10-25 16:53:52 +02:00
dependencies = [
"clap",
"libc",
"uucore",
"windows-sys 0.48.0",
]
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
[[package]]
name = "uucore"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.0.23"
Pin `uu_cp` to the `0.0.22` release. (#10725)
2023-10-15 21:19:34 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "068748c7f682cf123dc52c2dbfb61447214c27f5566bfe7cd7225156a39bf7f2"
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
dependencies = [
"clap",
"dunce",
"glob",
"libc",
rename nushell's cp command to cp-old making coreutils the default cp (#10678) # Description This PR renames nushell's `cp` command to `cp-old` to make room for `ucp` to be renamed to `cp`, making the coreutils version of `cp` the default for nushell. After some period of time, we should remove `cp-old` entirely. # 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-10-11 01:13:28 +02:00
"nix",
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
"once_cell",
"os_display",
"uucore_procs",
"walkdir",
"wild",
"winapi-util",
"windows-sys 0.48.0",
]
[[package]]
name = "uucore_procs"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.0.23"
Pin `uu_cp` to the `0.0.22` release. (#10725)
2023-10-15 21:19:34 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "de9aca849d872044129960e8ace8eaad30aa64bd0346a561b7aaace20f5fcd18"
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
dependencies = [
"proc-macro2",
"quote",
"uuhelp_parser",
]
[[package]]
name = "uuhelp_parser"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "0.0.23"
Pin `uu_cp` to the `0.0.22` release. (#10725)
2023-10-15 21:19:34 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "e269065dd0e7d561fb4c16fc0ef754c6da9333ccab08d6eda770dc6e2575aff0"
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
Adds random command with uuid subcommand (#2050)
2020-06-25 07:51:09 +02:00
[[package]]
name = "uuid"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "1.6.1"
Adds random command with uuid subcommand (#2050)
2020-06-25 07:51:09 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "5e395fcf16a7a3d8127ec99782007af141946b4795001f876d54fb0d55978560"
Adds random command with uuid subcommand (#2050)
2020-06-25 07:51:09 +02:00
dependencies = [
Bump scraper from 0.16.0 to 0.17.1 (#9638)
2023-07-10 07:28:36 +02:00
"getrandom",
Adds random command with uuid subcommand (#2050)
2020-06-25 07:51:09 +02:00
]
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
[[package]]
name = "value-trait"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.8.0"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "ea87257cfcbedcb9444eda79c59fdfea71217e6305afee8ee33f500375c2ac97"
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
dependencies = [
"float-cmp",
"halfbrown",
Bump scraper from 0.14.0 to 0.15.0 (#8331) Bumps [scraper](https://github.com/causal-agent/scraper) from 0.14.0 to 0.15.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/causal-agent/scraper/releases">scraper's releases</a>.</em></p> <blockquote> <h2>0.15.0</h2> <h2>What's Changed</h2> <ul> <li>Bump cssparser to 0.28 and selectors to 0.23. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li>Create dependabot.yml by <a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li>Re-export Element trait from selectors crate by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/98">causal-agent/scraper#98</a></li> <li>build(deps): fix unchecked lock and update deps by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li>Re-export selectors' CaseSensitivity enum as it is part of our public API. by <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/108">causal-agent/scraper#108</a></li> <li>perf(element): add one sweep element creation by <a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/109">causal-agent/scraper#109</a></li> <li>Added feature flag <code>atomic</code> to make use of atomic <code>StrTendril</code> type. by <a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/adamreichold"><code>@​adamreichold</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/99">causal-agent/scraper#99</a></li> <li><a href="https://github.com/mohe2015"><code>@​mohe2015</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/97">causal-agent/scraper#97</a></li> <li><a href="https://github.com/j-mendez"><code>@​j-mendez</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/107">causal-agent/scraper#107</a></li> <li><a href="https://github.com/jaboatman"><code>@​jaboatman</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/causal-agent/scraper/pull/102">causal-agent/scraper#102</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/causal-agent/scraper/commit/3cb7e9a3202fc6f8b80820135ad071916bc2908b"><code>3cb7e9a</code></a> Version 0.15.0</li> <li><a href="https://github.com/causal-agent/scraper/commit/06f395efe0fb4e9c31cdbd81a9f9e41802572b33"><code>06f395e</code></a> Apply clippy suggestion</li> <li><a href="https://github.com/causal-agent/scraper/commit/ec91bf1ebc9921ca2adeddf93555081912c33334"><code>ec91bf1</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/102">#102</a> from jaboatman/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/4b7fb13446f5ab4400b1fdfb3092b71b3157af9a"><code>4b7fb13</code></a> Merge remote-tracking branch 'upstream/master'</li> <li><a href="https://github.com/causal-agent/scraper/commit/aa479ea170b7f2b463ccba85de0c802318d19abe"><code>aa479ea</code></a> perf(element): add one sweep element creation (<a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/109">#109</a>)</li> <li><a href="https://github.com/causal-agent/scraper/commit/9a6a638db208682593d83bef53c29052336c0487"><code>9a6a638</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/108">#108</a> from adamreichold/also-re-export-case-sensitivity</li> <li><a href="https://github.com/causal-agent/scraper/commit/794b5eef87aa1009a31d4d29093269a04e7d80fa"><code>794b5ee</code></a> Re-export selectors' CaseSensitivity enum as it is part of our public API.</li> <li><a href="https://github.com/causal-agent/scraper/commit/6abb8cd625af5ea4f5a59530f03436aa448f7c56"><code>6abb8cd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/causal-agent/scraper/issues/107">#107</a> from j-mendez/master</li> <li><a href="https://github.com/causal-agent/scraper/commit/c3dd2600dcd4c17424a307c2f82cfcab41943014"><code>c3dd260</code></a> chore(minor): fix element classes map format</li> <li><a href="https://github.com/causal-agent/scraper/commit/b7955b9049ccf5b685f53854d88cca322aa80bac"><code>b7955b9</code></a> perf(selectors): add lazy classes map</li> <li>Additional commits viewable in <a href="https://github.com/causal-agent/scraper/compare/v0.14.0...v0.15.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=scraper&package-manager=cargo&previous-version=0.14.0&new-version=0.15.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-06 04:37:22 +01:00
"itoa",
update polar to 0.25 (#6988)
2022-11-09 23:07:38 +01:00
"ryu",
]
Add git branch to prompt
2019-06-01 23:11:28 +02:00
[[package]]
name = "vcpkg"
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
version = "0.2.15"
Add some minor fixes (#2391)
2020-08-22 07:06:19 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
checksum = "accd4ea62f7bb7a82fe23066fb0957d48ef677f6eeb8215f372f52e48bb32426"
Add some minor fixes (#2391)
2020-08-22 07:06:19 +02:00
WIP
2021-10-25 06:01:02 +02:00
[[package]]
name = "version_check"
merge main
2022-02-08 14:28:21 +01:00
version = "0.9.4"
WIP
2021-10-25 06:01:02 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
merge main
2022-02-08 14:28:21 +01:00
checksum = "49874b5167b65d7193b8aba1567f5c7d93d001cafc34600cee003eda787e483f"
Merge master
2019-11-16 18:17:05 +01:00
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 21:02:26 +01:00
[[package]]
name = "vte"
nu-path crate refactor (#3730) * Resolve rebase artifacts * Remove leftover dependencies on removed feature * Remove unnecessary 'pub' * Start taking notes and fooling around * Split canonicalize to two versions; Add TODOs One that takes `relative_to` and one that doesn't. More TODO notes. * Merge absolutize to and rename resolve_dots * Add custom absolutize fn and use it in path expand * Convert a couple of dunce::canonicalize to ours * Update nu-path description * Replace all canonicalize with nu-path version * Remove leftover dunce dependencies * Fix broken autocd with trailing slash Trailing slash is preserved *only* in paths that do not contain "." or "..". This should be fixed in the future to cover all paths but for now it at least covers basic cases. * Use dunce::canonicalize for canonicalizing * Alow cd recovery from non-existent cwd * Disable removed canonicalize functionality tests Remove unused import * Break down nu-path into separate modules * Remove unused public imports * Remove abundant cow mapping * Fix clippy warning * Reformulate old canonicalize tests to expand_path They wouldn't work with the new canonicalize. * Canonicalize also ~ and ndots; Unify path joining Also, add doc comments in nu_path::expansions. * Add comment * Avoid expanding ndots if path is not valid UTF-8 With this change, no lossy path->string conversion should happen in the nu-path crate. * Fmt * Slight expand_tilde refactor; Add doc comments * Start nu-path integration tests * Add tests TODO * Fix docstring typo * Fix some doc strings * Add README for nu-path crate * Add a couple of canonicalize tests * Add nu-path integration tests * Add trim trailing slashes tests * Update nu-path dependency * Remove unused import * Regenerate lockfile
2021-08-28 14:59:09 +02:00
version = "0.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6cbce692ab4ca2f1f3047fcf732430249c0e971bfdd2b234cf2c47ad93af5983"
dependencies = [
"arrayvec 0.5.2",
"utf8parse",
"vte_generate_state_changes",
]
update `strip-ansi-escapes` to use new api (#9958) # Description This PR updates `strip-ansi-escapes` to support their new API. This also updates nushell to the latest reedline after the same fix https://github.com/nushell/reedline/pull/617 closes #9957 # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `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-08-08 22:20:37 +02:00
[[package]]
name = "vte"
version = "0.11.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f5022b5fbf9407086c180e9557be968742d839e68346af7792b8592489732197"
dependencies = [
"utf8parse",
"vte_generate_state_changes",
]
nu-path crate refactor (#3730) * Resolve rebase artifacts * Remove leftover dependencies on removed feature * Remove unnecessary 'pub' * Start taking notes and fooling around * Split canonicalize to two versions; Add TODOs One that takes `relative_to` and one that doesn't. More TODO notes. * Merge absolutize to and rename resolve_dots * Add custom absolutize fn and use it in path expand * Convert a couple of dunce::canonicalize to ours * Update nu-path description * Replace all canonicalize with nu-path version * Remove leftover dunce dependencies * Fix broken autocd with trailing slash Trailing slash is preserved *only* in paths that do not contain "." or "..". This should be fixed in the future to cover all paths but for now it at least covers basic cases. * Use dunce::canonicalize for canonicalizing * Alow cd recovery from non-existent cwd * Disable removed canonicalize functionality tests Remove unused import * Break down nu-path into separate modules * Remove unused public imports * Remove abundant cow mapping * Fix clippy warning * Reformulate old canonicalize tests to expand_path They wouldn't work with the new canonicalize. * Canonicalize also ~ and ndots; Unify path joining Also, add doc comments in nu_path::expansions. * Add comment * Avoid expanding ndots if path is not valid UTF-8 With this change, no lossy path->string conversion should happen in the nu-path crate. * Fmt * Slight expand_tilde refactor; Add doc comments * Start nu-path integration tests * Add tests TODO * Fix docstring typo * Fix some doc strings * Add README for nu-path crate * Add a couple of canonicalize tests * Add nu-path integration tests * Add trim trailing slashes tests * Update nu-path dependency * Remove unused import * Regenerate lockfile
2021-08-28 14:59:09 +02:00
[[package]]
name = "vte_generate_state_changes"
version = "0.1.1"
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 21:02:26 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-path crate refactor (#3730) * Resolve rebase artifacts * Remove leftover dependencies on removed feature * Remove unnecessary 'pub' * Start taking notes and fooling around * Split canonicalize to two versions; Add TODOs One that takes `relative_to` and one that doesn't. More TODO notes. * Merge absolutize to and rename resolve_dots * Add custom absolutize fn and use it in path expand * Convert a couple of dunce::canonicalize to ours * Update nu-path description * Replace all canonicalize with nu-path version * Remove leftover dunce dependencies * Fix broken autocd with trailing slash Trailing slash is preserved *only* in paths that do not contain "." or "..". This should be fixed in the future to cover all paths but for now it at least covers basic cases. * Use dunce::canonicalize for canonicalizing * Alow cd recovery from non-existent cwd * Disable removed canonicalize functionality tests Remove unused import * Break down nu-path into separate modules * Remove unused public imports * Remove abundant cow mapping * Fix clippy warning * Reformulate old canonicalize tests to expand_path They wouldn't work with the new canonicalize. * Canonicalize also ~ and ndots; Unify path joining Also, add doc comments in nu_path::expansions. * Add comment * Avoid expanding ndots if path is not valid UTF-8 With this change, no lossy path->string conversion should happen in the nu-path crate. * Fmt * Slight expand_tilde refactor; Add doc comments * Start nu-path integration tests * Add tests TODO * Fix docstring typo * Fix some doc strings * Add README for nu-path crate * Add a couple of canonicalize tests * Add nu-path integration tests * Add trim trailing slashes tests * Update nu-path dependency * Remove unused import * Regenerate lockfile
2021-08-28 14:59:09 +02:00
checksum = "d257817081c7dffcdbab24b9e62d2def62e2ff7d00b1c20062551e6cccc145ff"
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 21:02:26 +01:00
dependencies = [
nu-path crate refactor (#3730) * Resolve rebase artifacts * Remove leftover dependencies on removed feature * Remove unnecessary 'pub' * Start taking notes and fooling around * Split canonicalize to two versions; Add TODOs One that takes `relative_to` and one that doesn't. More TODO notes. * Merge absolutize to and rename resolve_dots * Add custom absolutize fn and use it in path expand * Convert a couple of dunce::canonicalize to ours * Update nu-path description * Replace all canonicalize with nu-path version * Remove leftover dunce dependencies * Fix broken autocd with trailing slash Trailing slash is preserved *only* in paths that do not contain "." or "..". This should be fixed in the future to cover all paths but for now it at least covers basic cases. * Use dunce::canonicalize for canonicalizing * Alow cd recovery from non-existent cwd * Disable removed canonicalize functionality tests Remove unused import * Break down nu-path into separate modules * Remove unused public imports * Remove abundant cow mapping * Fix clippy warning * Reformulate old canonicalize tests to expand_path They wouldn't work with the new canonicalize. * Canonicalize also ~ and ndots; Unify path joining Also, add doc comments in nu_path::expansions. * Add comment * Avoid expanding ndots if path is not valid UTF-8 With this change, no lossy path->string conversion should happen in the nu-path crate. * Fmt * Slight expand_tilde refactor; Add doc comments * Start nu-path integration tests * Add tests TODO * Fix docstring typo * Fix some doc strings * Add README for nu-path crate * Add a couple of canonicalize tests * Add nu-path integration tests * Add trim trailing slashes tests * Update nu-path dependency * Remove unused import * Regenerate lockfile
2021-08-28 14:59:09 +02:00
"proc-macro2",
"quote",
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 21:02:26 +01:00
]
Bat
2019-05-18 03:24:13 +02:00
[[package]]
tests for lex and lite parser
2021-08-30 20:36:07 +02:00
name = "wait-timeout"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9f200f5b12eb75f8c1ed65abd4b2db8a6e1b138a20de009dacee265a2498f3f6"
dependencies = [
"libc",
]
`To html` and `to md` (#453) * MathEval Variance and Stddev * Fix tests and linting * Typo * Deal with streams when they are not tables * First draft of these commands * To MD * To md and to html * Fixed cargo and to_md * `into_abbreviated_string` instead of `into_string` * Changed how inner tables are displayed
2021-12-10 02:16:35 +01:00
[[package]]
Bat
2019-05-18 03:24:13 +02:00
name = "walkdir"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "2.4.0"
Bat
2019-05-18 03:24:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "d71d857dc86794ca4c280d616f7da00d2dbfd8cd788846559a6813e6aa4b54ee"
Bat
2019-05-18 03:24:13 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"same-file",
"winapi-util",
Bat
2019-05-18 03:24:13 +02:00
]
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
[[package]]
name = "want"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
version = "0.3.1"
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
REFACTOR: move the 0% commands to `nu-cmd-extra` (#9404) requires - https://github.com/nushell/nushell/pull/9455 # :gear: Description in this PR i move the commands we've all agreed, in the core team, to move out of the core Nushell to the `extra` feature. > **Warning** > in the first commits here, i've > - moved the implementations to `nu-cmd-extra` > - removed the declaration of all the commands below from `nu-command` > - made sure the commands were not available anymore with `cargo run -- -n` ## the list of commands to move with the current command table downloaded as `commands.csv`, i've run ```bash let commands = ( open commands.csv | where is_plugin == "FALSE" and category != "deprecated" | select name category "approv. %" | rename name category approval | insert treated {|it| ( ($it.approval == 100) or # all the core team agreed on them ($it.name | str starts-with "bits") or # see https://github.com/nushell/nushell/pull/9241 ($it.name | str starts-with "dfr") # see https://github.com/nushell/nushell/pull/9327 )} ) ``` to preprocess them and then ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} ``` to get all untreated commands with no approval, which gives ``` ╭────┬───────────────┬─────────┬─────────────┬──────────╮ │ # │ name │ treated │ category │ approval │ ├────┼───────────────┼─────────┼─────────────┼──────────┤ │ 0 │ fmt │ false │ conversions │ 0 │ │ 1 │ each while │ false │ filters │ 0 │ │ 2 │ roll │ false │ filters │ 0 │ │ 3 │ roll down │ false │ filters │ 0 │ │ 4 │ roll left │ false │ filters │ 0 │ │ 5 │ roll right │ false │ filters │ 0 │ │ 6 │ roll up │ false │ filters │ 0 │ │ 7 │ rotate │ false │ filters │ 0 │ │ 8 │ update cells │ false │ filters │ 0 │ │ 9 │ decode hex │ false │ formats │ 0 │ │ 10 │ encode hex │ false │ formats │ 0 │ │ 11 │ from url │ false │ formats │ 0 │ │ 12 │ to html │ false │ formats │ 0 │ │ 13 │ ansi gradient │ false │ platform │ 0 │ │ 14 │ ansi link │ false │ platform │ 0 │ │ 15 │ format │ false │ strings │ 0 │ ╰────┴───────────────┴─────────┴─────────────┴──────────╯ ``` # :paintbrush: User-Facing Changes ``` $nothing ``` # :test_tube: Tests + Formatting - :black_circle: `toolkit fmt` - :black_circle: `toolkit clippy` - :black_circle: `toolkit test` - :black_circle: `toolkit test stdlib` # :book: After Submitting ``` $nothing ``` # :mag: For reviewers ```bash $commands | where {|it| (not $it.treated) and ($it.approval == 0)} | each {|command| try { help $command.name | ignore } catch {|e| $"($command.name): ($e.msg)" } } ``` should give no output in `cargo run --features extra -- -n` and a table with 16 lines in `cargo run -- -n`
2023-07-06 17:31:31 +02:00
checksum = "bfa7760aed19e106de2c7c0b581b509f2f25d3dacaf737cb82ac61bc6d760b0e"
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
dependencies = [
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"try-lock",
Fetch content from S3 (#2328) * fetch content from s3 resource * remove submodule * fix clippy * update Cargo.lock * fix s3 plugin dependency version
2020-08-12 19:20:22 +02:00
]
Help menu (#4992) * nu-completer with suggestions * help menu with scrolling * updates description rows based on space * configuration for help menu * update nu-ansi-term * corrected test for update cells * changed keybinding
2022-03-27 15:01:04 +02:00
[[package]]
name = "wasi"
version = "0.11.0+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9c8d87e72b64a3b4db28d11ce29237c246188f4f51057d65a7eab63b7987e423"
Add opening urls
2019-06-08 20:09:17 +02:00
[[package]]
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
name = "wasm-bindgen"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.2.89"
Add opening urls
2019-06-08 20:09:17 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "0ed0d4f68a3015cc185aff4db9506a015f4b96f95303897bfa23f846db54064e"
Filesize formatting (#456) * configure the format of filesize * type-o * removed some comments * updated tests * accomodated filesize_metric better, added test
2021-12-09 20:19:36 +01:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"wasm-bindgen-macro",
Add opening urls
2019-06-08 20:09:17 +02:00
]
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
[[package]]
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
name = "wasm-bindgen-backend"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.2.89"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "1b56f625e64f3a1084ded111c4d5f477df9f8c92df113852fa5a374dbda78826"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"bumpalo",
Update s3handler to 0.7 (really 0.7.3). (#3757) This brings with it a reduction in the number of duplicated dependencies that it has and the overhead it imposes on our build. The number of crates that need to be built for `cargo build --features extra` drops by roughly 50.
2021-07-09 21:28:07 +02:00
"log",
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
"once_cell",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"proc-macro2",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"wasm-bindgen-shared",
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
]
[[package]]
name = "wasm-bindgen-macro"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.2.89"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "0162dbf37223cd2afce98f3d0785506dcb8d266223983e4b5b525859e6e182b2"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
dependencies = [
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"quote",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"wasm-bindgen-macro-support",
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
]
[[package]]
name = "wasm-bindgen-macro-support"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.2.89"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "f0eb82fcb7930ae6219a7ecfd55b217f5f0893484b7a13022ebb2b2bf20b5283"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"proc-macro2",
Remove duplicate dependencies (#3961) * chore: Replace surf with reqwest Removes a lot of older, duplication versions of some dependencies (roughtly 90 dependencies removed in total) * chore: Remove syn 0.11 * chore: Remove unnecessary features from ptree Removes some more duplicate dependencies * cargo update * Ensure we run the fetch and post plugins on the tokio runtime * Fix clippy warning * fix: Github requires a user agent on requests Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2021-08-28 05:34:11 +02:00
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"wasm-bindgen-backend",
"wasm-bindgen-shared",
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
]
[[package]]
name = "wasm-bindgen-shared"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.2.89"
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "7ab9b36309365056cd639da3134bf87fa8f3d86008abf99e612384a6eecd459f"
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
new `glob` command (#5087)
2022-04-04 22:45:01 +02:00
[[package]]
name = "wax"
Bump wax from 0.5.0 to 0.6.0 (#10574)
2023-10-09 14:31:50 +02:00
version = "0.6.0"
new `glob` command (#5087)
2022-04-04 22:45:01 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump wax from 0.5.0 to 0.6.0 (#10574)
2023-10-09 14:31:50 +02:00
checksum = "8d12a78aa0bab22d2f26ed1a96df7ab58e8a93506a3e20adb47c51a93b4e1357"
new `glob` command (#5087)
2022-04-04 22:45:01 +02:00
dependencies = [
"const_format",
Bump wax from 0.5.0 to 0.6.0 (#10574)
2023-10-09 14:31:50 +02:00
"itertools 0.11.0",
Remove `math eval` command (#7284) Reasoning: Most missing math commands are implemented with #7258. The `meval` crate itself declares that it doesn't strive to stringent standards (https://docs.rs/meval/latest/meval/#related-projects). For example no particular special casing or transformations are performed to ensure numerical stability. It uses the same rust `std` library functions we use or have access to (and `f64`). While the command call syntax in nushell may be a bit more verbose, having a single source of truth and common commands is beneficial. Furthermore the `math` commands can themselves implement broadcasting over lists (or table columns). Closes #7073 Removed dependencies: - `meval` - `nom 1.2.4` (duplicate) User-Facing Changes: Scripts using `math eval` will break. We remove a further `eval` like behavior to get results through runtime evaluation (albeit limited in scope) Tests: - Updated tests that internally used `math eval`. - Removed one test that primarily used `math eval` to obtain a result from `str join`
2023-01-04 23:50:18 +01:00
"nom",
new `glob` command (#5087)
2022-04-04 22:45:01 +02:00
"pori",
"regex",
"thiserror",
"walkdir",
]
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
[[package]]
name = "web-sys"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.3.66"
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "50c24a44ec86bb68fbecd1b3efed7e85ea5621b39b35ef2766b66cd984f8010f"
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"js-sys",
"wasm-bindgen",
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
]
Replace `ichwh` with `which` and some fixes for auto-cd (canonicalization) (#1672) * fix: absolutize path against its parent if it was a symlink. On Linux this happens because Rust calls readlink but doesn't canonicalize the resultant path. * feat: playground function to create symlinks * fix: use playground dirs * feat: test for #1631, shift tests names * Creation of FilesystemShell with custom location may fail * Replace ichwh with which * Creation of FilesystemShell with custom location may fail * Replace ichwh with which * fix: add ichwh again since it cannot be completely replaced * fix: replace one more use of which
2020-04-27 19:49:53 +02:00
[[package]]
name = "which"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "4.4.2"
Replace `ichwh` with `which` and some fixes for auto-cd (canonicalization) (#1672) * fix: absolutize path against its parent if it was a symlink. On Linux this happens because Rust calls readlink but doesn't canonicalize the resultant path. * feat: playground function to create symlinks * fix: use playground dirs * feat: test for #1631, shift tests names * Creation of FilesystemShell with custom location may fail * Replace ichwh with which * Creation of FilesystemShell with custom location may fail * Replace ichwh with which * fix: add ichwh again since it cannot be completely replaced * fix: replace one more use of which
2020-04-27 19:49:53 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "87ba24419a2078cd2b0f2ede2691b6c66d8e47836da3b6db8265ebad47afbfc7"
Replace `ichwh` with `which` and some fixes for auto-cd (canonicalization) (#1672) * fix: absolutize path against its parent if it was a symlink. On Linux this happens because Rust calls readlink but doesn't canonicalize the resultant path. * feat: playground function to create symlinks * fix: use playground dirs * feat: test for #1631, shift tests names * Creation of FilesystemShell with custom location may fail * Replace ichwh with which * Creation of FilesystemShell with custom location may fail * Replace ichwh with which * fix: add ichwh again since it cannot be completely replaced * fix: replace one more use of which
2020-04-27 19:49:53 +02:00
dependencies = [
allow start to handle urls (#3351)
2021-04-24 16:33:17 +02:00
"either",
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
"home",
Upgrade `which` dependency to fix case on Windows (#6453)
2022-08-31 18:50:18 +02:00
"once_cell",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"rustix 0.38.28",
Replace `ichwh` with `which` and some fixes for auto-cd (canonicalization) (#1672) * fix: absolutize path against its parent if it was a symlink. On Linux this happens because Rust calls readlink but doesn't canonicalize the resultant path. * feat: playground function to create symlinks * fix: use playground dirs * feat: test for #1631, shift tests names * Creation of FilesystemShell with custom location may fail * Replace ichwh with which * Creation of FilesystemShell with custom location may fail * Replace ichwh with which * fix: add ichwh again since it cannot be completely replaced * fix: replace one more use of which
2020-04-27 19:49:53 +02:00
]
Bump which from 4.4.2 to 5.0.0 (#10811)
2023-10-23 08:14:28 +02:00
[[package]]
name = "which"
version = "5.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9bf3ea8596f3a0dd5980b46430f2058dfe2c36a27ccfbb1845d6fbfcd9ba6e14"
dependencies = [
"either",
"home",
"once_cell",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"rustix 0.38.28",
Bump which from 4.4.2 to 5.0.0 (#10811)
2023-10-23 08:14:28 +02:00
"windows-sys 0.48.0",
]
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
[[package]]
name = "wild"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "2.2.0"
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "10d01931a94d5a115a53f95292f51d316856b68a035618eb831bbba593a30b67"
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
dependencies = [
"glob",
]
allow start to handle urls (#3351)
2021-04-24 16:33:17 +02:00
[[package]]
objectshell initial commit
2019-05-10 18:59:12 +02:00
name = "winapi"
Bump deps and touchup (#2066)
2020-06-27 09:54:31 +02:00
version = "0.3.9"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump deps and touchup (#2066)
2020-06-27 09:54:31 +02:00
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
objectshell initial commit
2019-05-10 18:59:12 +02:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
[[package]]
objectshell initial commit
2019-05-10 18:59:12 +02:00
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "winapi-util"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.1.6"
Bat
2019-05-18 03:24:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "f29e6f9198ba0d26b4c9f07dbe6f9ed633e1f3d5b8b414090084349e46a52596"
Bat
2019-05-18 03:24:13 +02:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"winapi",
Bat
2019-05-18 03:24:13 +02:00
]
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
[[package]]
Remove 'arboard' (#4174)
2021-12-01 20:48:03 +01:00
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
Bump windows from 0.43.0 to 0.44.0 (#7911)
2023-01-30 03:17:18 +01:00
[[package]]
name = "windows"
version = "0.44.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9e745dab35a0c4c77aa3ce42d595e13d2003d6902d6b08c9ef5fc326d08da12b"
dependencies = [
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
"windows-targets 0.42.2",
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
]
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
[[package]]
name = "windows"
Bump windows from 0.48.0 to 0.52.0 (#11325) # Description Bump `windows` to 0.52.0 and fix `is_admin` https://github.com/microsoft/windows-rs/pull/2476 # User-Facing Changes N/A --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-12-21 18:49:15 +01:00
version = "0.52.0"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump windows from 0.48.0 to 0.52.0 (#11325) # Description Bump `windows` to 0.52.0 and fix `is_admin` https://github.com/microsoft/windows-rs/pull/2476 # User-Facing Changes N/A --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-12-21 18:49:15 +01:00
checksum = "e48a53791691ab099e5e2ad123536d0fff50652600abaf43bbf952894110d0be"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
dependencies = [
Bump windows from 0.48.0 to 0.52.0 (#11325) # Description Bump `windows` to 0.52.0 and fix `is_admin` https://github.com/microsoft/windows-rs/pull/2476 # User-Facing Changes N/A --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-12-21 18:49:15 +01:00
"windows-core 0.52.0",
"windows-targets 0.52.0",
Bump windows from 0.43.0 to 0.44.0 (#7911)
2023-01-30 03:17:18 +01:00
]
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
[[package]]
name = "windows-core"
version = "0.51.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f1f8cf84f35d2db49a46868f947758c7a1138116f7fac3bc844f43ade1292e64"
dependencies = [
"windows-targets 0.48.5",
]
Bump windows from 0.48.0 to 0.52.0 (#11325) # Description Bump `windows` to 0.52.0 and fix `is_admin` https://github.com/microsoft/windows-rs/pull/2476 # User-Facing Changes N/A --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-12-21 18:49:15 +01:00
[[package]]
name = "windows-core"
version = "0.52.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "33ab640c8d7e35bf8ba19b884ba838ceb4fba93a4e8c65a9059d08afcfc683d9"
dependencies = [
"windows-targets 0.52.0",
]
Bump errno from 0.2.8 to 0.3.0 (#8131) Bumps [errno](https://github.com/lambda-fairy/rust-errno) from 0.2.8 to 0.3.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/lambda-fairy/rust-errno/blob/main/CHANGELOG.md">errno's changelog</a>.</em></p> <blockquote> <h1>[0.3.0] - 2023-02-12</h1> <ul> <li> <p>Add haiku support <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/42">#42</a></p> </li> <li> <p>Add AIX support <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/54">#54</a></p> </li> <li> <p>Add formatting with <code>#![no_std]</code> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/44">#44</a></p> </li> <li> <p>Switch from <code>winapi</code> to <code>windows-sys</code> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/55">#55</a></p> </li> <li> <p>Update minimum Rust version to 1.48 <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/48">#48</a> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/55">#55</a></p> </li> <li> <p>Upgrade to Rust 2018 edition <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/59">#59</a></p> </li> <li> <p>wasm32-wasi: Use <code>__errno_location</code> instead of <code>feature(thread_local)</code>. <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/66">#66</a></p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/e1882701f6d21bd9f45c2941a85416c59fa019ac"><code>e188270</code></a> Release 0.3.0</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/3983d26f982014d083bf58ac9dafa69805c458ca"><code>3983d26</code></a> Add <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/66">#66</a> to changelog</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/362d7c6c358d82e19182fb46ebb0b23beeb50713"><code>362d7c6</code></a> Update windows-sys requirement from 0.42 to 0.45 (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/67">#67</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/b8cc39bb8de7194d64f52d762310a113a998048d"><code>b8cc39b</code></a> wasm32-wasi: Use <code>__errno_location</code> instead of <code>feature(thread_local)</code>. (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/66">#66</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/dbd02cf02f6cb81bcf93e1b754167b59c0996b9a"><code>dbd02cf</code></a> Replace deprecated <code>trim_right</code> with <code>trim_end</code> (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/65">#65</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/c999f38356ce5c291296ab2e09ea584df45d2a9b"><code>c999f38</code></a> Add comparison with <code>std::io::Error</code></li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/8a4c62af22f85c7f0214e6e6bdc710edf67d0088"><code>8a4c62a</code></a> Bump actions/checkout from 2 to 3 (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/64">#64</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/04379ae703bc48c4a3fdf51be748cbddbf565b8c"><code>04379ae</code></a> Add Dependabot (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/63">#63</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/18e34d3895840a82a074b41bd0029385fddb6e5c"><code>18e34d3</code></a> Setup caching for CI</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/81c3ba4cba053185cc02f51c12650e86f3bb2fc8"><code>81c3ba4</code></a> Run clippy in CI</li> <li>Additional commits viewable in <a href="https://github.com/lambda-fairy/rust-errno/compare/v0.2.8...v0.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=errno&package-manager=cargo&previous-version=0.2.8&new-version=0.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-22 13:56:31 +01:00
[[package]]
name = "windows-sys"
version = "0.45.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "75283be5efb2831d37ea142365f009c02ec203cd29a3ebecbc093d52315b66d0"
dependencies = [
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
"windows-targets 0.42.2",
Bump errno from 0.2.8 to 0.3.0 (#8131) Bumps [errno](https://github.com/lambda-fairy/rust-errno) from 0.2.8 to 0.3.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/lambda-fairy/rust-errno/blob/main/CHANGELOG.md">errno's changelog</a>.</em></p> <blockquote> <h1>[0.3.0] - 2023-02-12</h1> <ul> <li> <p>Add haiku support <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/42">#42</a></p> </li> <li> <p>Add AIX support <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/54">#54</a></p> </li> <li> <p>Add formatting with <code>#![no_std]</code> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/44">#44</a></p> </li> <li> <p>Switch from <code>winapi</code> to <code>windows-sys</code> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/55">#55</a></p> </li> <li> <p>Update minimum Rust version to 1.48 <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/48">#48</a> <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/55">#55</a></p> </li> <li> <p>Upgrade to Rust 2018 edition <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/59">#59</a></p> </li> <li> <p>wasm32-wasi: Use <code>__errno_location</code> instead of <code>feature(thread_local)</code>. <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/pull/66">#66</a></p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/e1882701f6d21bd9f45c2941a85416c59fa019ac"><code>e188270</code></a> Release 0.3.0</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/3983d26f982014d083bf58ac9dafa69805c458ca"><code>3983d26</code></a> Add <a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/66">#66</a> to changelog</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/362d7c6c358d82e19182fb46ebb0b23beeb50713"><code>362d7c6</code></a> Update windows-sys requirement from 0.42 to 0.45 (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/67">#67</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/b8cc39bb8de7194d64f52d762310a113a998048d"><code>b8cc39b</code></a> wasm32-wasi: Use <code>__errno_location</code> instead of <code>feature(thread_local)</code>. (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/66">#66</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/dbd02cf02f6cb81bcf93e1b754167b59c0996b9a"><code>dbd02cf</code></a> Replace deprecated <code>trim_right</code> with <code>trim_end</code> (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/65">#65</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/c999f38356ce5c291296ab2e09ea584df45d2a9b"><code>c999f38</code></a> Add comparison with <code>std::io::Error</code></li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/8a4c62af22f85c7f0214e6e6bdc710edf67d0088"><code>8a4c62a</code></a> Bump actions/checkout from 2 to 3 (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/64">#64</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/04379ae703bc48c4a3fdf51be748cbddbf565b8c"><code>04379ae</code></a> Add Dependabot (<a href="https://github-redirect.dependabot.com/lambda-fairy/rust-errno/issues/63">#63</a>)</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/18e34d3895840a82a074b41bd0029385fddb6e5c"><code>18e34d3</code></a> Setup caching for CI</li> <li><a href="https://github.com/lambda-fairy/rust-errno/commit/81c3ba4cba053185cc02f51c12650e86f3bb2fc8"><code>81c3ba4</code></a> Run clippy in CI</li> <li>Additional commits viewable in <a href="https://github.com/lambda-fairy/rust-errno/compare/v0.2.8...v0.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=errno&package-manager=cargo&previous-version=0.2.8&new-version=0.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-22 13:56:31 +01:00
]
Bump winreg from 0.11.0 to 0.50.0 (#8837)
2023-04-14 14:15:01 +02:00
[[package]]
name = "windows-sys"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "677d2418bec65e3338edb076e806bc1ec15693c5d0104683f2efe857f61056a9"
dependencies = [
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
"windows-targets 0.48.5",
Bump winreg from 0.11.0 to 0.50.0 (#8837)
2023-04-14 14:15:01 +02:00
]
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "windows-sys"
version = "0.52.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "282be5f36a8ce781fad8c8ae18fa3f9beff57ec1b52cb3de0789201425d9a33d"
dependencies = [
"windows-targets 0.52.0",
]
Bump windows from 0.43.0 to 0.44.0 (#7911)
2023-01-30 03:17:18 +01:00
[[package]]
name = "windows-targets"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
version = "0.42.2"
Bump windows from 0.43.0 to 0.44.0 (#7911)
2023-01-30 03:17:18 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
checksum = "8e5180c00cd44c9b1c88adb3693291f1cd93605ded80c250a75d472756b4d071"
Bump windows from 0.43.0 to 0.44.0 (#7911)
2023-01-30 03:17:18 +01:00
dependencies = [
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
"windows_aarch64_gnullvm 0.42.2",
"windows_aarch64_msvc 0.42.2",
"windows_i686_gnu 0.42.2",
"windows_i686_msvc 0.42.2",
"windows_x86_64_gnu 0.42.2",
"windows_x86_64_gnullvm 0.42.2",
"windows_x86_64_msvc 0.42.2",
]
[[package]]
name = "windows-targets"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.48.5"
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "9a2fa6e2155d7247be68c096456083145c183cbbbc2764150dda45a87197940c"
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
dependencies = [
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
"windows_aarch64_gnullvm 0.48.5",
"windows_aarch64_msvc 0.48.5",
"windows_i686_gnu 0.48.5",
"windows_i686_msvc 0.48.5",
"windows_x86_64_gnu 0.48.5",
"windows_x86_64_gnullvm 0.48.5",
"windows_x86_64_msvc 0.48.5",
let `start` open anything and everything (#7580) # Description Fixes #7546 's request. I'm unsure, so hopefully someone in charge of design can chip in. # User-Facing Changes `open` now opens directories in the default file manager. # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-03 19:47:37 +01:00
]
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "windows-targets"
version = "0.52.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8a18201040b24831fbb9e4eb208f8892e1f50a37feb53cc7ff887feb8f50e7cd"
dependencies = [
"windows_aarch64_gnullvm 0.52.0",
"windows_aarch64_msvc 0.52.0",
"windows_i686_gnu 0.52.0",
"windows_i686_msvc 0.52.0",
"windows_x86_64_gnu 0.52.0",
"windows_x86_64_gnullvm 0.52.0",
"windows_x86_64_msvc 0.52.0",
]
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
[[package]]
name = "windows_aarch64_gnullvm"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
version = "0.42.2"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
checksum = "597a5118570b68bc08d8d59125332c54f1ba9d9adeedeef5b99b02ba2b0698f8"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
[[package]]
name = "windows_aarch64_gnullvm"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.48.5"
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "2b38e32f0abccf9987a4e3079dfb67dcd799fb61361e53e2882c3cbaf0d905d8"
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "windows_aarch64_gnullvm"
version = "0.52.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cb7764e35d4db8a7921e09562a0304bf2f93e0a51bfccee0bd0bb0b666b015ea"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
[[package]]
name = "windows_aarch64_msvc"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
version = "0.42.2"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
checksum = "e08e8864a60f06ef0d0ff4ba04124db8b0fb3be5776a5cd47641e942e58c4d43"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
[[package]]
name = "windows_aarch64_msvc"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.48.5"
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "dc35310971f3b2dbbf3f0690a219f40e2d9afcf64f9ab7cc1be722937c26b4bc"
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "windows_aarch64_msvc"
version = "0.52.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bbaa0368d4f1d2aaefc55b6fcfee13f41544ddf36801e793edbbfd7d7df075ef"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
[[package]]
name = "windows_i686_gnu"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
version = "0.42.2"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
checksum = "c61d927d8da41da96a81f029489353e68739737d3beca43145c8afec9a31a84f"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
[[package]]
name = "windows_i686_gnu"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.48.5"
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "a75915e7def60c94dcef72200b9a8e58e5091744960da64ec734a6c6e9b3743e"
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "windows_i686_gnu"
version = "0.52.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a28637cb1fa3560a16915793afb20081aba2c92ee8af57b4d5f28e4b3e7df313"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
[[package]]
name = "windows_i686_msvc"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
version = "0.42.2"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
checksum = "44d840b6ec649f480a41c8d80f9c65108b92d89345dd94027bfe06ac444d1060"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
[[package]]
name = "windows_i686_msvc"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.48.5"
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "8f55c233f70c4b27f66c523580f78f1004e8b5a8b659e05a4eb49d4166cca406"
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "windows_i686_msvc"
version = "0.52.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ffe5e8e31046ce6230cc7215707b816e339ff4d4d67c65dffa206fd0f7aa7b9a"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
[[package]]
name = "windows_x86_64_gnu"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
version = "0.42.2"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
checksum = "8de912b8b8feb55c064867cf047dda097f92d51efad5b491dfb98f6bbb70cb36"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
[[package]]
name = "windows_x86_64_gnu"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.48.5"
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "53d40abd2583d23e4718fddf1ebec84dbff8381c07cae67ff7768bbf19c6718e"
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "windows_x86_64_gnu"
version = "0.52.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3d6fa32db2bc4a2f5abeacf2b69f7992cd09dca97498da74a151a3132c26befd"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
[[package]]
name = "windows_x86_64_gnullvm"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
version = "0.42.2"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
checksum = "26d41b46a36d453748aedef1486d5c7a85db22e56aff34643984ea85514e94a3"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
[[package]]
name = "windows_x86_64_gnullvm"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.48.5"
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "0b7b52767868a23d5bab768e390dc5f5c55825b6d30b86c844ff2dc7414044cc"
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "windows_x86_64_gnullvm"
version = "0.52.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1a657e1e9d3f514745a572a6846d3c7aa7dbe1658c056ed9c3344c4109a6949e"
Move to latest stable crossterm, with fix (#4684)
2022-03-01 13:05:46 +01:00
[[package]]
name = "windows_x86_64_msvc"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
version = "0.42.2"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump windows from 0.44.0 to 0.46.0 (#8535)
2023-03-22 14:02:03 +01:00
checksum = "9aec5da331524158c6d1a4ac0ab1541149c0b9505fde06423b02f5ef0106b9f0"
cargo update (#5639)
2022-05-25 19:13:14 +02:00
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
[[package]]
name = "windows_x86_64_msvc"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.48.5"
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "ed94fce61571a4006852b7389a063ab983c02eb1bb37b47f8272ce92d06d9538"
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-04-05 23:54:26 +02:00
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
[[package]]
name = "windows_x86_64_msvc"
version = "0.52.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dff9641d1cd4be8d1a070daf9e3773c5f67e78b4d9d42263020c057706765c04"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
[[package]]
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
name = "winnow"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "0.5.28"
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "6c830786f7720c2fd27a1a0e27a709dbd3c4d009b56d098fc742d4f4eab91fe2"
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
dependencies = [
"memchr",
]
Bumps Windows 0.37 -> 0.42. (#6865)
2022-10-23 02:59:44 +02:00
Bump winreg from 0.10.1 to 0.11.0 (#8128) Bumps [winreg](https://github.com/gentoo90/winreg-rs) from 0.10.1 to 0.11.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/gentoo90/winreg-rs/blob/master/CHANGELOG.md">winreg's changelog</a>.</em></p> <blockquote> <h2>0.11.0</h2> <ul> <li>Migrate to the 2018 edition of Rust</li> <li>Move the code from <code>lib.rs</code> to separate files</li> <li>Use <a href="https://crates.io/crates/cfg-if"><code>cfg-if</code></a> instead of <code>build.rs</code> to fail build on non-windows systems</li> <li>Reimplement deserialization logic, implement [de]serialization for byte arrays (<a href="https://github-redirect.dependabot.com/gentoo90/winreg-rs/issues/49">#49</a>)</li> <li>Fix some typos and <code>clippy</code> warnings</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/gentoo90/winreg-rs/commit/f34742d674fd3472bdad036849fe888e6474c07e"><code>f34742d</code></a> Bump version to 0.11.0</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/75f2593f6285d06aea031db9cfed3be0bdfd40aa"><code>75f2593</code></a> Move the changelog to a separate file</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/1f6f877ed73c5b94dd81b883c3acb3f9d14ffd85"><code>1f6f877</code></a> Fix some clippy warnings</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/7a32d642cd8489ab827f0fce984011b67d26672d"><code>7a32d64</code></a> Implement [de]serialization for byte arrays</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/8464557c2d75b6397571b25c0e93195aed29b05d"><code>8464557</code></a> Reimplement deserialization logic</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/9e8dc28029ffeb14fdff76a30c896e8b52825533"><code>9e8dc28</code></a> Put serialization tests into a separate file</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/04f7d232c7abaf6069020c52b8da77f9f1e5f5f2"><code>04f7d23</code></a> Use <code>cfg-if</code> to fail build on non-windows systems</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/c3ac5ba5eaa83916c2fbad270bb1a83fee9f7715"><code>c3ac5ba</code></a> Move the code from <code>lib.rs</code> to separate files</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/17378a9ca4c1f8fc2dc668a5dfe2f5d6bd54cc82"><code>17378a9</code></a> Migrate to the 2018 edition of Rust</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/f4d45923abf53b1aee8f9f7e2f002c459a97b717"><code>f4d4592</code></a> Remove Appveyor. It's broken anyway</li> <li>Additional commits viewable in <a href="https://github.com/gentoo90/winreg-rs/compare/v0.10.1...v0.11.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=winreg&package-manager=cargo&previous-version=0.10.1&new-version=0.11.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-20 03:57:46 +01:00
[[package]]
name = "winreg"
Bump winreg from 0.51.0 to 0.52.0 (#11102)
2023-11-20 20:35:21 +01:00
version = "0.52.0"
Bump winreg from 0.10.1 to 0.11.0 (#8128) Bumps [winreg](https://github.com/gentoo90/winreg-rs) from 0.10.1 to 0.11.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/gentoo90/winreg-rs/blob/master/CHANGELOG.md">winreg's changelog</a>.</em></p> <blockquote> <h2>0.11.0</h2> <ul> <li>Migrate to the 2018 edition of Rust</li> <li>Move the code from <code>lib.rs</code> to separate files</li> <li>Use <a href="https://crates.io/crates/cfg-if"><code>cfg-if</code></a> instead of <code>build.rs</code> to fail build on non-windows systems</li> <li>Reimplement deserialization logic, implement [de]serialization for byte arrays (<a href="https://github-redirect.dependabot.com/gentoo90/winreg-rs/issues/49">#49</a>)</li> <li>Fix some typos and <code>clippy</code> warnings</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/gentoo90/winreg-rs/commit/f34742d674fd3472bdad036849fe888e6474c07e"><code>f34742d</code></a> Bump version to 0.11.0</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/75f2593f6285d06aea031db9cfed3be0bdfd40aa"><code>75f2593</code></a> Move the changelog to a separate file</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/1f6f877ed73c5b94dd81b883c3acb3f9d14ffd85"><code>1f6f877</code></a> Fix some clippy warnings</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/7a32d642cd8489ab827f0fce984011b67d26672d"><code>7a32d64</code></a> Implement [de]serialization for byte arrays</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/8464557c2d75b6397571b25c0e93195aed29b05d"><code>8464557</code></a> Reimplement deserialization logic</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/9e8dc28029ffeb14fdff76a30c896e8b52825533"><code>9e8dc28</code></a> Put serialization tests into a separate file</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/04f7d232c7abaf6069020c52b8da77f9f1e5f5f2"><code>04f7d23</code></a> Use <code>cfg-if</code> to fail build on non-windows systems</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/c3ac5ba5eaa83916c2fbad270bb1a83fee9f7715"><code>c3ac5ba</code></a> Move the code from <code>lib.rs</code> to separate files</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/17378a9ca4c1f8fc2dc668a5dfe2f5d6bd54cc82"><code>17378a9</code></a> Migrate to the 2018 edition of Rust</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/f4d45923abf53b1aee8f9f7e2f002c459a97b717"><code>f4d4592</code></a> Remove Appveyor. It's broken anyway</li> <li>Additional commits viewable in <a href="https://github.com/gentoo90/winreg-rs/compare/v0.10.1...v0.11.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=winreg&package-manager=cargo&previous-version=0.10.1&new-version=0.11.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-20 03:57:46 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump winreg from 0.51.0 to 0.52.0 (#11102)
2023-11-20 20:35:21 +01:00
checksum = "a277a57398d4bfa075df44f501a17cfdf8542d224f0d36095a2adc7aee4ef0a5"
Bump winreg from 0.10.1 to 0.11.0 (#8128) Bumps [winreg](https://github.com/gentoo90/winreg-rs) from 0.10.1 to 0.11.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/gentoo90/winreg-rs/blob/master/CHANGELOG.md">winreg's changelog</a>.</em></p> <blockquote> <h2>0.11.0</h2> <ul> <li>Migrate to the 2018 edition of Rust</li> <li>Move the code from <code>lib.rs</code> to separate files</li> <li>Use <a href="https://crates.io/crates/cfg-if"><code>cfg-if</code></a> instead of <code>build.rs</code> to fail build on non-windows systems</li> <li>Reimplement deserialization logic, implement [de]serialization for byte arrays (<a href="https://github-redirect.dependabot.com/gentoo90/winreg-rs/issues/49">#49</a>)</li> <li>Fix some typos and <code>clippy</code> warnings</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/gentoo90/winreg-rs/commit/f34742d674fd3472bdad036849fe888e6474c07e"><code>f34742d</code></a> Bump version to 0.11.0</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/75f2593f6285d06aea031db9cfed3be0bdfd40aa"><code>75f2593</code></a> Move the changelog to a separate file</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/1f6f877ed73c5b94dd81b883c3acb3f9d14ffd85"><code>1f6f877</code></a> Fix some clippy warnings</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/7a32d642cd8489ab827f0fce984011b67d26672d"><code>7a32d64</code></a> Implement [de]serialization for byte arrays</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/8464557c2d75b6397571b25c0e93195aed29b05d"><code>8464557</code></a> Reimplement deserialization logic</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/9e8dc28029ffeb14fdff76a30c896e8b52825533"><code>9e8dc28</code></a> Put serialization tests into a separate file</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/04f7d232c7abaf6069020c52b8da77f9f1e5f5f2"><code>04f7d23</code></a> Use <code>cfg-if</code> to fail build on non-windows systems</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/c3ac5ba5eaa83916c2fbad270bb1a83fee9f7715"><code>c3ac5ba</code></a> Move the code from <code>lib.rs</code> to separate files</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/17378a9ca4c1f8fc2dc668a5dfe2f5d6bd54cc82"><code>17378a9</code></a> Migrate to the 2018 edition of Rust</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/f4d45923abf53b1aee8f9f7e2f002c459a97b717"><code>f4d4592</code></a> Remove Appveyor. It's broken anyway</li> <li>Additional commits viewable in <a href="https://github.com/gentoo90/winreg-rs/compare/v0.10.1...v0.11.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=winreg&package-manager=cargo&previous-version=0.10.1&new-version=0.11.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-20 03:57:46 +01:00
dependencies = [
dependency: use notify-debouncer-full(based on notify v6) instead of notify v4 (#9606) # Description Closes: #9324 I have done some manually test locally on MacOS, and it seems fine for me. cc: @rgwood
2023-07-05 14:14:55 +02:00
"cfg-if",
Bump winreg from 0.11.0 to 0.50.0 (#8837)
2023-04-14 14:15:01 +02:00
"windows-sys 0.48.0",
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
]
Change `embed-resource` dep to slimmer `winres` (#5630)
2022-05-25 05:28:10 +02:00
[[package]]
Move from `winres` to better-maintained `winresource` fork (#9001) This MR closes #8986; big thanks to @WindSoilder for investigating this and making the MR very easy. I did manual testing to confirm that the icon etc. are still being set correctly after this change. Also skimmed the `winresource` code, no issues jumped out at me.
2023-04-26 14:14:55 +02:00
name = "winresource"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.1.17"
Change `embed-resource` dep to slimmer `winres` (#5630)
2022-05-25 05:28:10 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "77e2aaaf8cfa92078c0c0375423d631f82f2f57979c2884fdd5f604a11e45329"
Change `embed-resource` dep to slimmer `winres` (#5630)
2022-05-25 05:28:10 +02:00
dependencies = [
Bump toml from 0.7.6 to 0.8.0 (#10408) Bumps [toml](https://github.com/toml-rs/toml) from 0.7.6 to 0.8.0. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/toml-rs/toml/commit/310f6ee9c5e80dd6da545d400b358b1bd5895dd4"><code>310f6ee</code></a> chore: Release</li> <li><a href="https://github.com/toml-rs/toml/commit/90da8bc4254152c4a783a098e09c8ac341dc60c7"><code>90da8bc</code></a> docs: Update changelog</li> <li><a href="https://github.com/toml-rs/toml/commit/f3e120f1a052af5ec31a4577138a914e76a52f33"><code>f3e120f</code></a> Merge pull request <a href="https://redirect.github.com/toml-rs/toml/issues/608">#608</a> from epage/enum</li> <li><a href="https://github.com/toml-rs/toml/commit/58a7101f68ecacc7de1f711f1c25c7ea458c9fdd"><code>58a7101</code></a> fix(serde): Support struct variants as table of a table</li> <li><a href="https://github.com/toml-rs/toml/commit/88a4dba3123600016b2388439750198b6c57db13"><code>88a4dba</code></a> fix(serde): Support tuple variants as table of an array</li> <li><a href="https://github.com/toml-rs/toml/commit/cf06b83424921c7ca902bba9fa18d66088af764d"><code>cf06b83</code></a> test(serde): Verify both Table and Value serializers</li> <li><a href="https://github.com/toml-rs/toml/commit/4ffa44ec16155fa73120538eb993dd489552f3ea"><code>4ffa44e</code></a> test(serde): Make parameter order more consistent</li> <li><a href="https://github.com/toml-rs/toml/commit/2b7c34c900aa2622660af495e126a75b71916cba"><code>2b7c34c</code></a> test(serde): Focus on string serialization first</li> <li><a href="https://github.com/toml-rs/toml/commit/e2a6a1ceceb87e222ab1ed13309948157a4492d1"><code>e2a6a1c</code></a> test(serde): Verify existing variant behavior</li> <li><a href="https://github.com/toml-rs/toml/commit/3f3e8329bb205f889dfbf02c2ccabc4d784271a3"><code>3f3e832</code></a> chore: Release</li> <li>Additional commits viewable in <a href="https://github.com/toml-rs/toml/compare/toml-v0.7.6...toml-v0.8.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=toml&package-manager=cargo&previous-version=0.7.6&new-version=0.8.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-09-18 07:50:30 +02:00
"toml 0.7.8",
Move from `winres` to better-maintained `winresource` fork (#9001) This MR closes #8986; big thanks to @WindSoilder for investigating this and making the MR very easy. I did manual testing to confirm that the icon etc. are still being set correctly after this change. Also skimmed the `winresource` code, no issues jumped out at me.
2023-04-26 14:14:55 +02:00
"version_check",
Change `embed-resource` dep to slimmer `winres` (#5630)
2022-05-25 05:28:10 +02:00
]
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
[[package]]
name = "xattr"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
version = "1.1.3"
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
checksum = "a7dae5072fe1f8db8f8d29059189ac175196e410e40ba42d5d4684ae2f750995"
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
dependencies = [
"libc",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"linux-raw-sys 0.4.12",
"rustix 0.38.28",
use uutils/coreutils cp command in place of nushell's cp command (#10097) <!-- 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 Hi. Basically, this is a continuation of the work that @fdncred started. Given some nice discussions on #9463 , and [merged uutils PR](https://github.com/uutils/coreutils/pull/5152) from @tertsdiepraam we have decided to give the `cp` command the `crawl` stage as it was named. > [!NOTE] Given that the `uutils` crate has not made the release for the merged PR, just make sure you checkout latest and put it in the required place to make this PR work. The aim of this PR is for is to see how to move forward using `uutils` crate. In order to getting this started, I have made the current `nushell cp tests` pass along with some extra ones I copied over from the `uutils` repo. With all of that being said, things that would be nice to decide, and keep working on: Crawl: - Handling of certain `named` flags, with their long and short forms(e.g. --update, --reflink, --preserve, etc), and using default values. Maybe `-u` can already have a `default_missing_value`. - Should we maybe just support one single option `switch` flags (see `--backup` in code) as a contrast to the other named args. - Complete test coverage from `uutils`. They had > 100 tests, and I could only port like 12 as they are a bit time consuming given they cannot be straight up copy pasted. Maybe we do not need all >100, but maybe the more relevant to what we want. - Refactor this code Walk: - Non fatal errors on `copy` from `utils`. Currently it just sends it to stdout but errors have no span - Better integration An added possibility is the addition of `SyntaxShape::OneOf()` for `Named` arguments which was briefly mentioned in the discord server, but that is still to be decided. This could greatly improve some of the integration. This would enable something like `cp --preserve [all timestamp]` or `cp --preserve all` to both work. I did not want to keep holding on this, and wait till I was happy with the code because I think its nice if everyone can start up and suggest refactors, but the main important part now was getting it out the door, as if I take my sweet time this will take way longer :stuck_out_tongue: <!-- 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. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting Make sure you've run and fixed any issues with these commands: - [X] cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [X] cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - [X] cargo test --workspace` to check that all tests pass - [X] 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. --> --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-09-08 20:57:38 +02:00
]
From ssv from xml (#383) * MathEval Variance and Stddev * Fix tests and linting * Typo * Deal with streams when they are not tables * From xml and from ssv * linting
2021-11-29 20:22:13 +01:00
[[package]]
Add xml open support
2019-06-11 08:26:03 +02:00
name = "xmlparser"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.13.6"
Add xml open support
2019-06-11 08:26:03 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "66fee0b777b0f5ac1c69bb06d361268faafa61cd4682ae064a171c16c433e9e4"
Add xml open support
2019-06-11 08:26:03 +02:00
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 16:27:37 +01:00
[[package]]
name = "xxhash-rust"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
version = "0.8.7"
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 16:27:37 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
nu-explore: Try to fix a truncation issue in expand view (#10580) I haven't tested cause can't reproduce, but the issue very likely was related to a emojies. (I mean I probably could but ....) Could you try it @fdncred? fix #10560
2023-10-07 13:58:26 +02:00
checksum = "9828b178da53440fa9c766a3d2f73f7cf5d0ac1fe3980c1e5018d899fd19e07b"
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-01-13 16:27:37 +01:00
WIP/ Checkout to new `tabled` (#6286) * nu-table/ Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Fix first column alignment Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix color issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Fix footer row Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table/ Update * Use latest tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add optional -e, -c argument to `table` command for different view Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Update Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix cargo clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * nu-table: Add footer into -e/c mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Publish new expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add width ctrl for Expand mode Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Refactorings Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Merge with main Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix clippy Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Fix tests Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Bump tabled Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * Add record expand and fix empty list issue Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> * refactoring Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com>
2022-10-03 18:40:16 +02:00
[[package]]
name = "yansi"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "09041cd90cf85f7f8b2df60c646f853b7f535ce68f85244eb6731cf89fa498ec"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
[[package]]
name = "zerocopy"
Bump zerocopy from 0.7.29 to 0.7.31 (#11336)
2023-12-15 11:40:56 +01:00
version = "0.7.31"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump zerocopy from 0.7.29 to 0.7.31 (#11336)
2023-12-15 11:40:56 +01:00
checksum = "1c4061bedbb353041c12f413700357bec76df2c7e2ca8e4df8bac24c6bf68e3d"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
dependencies = [
"zerocopy-derive",
]
[[package]]
name = "zerocopy-derive"
Bump zerocopy from 0.7.29 to 0.7.31 (#11336)
2023-12-15 11:40:56 +01:00
version = "0.7.31"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump zerocopy from 0.7.29 to 0.7.31 (#11336)
2023-12-15 11:40:56 +01:00
checksum = "b3c129550b3e6de3fd0ba67ba5c81818f9805e58b8d7fee80a3a59d2c9fc601a"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
dependencies = [
"proc-macro2",
"quote",
Polars Struct support without unsafe blocks (#11229) Second attempt at polars Struct support. This version avoid using unsafe checks by cloning the StructArray and utilizing the into_static to convert to a StructOwned. --------- Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-15 11:21:30 +01:00
"syn 2.0.40",
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
]
`from xlsx` `from ods` and `from toml` (#352) * MathEval Variance and Stddev * Fix tests and linting * Typo * Deal with streams when they are not tables * `from toml` command * From ods * From XLSX
2021-11-19 20:23:35 +01:00
[[package]]
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
name = "zip"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
version = "0.6.6"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
add cargo.lock file (#9223) # Description Missed adding this with the 0.80.1 change. # 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 -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- crates/nu-std/tests/run.nu` 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-05-18 01:32:28 +02:00
checksum = "760394e246e4c28189f19d488c058bf16f564016aefac5d32bb1f3b51d5e9261"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
dependencies = [
updated dependencies (#2517)
2020-09-09 00:35:45 +02:00
"byteorder",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"crc32fast",
couple minor updates to xml deps (#7311) # Description Just some minor updates to xml deps # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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.
2022-12-01 20:25:13 +01:00
"crossbeam-utils",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"flate2",
]
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
[[package]]
name = "zstd"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "0.13.0"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "bffb3309596d527cfcba7dfc6ed6052f1d39dfbd7c867aa2e865e4a449c10110"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
dependencies = [
Update polars to 0.28 (#9136) # Description Update polars to 0.28. Luckily, it didn't require major changes. # User-Facing Changes None. (Apart from the fact that certain error messages will stop breaking table formatting)
2023-05-08 17:42:53 +02:00
"zstd-safe",
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
]
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
[[package]]
name = "zstd-safe"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
version = "7.0.0"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrading to polars 0.35 (#11241) Co-authored-by: Jack Wright <jack.wright@disqo.com>
2023-12-06 01:09:34 +01:00
checksum = "43747c7422e2924c11144d5229878b98180ef8b06cca4ab5af37afc8a8d8ea3e"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
dependencies = [
"zstd-sys",
]
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
[[package]]
name = "zstd-sys"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
version = "2.0.9+zstd.1.5.5"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add `mktemp` command (#11005) closes #10845 I've opened this a little prematurely to get some questions answered before I cleanup the code. As I started trying to better understand GNUs `mktemp` I've realized its kind of peculiar and we might want to change its behavior to introduce it to nushell. #### quiet and dry run Does it make sense to keep the `quiet` and `dry_run` flags? I don't think so. The GNU documentation says this about the dry run flag "Using the output of this command to create a new file is inherently unsafe, as there is a window of time between generating the name and using it where another process can create an object by the same name." So yeah why keep it? As far as quiet goes, does it make sense to silence the errors in nushell? #### other confusing flags According to the [gnu docs](https://www.gnu.org/software/coreutils/manual/html_node/mktemp-invocation.html), the `-t` flag is deprecated and the `-p`/ `--tempdir` are the same flag with the only difference being `--tempdir` takes an optional path, Given that, I've broken the `-p` away from `--tempdir`. Now there is one switch `--tmpdir`/`-t` and one named param `--tmpdir-path`/`-p`. GNU mktemp ``` -p DIR, --tmpdir[=DIR] interpret TEMPLATE relative to DIR; if DIR is not specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE must not be an absolute name; unlike with -t, TEMPLATE may contain slashes, but mktemp creates only the final component -t interpret TEMPLATE as a single file name component, relative to a directory: $TMPDIR, if set; else the directory specified via -p; else /tmp [deprecated] ``` to nushell mktemp ``` -p, --tmpdir-path <Filepath> # named param, must provide a path -t, --tmpdir # a switch ``` Is this a terrible idea? What should I do? --------- Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-18 02:30:53 +01:00
checksum = "9e16efa8a874a0481a574084d34cc26fdb3b99627480f785888deb6386506656"
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
dependencies = [
"cc",
Update all dependencies in `Cargo.lock` (#8408) # Description This includes the development versions of `reedline` and `nu-ansi-term` (Interesting to see if there is potential breakage due to a change to the `Color::default()`) All other crates are updated to the latest available version. This change reduces the number of dependencies to compile slightly and for me on Linux reduced the compile time a few seconds. # Output from `cargo build --timings` ## `main` <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 398 Total units: | 398 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:19:14Z Total time: | 75.1s (1m 15.1s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> ## this PR <html><body> <!--StartFragment--> Targets: | nu 0.76.1 (bin "nu") -- | -- Profile: | dev Fresh units: | 0 Dirty units: | 392 Total units: | 392 Max concurrency: | 16 (jobs=16 ncpu=16) Build start: | 2023-03-11T18:21:20Z Total time: | 69.6s (1m 9.6s) rustc: | rustc 1.66.1 (90743e729 2023-01-10)Host: x86_64-unknown-linux-gnuTarget: x86_64-unknown-linux-gnu <!--EndFragment--> </body> </html> # User-Facing Changes None intended, none visually detected upon a cursory look around. # Tests + Formatting -
2023-03-12 00:35:56 +01:00
"pkg-config",
Load parquet and json files (#3437) * Load parquet and json files * changed csv file error
2021-05-18 21:33:10 +02:00
]
Reference in New Issue Copy Permalink