embarkstudios/relnotes

Automatic GitHub Release Notes

relnotes's Issues

Update to v0.3 of Embark's standard lints

Embark uses a standard set of lints across all repositories. We just upgraded
to version 0.3 of these lints, and this repository needs to be updated to
the new set of lints with any warnings fixed.

Steps

1. Copy the contents of the lints.rs file from
   EmbarkStudios/rust-ecosystem and replace the old list of lints in the
   src/lib.rs and/or src/main.rs files with the new list.
2. Run cargo clippy
3. Update and fix any code that now triggers a new warning.

`there is no reactor running, must be called from the context of a Tokio 1.x runtime`

Describe the bug
I wanted to try out relnotes for cargo-generate but I'm getting this error message:

relnotes cargo-generate/[email protected]
[2021-02-08T19:01:33Z INFO  relnotes] Using `0.5.3` as version number.
thread 'main' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime', /Users/d34dl0ck/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.2.0/src/runtime/blocking/pool.rs:85:33
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

To Reproduce
Steps to reproduce the behavior:

1. just run relnotes cargo-generate/[email protected]
2. same happens when providing a config file
3. 'there is no reactor running, must be called from the context of a Tokio 1.x runtime'

Expected behavior
It should work as described in the README.

Device:

• MacOS 11.2 (amd64)

Additional context

cargo --version && rustc --version
cargo 1.49.0 (d00d64df9 2020-12-05)
rustc 1.49.0 (e1884a8e3 2020-12-29)