aya/aya-log/Cargo.toml

[package]
name = "aya-log"
version = "0.1.13"
description = "A logging library for eBPF programs."
keywords = ["bpf", "ebpf", "log", "logging"]
license = "MIT OR Apache-2.0"
authors = ["The Aya Contributors"]
repository = "https://github.com/aya-rs/aya-log"
readme = "README.md"
documentation = "https://docs.rs/aya-log"
edition = "2021"

[dependencies]
aya = { path = "../aya", version = "0.11.0", features = ["async_tokio"] }
aya-log-common = { path = "../aya-log-common", version = "0.1.13" }
thiserror = "1"
log = "0.4"
bytes = "1.1"
tokio = { version = "1.24" }

[dev-dependencies]
env_logger = "0.10"
testing_logger = "0.1.1"

[lib]
path = "src/lib.rs"
Re-organize into a single workspace This commit moves the aya-log projects from the subtree and adds them to the main cargo workspace. It also brings the BPF crates into the workspace and moves the macro crates up a level since they aren't BPF code. Miri was disabled for aya-bpf as the previous config wasn't actually checking anything. CI, clippy, fmt and release configurations have all been adjusted appropriately. CI was not properly running for other supported arches which was also ixed here. Signed-off-by: Dave Tucker <dave@dtucker.co.uk> 2 years ago			`[package]`
			`name = "aya-log"`
{{crate_name}}: release version 0.1.13 2 years ago			`version = "0.1.13"`
Re-organize into a single workspace This commit moves the aya-log projects from the subtree and adds them to the main cargo workspace. It also brings the BPF crates into the workspace and moves the macro crates up a level since they aren't BPF code. Miri was disabled for aya-bpf as the previous config wasn't actually checking anything. CI, clippy, fmt and release configurations have all been adjusted appropriately. CI was not properly running for other supported arches which was also ixed here. Signed-off-by: Dave Tucker <dave@dtucker.co.uk> 2 years ago			`description = "A logging library for eBPF programs."`
toml: add formatter and check in CI 1 year ago			`keywords = ["bpf", "ebpf", "log", "logging"]`
Re-organize into a single workspace This commit moves the aya-log projects from the subtree and adds them to the main cargo workspace. It also brings the BPF crates into the workspace and moves the macro crates up a level since they aren't BPF code. Miri was disabled for aya-bpf as the previous config wasn't actually checking anything. CI, clippy, fmt and release configurations have all been adjusted appropriately. CI was not properly running for other supported arches which was also ixed here. Signed-off-by: Dave Tucker <dave@dtucker.co.uk> 2 years ago			`license = "MIT OR Apache-2.0"`
			`authors = ["The Aya Contributors"]`
			`repository = "https://github.com/aya-rs/aya-log"`
			`readme = "README.md"`
			`documentation = "https://docs.rs/aya-log"`
Change from Rust edition 2018 to 2021 Rust 2021 adds more core prelude imports, including `TryFrom` and `TryInto`. Signed-off-by: Michal Rostecki <vadorovsky@gmail.com> 2 years ago			`edition = "2021"`
Re-organize into a single workspace This commit moves the aya-log projects from the subtree and adds them to the main cargo workspace. It also brings the BPF crates into the workspace and moves the macro crates up a level since they aren't BPF code. Miri was disabled for aya-bpf as the previous config wasn't actually checking anything. CI, clippy, fmt and release configurations have all been adjusted appropriately. CI was not properly running for other supported arches which was also ixed here. Signed-off-by: Dave Tucker <dave@dtucker.co.uk> 2 years ago
			`[dependencies]`
toml: add formatter and check in CI 1 year ago			`aya = { path = "../aya", version = "0.11.0", features = ["async_tokio"] }`
aya-log: Move the `Pod` implementations from aya-log-common to aya-log Keeping the `Pod` implementations and optional dependency on aya in aya-log-common breaks the clippy checks (which are made on the entire workspace). The reason is that when different crates inside the workspace have the same dependency with different features, that dependency is built only once with the sum of features needed by all crates. It's not being built separately with different feature sets. That's why, before this change, aya-log-common was built once for the entire workspace with `userspace` feature enabled. That made importing aya-log-ebpf inside integration-ebpf impossible. The aya-log-common build, with `userspace` feature enabled, was pulling std as a dependency. Therefore, importing aya-log-ebpf inside integration-ebpf resulted in including std and errors like: ``` error[E0152]: found duplicate lang item `panic_impl` --> test/integration-ebpf/src/log.rs:23:1 \| 23 \| fn panic(_info: &core::panic::PanicInfo) -> ! { \| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ \| = note: the lang item is first defined in crate `std` (which `aya` depends on) ``` This change fixes the problem by removing the `userspace` feature from aya-log-common and moving the `Pod` implementations to aya-log. 2 years ago			`aya-log-common = { path = "../aya-log-common", version = "0.1.13" }`
Re-organize into a single workspace This commit moves the aya-log projects from the subtree and adds them to the main cargo workspace. It also brings the BPF crates into the workspace and moves the macro crates up a level since they aren't BPF code. Miri was disabled for aya-bpf as the previous config wasn't actually checking anything. CI, clippy, fmt and release configurations have all been adjusted appropriately. CI was not properly running for other supported arches which was also ixed here. Signed-off-by: Dave Tucker <dave@dtucker.co.uk> 2 years ago			`thiserror = "1"`
			`log = "0.4"`
			`bytes = "1.1"`
Update Tokio and inventory Signed-off-by: Michal Rostecki <vadorovsky@gmail.com> 2 years ago			`tokio = { version = "1.24" }`
Re-organize into a single workspace This commit moves the aya-log projects from the subtree and adds them to the main cargo workspace. It also brings the BPF crates into the workspace and moves the macro crates up a level since they aren't BPF code. Miri was disabled for aya-bpf as the previous config wasn't actually checking anything. CI, clippy, fmt and release configurations have all been adjusted appropriately. CI was not properly running for other supported arches which was also ixed here. Signed-off-by: Dave Tucker <dave@dtucker.co.uk> 2 years ago
			`[dev-dependencies]`
build(deps): update env_logger requirement from 0.9 to 0.10 Updates the requirements on [env_logger](https://github.com/rust-cli/env_logger) to permit the latest version. - [Release notes](https://github.com/rust-cli/env_logger/releases) - [Changelog](https://github.com/rust-cli/env_logger/blob/main/CHANGELOG.md) - [Commits](https://github.com/rust-cli/env_logger/compare/v0.9.0...v0.10.0) --- updated-dependencies: - dependency-name: env_logger dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> 2 years ago			`env_logger = "0.10"`
Re-organize into a single workspace This commit moves the aya-log projects from the subtree and adds them to the main cargo workspace. It also brings the BPF crates into the workspace and moves the macro crates up a level since they aren't BPF code. Miri was disabled for aya-bpf as the previous config wasn't actually checking anything. CI, clippy, fmt and release configurations have all been adjusted appropriately. CI was not properly running for other supported arches which was also ixed here. Signed-off-by: Dave Tucker <dave@dtucker.co.uk> 2 years ago			`testing_logger = "0.1.1"`

			`[lib]`
			`path = "src/lib.rs"`