mirrors/rust-lightning
1
0
Fork 0
mirror of https://github.com/lightningdevkit/rust-lightning.git synced 2025-02-24 15:02:20 +01:00
Code Issues Projects Releases Packages Wiki Activity
rust-lightning/lightning-background-processor/Cargo.toml

35 lines
1.1 KiB
TOML
Raw Normal View History

Add BackgroundProcessor for ChannelManager persistence and other Other includes calling timer_chan_freshness_every_minute() and in the future, possibly persisting channel graph data. This struct is suitable for things that need to happen periodically and can happen in the background.
2021-01-11 18:03:32 -05:00
[package]
Rename `background-processor` to `lightning-background-processor` This matches our naming scheme better and fits better on crates.io. Also drop the version to 0.0.1 to match our versioning scheme better.
2021-03-08 18:48:24 -05:00
name = "lightning-background-processor"
Bump crate versions to 0.0.123-beta/invoice 0.31-beta
2024-04-19 01:03:03 +00:00
version = "0.0.123-beta"
Add BackgroundProcessor for ChannelManager persistence and other Other includes calling timer_chan_freshness_every_minute() and in the future, possibly persisting channel graph data. This struct is suitable for things that need to happen periodically and can happen in the background.
2021-01-11 18:03:32 -05:00
authors = ["Valentine Wallace <vwallace@protonmail.com>"]
Update licenses and add missing fields in Cargo.toml files
2021-03-09 16:51:14 -05:00
license = "MIT OR Apache-2.0"
http => https
2023-07-23 08:58:41 +03:00
repository = "https://github.com/lightningdevkit/rust-lightning"
Update licenses and add missing fields in Cargo.toml files
2021-03-09 16:51:14 -05:00
description = """
Utilities to perform required background tasks for Rust Lightning.
"""
Bump MSRV to rustc 1.63.0 and edition to 2021 .. which is a reasonable common ground, also supported by Debian stable.
2023-10-24 15:16:38 +02:00
edition = "2021"
Add BackgroundProcessor for ChannelManager persistence and other Other includes calling timer_chan_freshness_every_minute() and in the future, possibly persisting channel graph data. This struct is suitable for things that need to happen periodically and can happen in the background.
2021-01-11 18:03:32 -05:00
Generate docs with features for docs.rs Enable generating docs using --all-features or --features="std" where applicable. Additionally, use doc_auto_cfg to tag items requiring a feature. https://doc.rust-lang.org/nightly/rustdoc/unstable-features.html#doc_auto_cfg-automatically-generate-doccfg This requires building with nightly, which is what is used by docs.rs. https://docs.rs/about/builds To test locally, use: RUSTDOCFLAGS="--cfg docsrs" cargo +nightly doc ...
2022-02-11 22:22:20 -06:00
[package.metadata.docs.rs]
all-features = true
rustdoc-args = ["--cfg", "docsrs"]
Add `futures` CI check This adds testing of the `futures` feature to CI. In order to avoid introducing a dependency on `std`, we switch to using the `futures-util` crate directly enabling only a subset of features. To this end, we also switch to using the `select_biased!` macro, which is equivalent to `select!` except that it doesn't choose ready futures pseudo-randomly at runtime.
2022-10-10 14:47:18 -04:00
[features]
Remove `futures` dependency in `lightning-background-processor` As `futures` apparently makes no guarantees on MSRVs even in patch releases we really can't rely on it at all, and while it currently has an acceptable MSRV without the macros feature, its best to just remove it wholesale. Luckily, removing it is relatively trivial, even if it requires the most trivial of unsafe tags.
2023-03-30 22:11:22 +00:00
futures = [ ]
Drop the `no-std` feature from BP and drop feature implications Now that we don't have to have everything in our entire ecosystem use the same `std`/`no-std` feature combinations we should start by untangling our own features a bit. This takes the first step by removing the `no-std` feature entirely from the `lightning-background-processor` crate and removing most feature implications on dependencies from the remaining `std` feature. It also addresses a CI oversight where we were not testing `lightning-background-processor` without the `std` feature in CI at all.
2024-08-16 19:07:05 +00:00
std = []
Make `background-processor` no-std-friendly (ish) This makes `background-processor` build without `std` at all. This isn't particularly useful in the general no-std case as `background-processor` is only useful with the `futures` feature, and async will generally need `std` in some way or another. Still, it ensures we don't end up reintroducing a dependency on the current time, which breaks `wasm` use-cases.
2023-01-17 00:16:48 +00:00
default = ["std"]
Add `futures` CI check This adds testing of the `futures` feature to CI. In order to avoid introducing a dependency on `std`, we switch to using the `futures-util` crate directly enabling only a subset of features. To this end, we also switch to using the `select_biased!` macro, which is equivalent to `select!` except that it doesn't choose ready futures pseudo-randomly at runtime.
2022-10-10 14:47:18 -04:00
Add BackgroundProcessor for ChannelManager persistence and other Other includes calling timer_chan_freshness_every_minute() and in the future, possibly persisting channel graph data. This struct is suitable for things that need to happen periodically and can happen in the background.
2021-01-11 18:03:32 -05:00
[dependencies]
Upgrade rust-bitcoin to 0.32.2.
2024-08-16 08:02:50 -07:00
bitcoin = { version = "0.32.2", default-features = false }
Bump crate versions to 0.0.123-beta/invoice 0.31-beta
2024-04-19 01:03:03 +00:00
lightning = { version = "0.0.123-beta", path = "../lightning", default-features = false }
lightning-rapid-gossip-sync = { version = "0.0.123-beta", path = "../lightning-rapid-gossip-sync", default-features = false }
Add BackgroundProcessor for ChannelManager persistence and other Other includes calling timer_chan_freshness_every_minute() and in the future, possibly persisting channel graph data. This struct is suitable for things that need to happen periodically and can happen in the background.
2021-01-11 18:03:32 -05:00
[dev-dependencies]
Update tokio version to the latest to avoid tokio versions with security bugs. This commit will set tokio version requirement to >=1.35.0, <2.0.0 to avoid versions with security issues (https://rustsec.org/packages/tokio.html).
2023-12-13 10:37:58 -08:00
tokio = { version = "1.35", features = [ "macros", "rt", "rt-multi-thread", "sync", "time" ] }
Bump crate versions to 0.0.123-beta/invoice 0.31-beta
2024-04-19 01:03:03 +00:00
lightning = { version = "0.0.123-beta", path = "../lightning", features = ["_test_utils"] }
lightning-invoice = { version = "0.31.0-beta", path = "../lightning-invoice" }
lightning-persister = { version = "0.0.123-beta", path = "../lightning-persister" }
Use native check-cfg lint in cargo beta This uses the newly introduced conditional configuration checks that are now configurable withint Cargo (beta). This allows us to get rid of our custom python script that checks for expected features and cfgs. This does introduce a warning regarding the unknown lint in Cargo versions prior to the current beta, but since these are not rustc errors, they won't break any builds with the "-D warnings" RUSTFLAG. Moving to this lint actually exposed the "strict" feature not being present in the lightning-invoice crate, as our python script didnt correctly parse the cfg_attr where it appeared.
2024-07-12 11:23:50 +02:00
[lints]
workspace = true
Reference in a new issue Copy permalink