Skip to content

add log on nesting feature - #184

Merged
yanganto merged 9 commits into
mainfrom
log-nesting
Sep 12, 2026
Merged

yanganto merged 9 commits into
mainfrom
log-nesting

Conversation

@yanganto

@yanganto yanganto commented Sep 8, 2026

Copy link
Copy Markdown
Owner

No description provided.

@yanganto
yanganto force-pushed the log-nesting branch 3 times, most recently from 4f8d5f5 to 4b0ea0b Compare September 12, 2026 03:11
@yanganto
yanganto marked this pull request as ready for review September 12, 2026 05:11
@yanganto
yanganto force-pushed the log-nesting branch 2 times, most recently from 856bd21 to fb6d54d Compare September 12, 2026 06:13
@yanganto
yanganto merged commit 4c17390 into main Sep 12, 2026
3 checks passed
@yanganto
yanganto deleted the log-nesting branch September 12, 2026 07:39
kp-mariappan-ramasamy added a commit to expressvpn/lightway that referenced this pull request Sep 15, 2026
struct-patch 0.14.2 leaks `#[cfg(feature = "nesting")]` attributes into the
code generated by the `Patch` derive. Those cfgs are evaluated against the
consuming crate's features rather than struct-patch's own, so lightway-client
(which has no `nesting` feature) trips rustc's `unexpected_cfgs` lint:

    error: unexpected `cfg` condition value: `nesting`
      --> lightway-client/src/config.rs:30:71

Under `-D warnings` this is a hard failure, which broke the lint, Windows,
Nix test and mobile CI jobs. Enabling struct-patch's `nesting` feature does
not help, since the cfg resolves in the downstream crate.

Drop the pin once a fixed release is published.

Upstream issue: yanganto/struct-patch#185
Introduced by:  yanganto/struct-patch#184
Changes:        yanganto/struct-patch@v0.14.1...v0.14.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant