Bump the cargo group across 1 directory with 7 updates #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps the cargo group with 7 updates in the / directory: | Package | From | To | | --- | --- | --- | | [time](https://github.com/time-rs/time) | `0.3.21` | `0.3.34` | | [openssl](https://github.com/sfackler/rust-openssl) | `0.10.52` | `0.10.60` | | [h2](https://github.com/hyperium/h2) | `0.3.19` | `0.3.26` | | [libgit2-sys](https://github.com/rust-lang/git2-rs) | `0.15.1+1.6.4` | `0.15.2+1.6.4` | | [rustix](https://github.com/bytecodealliance/rustix) | `0.36.14` | `0.36.17` | | [shlex](https://github.com/comex/rust-shlex) | `1.1.0` | `1.3.0` | | [unsafe-libyaml](https://github.com/dtolnay/unsafe-libyaml) | `0.2.8` | `0.2.11` | Updates `time` from 0.3.21 to 0.3.34 - [Release notes](https://github.com/time-rs/time/releases) - [Changelog](https://github.com/time-rs/time/blob/main/CHANGELOG.md) - [Commits](time-rs/time@v0.3.21...v0.3.34) Updates `openssl` from 0.10.52 to 0.10.60 - [Release notes](https://github.com/sfackler/rust-openssl/releases) - [Commits](sfackler/rust-openssl@openssl-v0.10.52...openssl-v0.10.60) Updates `h2` from 0.3.19 to 0.3.26 - [Release notes](https://github.com/hyperium/h2/releases) - [Changelog](https://github.com/hyperium/h2/blob/v0.3.26/CHANGELOG.md) - [Commits](hyperium/h2@v0.3.19...v0.3.26) Updates `libgit2-sys` from 0.15.1+1.6.4 to 0.15.2+1.6.4 - [Changelog](https://github.com/rust-lang/git2-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/git2-rs/commits) Updates `rustix` from 0.36.14 to 0.36.17 - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](bytecodealliance/rustix@v0.36.14...v0.36.17) Updates `shlex` from 1.1.0 to 1.3.0 - [Changelog](https://github.com/comex/rust-shlex/blob/master/CHANGELOG.md) - [Commits](https://github.com/comex/rust-shlex/commits) Updates `unsafe-libyaml` from 0.2.8 to 0.2.11 - [Release notes](https://github.com/dtolnay/unsafe-libyaml/releases) - [Commits](dtolnay/unsafe-libyaml@0.2.8...0.2.11) --- updated-dependencies: - dependency-name: time dependency-type: direct:production dependency-group: cargo - dependency-name: openssl dependency-type: direct:production dependency-group: cargo - dependency-name: h2 dependency-type: indirect dependency-group: cargo - dependency-name: libgit2-sys dependency-type: indirect dependency-group: cargo - dependency-name: rustix dependency-type: indirect dependency-group: cargo - dependency-name: shlex dependency-type: indirect dependency-group: cargo - dependency-name: unsafe-libyaml dependency-type: indirect dependency-group: cargo ... Signed-off-by: dependabot[bot] <support@github.com>
testfailed
pushed a commit
that referenced
this pull request
Jun 12, 2024
nushell#10851) # Description Fixes: nushell#10271 Given the following script: ```shell # test.sh echo aaaaa echo bbbbb 1>&2 echo cc ``` This pr makes the following command possible: ```nushell bash test.sh err> /dev/null | lines | each {|line| $line | str length} ``` ## General idea behind the change: When nushell redirect stderr message to external file 1. it take stdout of external stream, and pass this stream to next command, so it won't block next pipeline command from running. 2. relative stderr stream are handled by `save` command These two streams are handled separately, so we need to delegate a thread to `save` command, or else we'll have a chance to hang nushell, we have meet a similar before: nushell#5625. ### One case to consider What if we're failed to save to an external stream? (Like we don't have a permission to save to a file)? In this case nushell will just print a waning message, and don't stop the following scripts from running. # User-Facing Changes ## Before ```nushell ❯ bash test2.sh err> /dev/null | lines | each {|line| $line | str length} aaaaa cc ``` ## After ```nushell ❯ bash test2.sh err> /dev/null | lines | each {|line| $line | str length} ╭───┬───╮ │ 0 │ 5 │ │ 1 │ 2 │ ╰───┴───╯ ``` BTY, after this pr, the following commands are impossible either, it's important to make sure that the implementation doesn't introduce too much costs: ```nushell ❯ echo a e> a.txt e> a.txt Error: × Can't make stderr redirection twice ╭─[entry #1:1:1] 1 │ echo a e> a.txt e> a.txt · ─┬ · ╰── try to remove one ╰──── ❯ echo a o> a.txt o> a.txt Error: × Can't make stdout redirection twice ╭─[entry #2:1:1] 1 │ echo a o> a.txt o> a.txt · ─┬ · ╰── try to remove one ╰──── ```
testfailed
pushed a commit
that referenced
this pull request
Jun 12, 2024
Goes towards implementing nushell#10598, which asks for a spread operator in lists, in records, and when calling commands (continuation of nushell#11006, which only implements it in lists) # Description This PR is for adding a spread operator that can be used when building records. Additional functionality can be added later. Changes: - Previously, the `Expr::Record` variant held `(Expression, Expression)` pairs. It now holds instances of an enum `RecordItem` (the name isn't amazing) that allows either a key-value mapping or a spread operator. - `...` will be treated as the spread operator when it appears before `$`, `{`, or `(` inside records (no whitespace allowed in between) (not implemented yet) - The error message for duplicate columns now includes the column name itself, because if two spread records are involved in such an error, you can't tell which field was duplicated from the spans alone `...` will still be treated as a normal string outside records, and even in records, it is not treated as a spread operator when not followed immediately by a `$`, `{`, or `(`. # User-Facing Changes Users will be able to use `...` when building records. ``` > let rec = { x: 1, ...{ a: 2 } } > $rec ╭───┬───╮ │ x │ 1 │ │ a │ 2 │ ╰───┴───╯ > { foo: bar, ...$rec, baz: blah } ╭─────┬──────╮ │ foo │ bar │ │ x │ 1 │ │ a │ 2 │ │ baz │ blah │ ╰─────┴──────╯ ``` If you want to update a field of a record, you'll have to use `merge` instead: ``` > { ...$rec, x: 5 } Error: nu::shell::column_defined_twice × Record field or table column used twice: x ╭─[entry #2:1:1] 1 │ { ...$rec, x: 5 } · ──┬─ ┬ · │ ╰── field redefined here · ╰── field first defined here ╰──── > $rec | merge { x: 5 } ╭───┬───╮ │ x │ 5 │ │ a │ 2 │ ╰───┴───╯ ``` # Tests + Formatting # After Submitting
testfailed
pushed a commit
that referenced
this pull request
Jun 12, 2024
) # Description Fixes: nushell#11143 # User-Facing Changes Take the following as example: ```nushell module foo { export def bar [] {}; export def baz [] {} } ``` `use foo bar baz` will be error: ``` ❯ use foo c d Error: nu::parser::wrong_import_pattern × Wrong import pattern structure. ╭─[entry #2:1:1] 1 │ use foo c d · ┬ · ╰── Trying to import something but the parent `c` is not a module, maybe you want to try `use <module> [<name1>, <name2>]` ╰──── ``` # Tests + Formatting Done
testfailed
pushed a commit
that referenced
this pull request
Jun 12, 2024
this will allow to run ```nushell format date --list | get 0 ``` and get ``` ─────────────┬─────────────────────────────────────────────────────────── Specification│%Y Example │2023 Description │The full proleptic Gregorian year, zero-padded to 4 digits. ─────────────┴─────────────────────────────────────────────────────────── ``` instead of currently ``` Error: nu::parser::input_type_mismatch × Command does not support string input. ╭─[entry #2:1:1] 1 │ format date --list | get 0 · ─┬─ · ╰── command doesn't support string input ╰──── ```
testfailed
pushed a commit
that referenced
this pull request
Jun 12, 2024
# Description
Currently, when writing a record, if you don't give the value for a
field, the syntax error highlights the entire record instead of
pinpointing the issue. Here's some examples:
```nushell
> { a: 2, 3 } # Missing colon (and value)
Error: nu::parser::parse_mismatch
× Parse mismatch during operation.
╭─[entry #2:1:1]
1 │ { a: 2, 3 }
· ─────┬─────
· ╰── expected record
╰────
> { a: 2, 3: } # Missing value
Error: nu::parser::parse_mismatch
× Parse mismatch during operation.
╭─[entry nushell#3:1:1]
1 │ { a: 2, 3: }
· ──────┬─────
· ╰── expected record
╰────
> { a: 2, 3 4 } # Missing colon
Error: nu::parser::parse_mismatch
× Parse mismatch during operation.
╭─[entry nushell#4:1:1]
1 │ { a: 2, 3 4 }
· ──────┬──────
· ╰── expected record
╰────
```
In all of them, the entire record is highlighted red because an
`Expr::Garbage` is returned covering that whole span:
This PR is for highlighting only the part inside the record that could
not be parsed. If the record literal is big, an error message pointing
to the start of where the parser thinks things went wrong should help
people fix their code.
# User-Facing Changes
Below are screenshots of the new errors:
If there's a stray record key right before the record ends, it
highlights only that key and tells the user it expected a colon after
it:
If the record ends before the value for the last field was given, it
highlights the key and colon of that field and tells the user it
expected a value after the colon:
If there are two consecutive expressions without a colon between them,
it highlights everything from the second expression to the end of the
record and tells the user it expected a colon. I was tempted to add a
help message suggesting adding a colon in between, but that may not
always be the right thing to do.
# Tests + Formatting
# After Submitting
testfailed
pushed a commit
that referenced
this pull request
Jun 12, 2024
# Description This is a follow up to: nushell#11365 After this pr, `--flag: bool` is no longer allowed. I think `ParseWarning::Deprecated` is useful when we want to deprecated something at syntax level, so I just leave it there for now. # User-Facing Changes ## Before ``` ❯ def foo [--b: bool] {} Error: × Deprecated: --flag: bool ╭─[entry nushell#15:1:1] 1 │ def foo [--b: bool] {} · ──┬─ · ╰── `--flag: bool` is deprecated and will be removed in 0.90. Please use `--flag` instead, more info: https://www.nushell.sh/book/custom_commands.html ╰──── ``` ## After ``` ❯ def foo [--b: bool] {} Error: × Type annotations are not allowed for boolean switches. ╭─[entry #2:1:1] 1 │ def foo [--b: bool] {} · ──┬─ · ╰── Remove the `: bool` type annotation. ╰──── ``` # Tests + Formatting Done
testfailed
pushed a commit
that referenced
this pull request
Jun 12, 2024
…r ints (nushell#11724) # Description This PR changes `into int` and `into filesize` so that they allow thousands separators. ### Before ```nushell ❯ '1,000' | into filesize Error: nu::shell::cant_convert × Can't convert to int. ╭─[entry #1:1:1] 1 │ '1,000' | into filesize · ───┬─── · ╰── can't convert string to int ╰──── ❯ '1,000' | into int Error: nu:🐚:cant_convert × Can't convert to int. ╭─[entry #2:1:1] 1 │ '1,000' | into int · ────┬─── · ╰── can't convert string to int ╰──── help: string "1,000" does not represent a valid integer ``` ### After ```nushell ❯ '1,000' | into filesize 1.0 KB ❯ '1,000' | into int 1000 ``` This works by getting the system locale and from that, determining what the thousands separator is. So, hopefully, this will work across locales. # 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. -->
testfailed
pushed a commit
that referenced
this pull request
Jun 12, 2024
# Description Close: nushell#9673 Close: nushell#8277 Close: nushell#10944 This pr introduces the following syntax: 1. `e>|`, pipe stderr to next command. Example: `$env.FOO=bar nu --testbin echo_env_stderr FOO e>| str length` 2. `o+e>|` and `e+o>|`, pipe both stdout and stderr to next command, example: `$env.FOO=bar nu --testbin echo_env_mixed out-err FOO FOO e+o>| str length` Note: it only works for external commands. ~There is no different for internal commands, that is, the following three commands do the same things:~ Edit: it raises errors if we want to pipes for internal commands ``` ❯ ls e>| str length Error: × `e>|` only works with external streams ╭─[entry #1:1:1] 1 │ ls e>| str length · ─┬─ · ╰── `e>|` only works on external streams ╰──── ❯ ls e+o>| str length Error: × `o+e>|` only works with external streams ╭─[entry #2:1:1] 1 │ ls e+o>| str length · ──┬── · ╰── `o+e>|` only works on external streams ╰──── ``` This can help us to avoid some strange issues like the following: `$env.FOO=bar (nu --testbin echo_env_stderr FOO) e>| str length` Which is hard to understand and hard to explain to users. # User-Facing Changes Nan # Tests + Formatting To be done # After Submitting Maybe update documentation about these syntax.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps the cargo group with 7 updates in the / directory:
0.3.210.3.340.10.520.10.600.3.190.3.260.15.1+1.6.40.15.2+1.6.40.36.140.36.171.1.01.3.00.2.80.2.11Updates
timefrom 0.3.21 to 0.3.34Release notes
Sourced from time's releases.
Changelog
Sourced from time's changelog.
... (truncated)
Commits
f11f9b2v0.3.34 releaseef7bfbdfix unsigned to signed conversion bug (#656)76468cbv0.3.33 release6c2b602Fix wasm32-unknown-unknown build (#655)ff3255fv0.3.32 released3dd5c9DeprecateDuration::time_fn8a0dc70Remove markdown files in favor of org-wide config980878bBuild docs using org-wide workflow, change audit4baf6b3Remove documentation of deprecated feature flagbe932d8Adds support to serialize and deserialize timestamps with different resolutio...Updates
opensslfrom 0.10.52 to 0.10.60Release notes
Sourced from openssl's releases.
... (truncated)
Commits
8f4b97aMerge pull request #2104 from alex/bump-for-releasedf66283Release openssl v0.10.60 and openssl-sys v0.9.961a09dc8Merge pull request #2102 from sfackler/ex-leakb0a1da5Merge branch 'master' into ex-leakf456b60Merge pull request #2099 from alex/deprecate-store-ref-objectsa8413b8Merge pull request #2100 from alex/symm-update-uncheckeda92c237clippye839496Don't leak when overwriting ex data602d38dAddedupdate_uncheckedtosymm::Cryptercf9681afixes #2096 -- deprecateX509StoreRef::objects, it is unsoundUpdates
h2from 0.3.19 to 0.3.26Release notes
Sourced from h2's releases.
... (truncated)
Changelog
Sourced from h2's changelog.
Commits
357127ev0.3.261a357aafix: limit number of CONTINUATION frames allowed5b6c9e0refactor: cleanup new unused warnings (#757)3a79832v0.3.2594e80b1perf: optimize header list size calculations (#750)7243ab5Prepare v0.3.24d919cd6streams: limit error resets for misbehaving connectionsa7eb14av0.3.23b668c7ffix: streams awaiting capacity lockout (#730) (#734)0f412d8v0.3.22Updates
libgit2-sysfrom 0.15.1+1.6.4 to 0.15.2+1.6.4Commits
Updates
rustixfrom 0.36.14 to 0.36.17Commits
76c998cchore: Release rustix version 0.36.171c6013aFix p{read,write}v{,v2}'s encoding of the offset argument on Linux. (#896) (#...6534992chore: Release rustix version 0.36.164928cf7Disable riscv64 testing.8cc159cFix thetest_ttyname_oktest when /dev/stdin is inaccessable. (#821)6dc7ba9Downgrade dependencies and disable tests to compile under Rust 1.48.ded8986Disable MIPS in CI. (#793)739f9c3Fixes forDiron macOS, FreeBSD, and WASI.87481a9Merge pull request from GHSA-c827-hfw6-qwvm5b764b5chore: Release rustix version 0.36.15Updates
shlexfrom 1.1.0 to 1.3.0Changelog
Sourced from shlex's changelog.
Commits
Updates
unsafe-libyamlfrom 0.2.8 to 0.2.11Release notes
Sourced from unsafe-libyaml's releases.
Commits
a7b8d1fRelease 0.2.117c42792Merge pull request #27 from dtolnay/simplekeyseb7de7eFix quadratic behavior in yaml_parser_fetch_more_tokens7440d58Merge pull request #25 from jayvdb/typosb3496cefix typos63131f5Explicitly disable unsafe_op_in_unsafe_fn lint61f3ab8Release 0.2.10d90d7abClean up some redundant casts7755559Merge pull request #24 from dtolnay/mallocalignb8a0863Fix insufficient alignment of malloc's return value on 32-bitDependabot 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 commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.