Mock Version: 6.3 Mock Version: 6.3 Mock Version: 6.3 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target i686 --nodeps /builddir/build/SPECS/rust-libcst.spec'], chrootPath='/var/lib/mock/f42-build-side-115005-61035727-6588078/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=201600uid=1000gid=425user='mockbuild'unshare_net=TrueprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.b1a_734z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.b1a_734z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '91cf7d7b892643e2b670ae46c0135975', '-D', '/var/lib/mock/f42-build-side-115005-61035727-6588078/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.b1a_734z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target i686 --nodeps /builddir/build/SPECS/rust-libcst.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: i686 Building for target i686 setting SOURCE_DATE_EPOCH=1752364800 Wrote: /builddir/build/SRPMS/rust-libcst-1.8.2-1.fc42.src.rpm Child return code was: 0 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noclean --target i686 --nodeps /builddir/build/SPECS/rust-libcst.spec'], chrootPath='/var/lib/mock/f42-build-side-115005-61035727-6588078/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=201600uid=1000gid=425user='mockbuild'unshare_net=TrueraiseExc=FalseprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.b1a_734z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.b1a_734z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', 'c0542692593248e3823363671cc89fd5', '-D', '/var/lib/mock/f42-build-side-115005-61035727-6588078/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.b1a_734z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -br --noclean --target i686 --nodeps /builddir/build/SPECS/rust-libcst.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: i686 Building for target i686 setting SOURCE_DATE_EPOCH=1752364800 Executing(%mkbuilddir): /bin/sh -e /var/tmp/rpm-tmp.jwD3Ke Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.md45NJ + umask 022 + cd /builddir/build/BUILD/rust-libcst-1.8.2-build + cd /builddir/build/BUILD/rust-libcst-1.8.2-build + rm -rf libcst-1.8.2 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/libcst-1.8.2.crate + STATUS=0 + '[' 0 -ne 0 ']' + cd libcst-1.8.2 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/libcst-fix-metadata.diff + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + set -euo pipefail + /usr/bin/mkdir -p target/rpm + /usr/bin/ln -s rpm target/release + /usr/bin/rm -rf .cargo/ + /usr/bin/mkdir -p .cargo + cat + cat + /usr/bin/rm -f Cargo.lock + /usr/bin/rm -f Cargo.toml.orig + rm tests/parser_roundtrip.rs + find -type f -print -exec dos2unix --keepdate '{}' + ./.cargo_vcs_info.json ./Grammar ./LICENSE ./README.md ./benches/parser_benchmark.rs ./src/bin.rs ./src/lib.rs ./src/nodes/codegen.rs ./src/nodes/expression.rs ./src/nodes/inflate_helpers.rs ./src/nodes/macros.rs ./src/nodes/mod.rs ./src/nodes/module.rs ./src/nodes/op.rs ./src/nodes/parser_config.rs ./src/nodes/py_cached.rs ./src/nodes/statement.rs ./src/nodes/test_utils.rs ./src/nodes/traits.rs ./src/nodes/whitespace.rs ./src/parser/errors.rs ./src/parser/grammar.rs ./src/parser/mod.rs ./src/parser/numbers.rs ./src/py.rs ./src/tokenizer/core/LICENSE ./src/tokenizer/core/README.md ./src/tokenizer/core/mod.rs ./src/tokenizer/core/string_types.rs ./src/tokenizer/debug_utils.rs ./src/tokenizer/mod.rs ./src/tokenizer/operators.rs ./src/tokenizer/tests.rs ./src/tokenizer/text_position/char_width.rs ./src/tokenizer/text_position/mod.rs ./src/tokenizer/whitespace_parser.rs ./tests/.gitattributes ./tests/fixtures/big_binary_operator.py ./tests/fixtures/class_craziness.py ./tests/fixtures/comments.py ./tests/fixtures/comparisons.py ./tests/fixtures/dangling_indent.py ./tests/fixtures/decorated_function_without_body.py ./tests/fixtures/dysfunctional_del.py ./tests/fixtures/expr.py ./tests/fixtures/expr_statement.py ./tests/fixtures/fun_with_func_defs.py ./tests/fixtures/global_nonlocal.py ./tests/fixtures/import.py ./tests/fixtures/indents_but_no_eol_before_eof.py ./tests/fixtures/just_a_comment_without_nl.py ./tests/fixtures/malicious_match.py ./tests/fixtures/mixed_newlines.py ./tests/fixtures/pep646.py ./tests/fixtures/raise.py ./tests/fixtures/smol_statements.py ./tests/fixtures/spacious_spaces.py ./tests/fixtures/starry_tries.py ./tests/fixtures/suicidal_slices.py ./tests/fixtures/super_strings.py ./tests/fixtures/terrible_tries.py ./tests/fixtures/trailing_comment_without_nl.py ./tests/fixtures/trailing_whitespace.py ./tests/fixtures/tuple_shenanigans.py ./tests/fixtures/type_parameters.py ./tests/fixtures/vast_emptiness.py ./tests/fixtures/with_wickedness.py ./tests/fixtures/wonky_walrus.py ./Cargo.toml ./.cargo/config.toml dos2unix: converting file ./.cargo_vcs_info.json to Unix format... dos2unix: converting file ./Grammar to Unix format... dos2unix: converting file ./LICENSE to Unix format... dos2unix: converting file ./README.md to Unix format... dos2unix: converting file ./benches/parser_benchmark.rs to Unix format... dos2unix: converting file ./src/bin.rs to Unix format... dos2unix: converting file ./src/lib.rs to Unix format... dos2unix: converting file ./src/nodes/codegen.rs to Unix format... dos2unix: converting file ./src/nodes/expression.rs to Unix format... dos2unix: converting file ./src/nodes/inflate_helpers.rs to Unix format... dos2unix: converting file ./src/nodes/macros.rs to Unix format... dos2unix: converting file ./src/nodes/mod.rs to Unix format... dos2unix: converting file ./src/nodes/module.rs to Unix format... dos2unix: converting file ./src/nodes/op.rs to Unix format... dos2unix: converting file ./src/nodes/parser_config.rs to Unix format... dos2unix: converting file ./src/nodes/py_cached.rs to Unix format... dos2unix: converting file ./src/nodes/statement.rs to Unix format... dos2unix: converting file ./src/nodes/test_utils.rs to Unix format... dos2unix: converting file ./src/nodes/traits.rs to Unix format... dos2unix: converting file ./src/nodes/whitespace.rs to Unix format... dos2unix: converting file ./src/parser/errors.rs to Unix format... dos2unix: converting file ./src/parser/grammar.rs to Unix format... dos2unix: converting file ./src/parser/mod.rs to Unix format... dos2unix: converting file ./src/parser/numbers.rs to Unix format... dos2unix: converting file ./src/py.rs to Unix format... dos2unix: converting file ./src/tokenizer/core/LICENSE to Unix format... dos2unix: converting file ./src/tokenizer/core/README.md to Unix format... dos2unix: converting file ./src/tokenizer/core/mod.rs to Unix format... dos2unix: converting file ./src/tokenizer/core/string_types.rs to Unix format... dos2unix: converting file ./src/tokenizer/debug_utils.rs to Unix format... dos2unix: converting file ./src/tokenizer/mod.rs to Unix format... dos2unix: converting file ./src/tokenizer/operators.rs to Unix format... dos2unix: converting file ./src/tokenizer/tests.rs to Unix format... dos2unix: converting file ./src/tokenizer/text_position/char_width.rs to Unix format... dos2unix: converting file ./src/tokenizer/text_position/mod.rs to Unix format... dos2unix: converting file ./src/tokenizer/whitespace_parser.rs to Unix format... dos2unix: converting file ./tests/.gitattributes to Unix format... dos2unix: converting file ./tests/fixtures/big_binary_operator.py to Unix format... dos2unix: converting file ./tests/fixtures/class_craziness.py to Unix format... dos2unix: converting file ./tests/fixtures/comments.py to Unix format... dos2unix: converting file ./tests/fixtures/comparisons.py to Unix format... dos2unix: converting file ./tests/fixtures/dangling_indent.py to Unix format... dos2unix: converting file ./tests/fixtures/decorated_function_without_body.py to Unix format... dos2unix: converting file ./tests/fixtures/dysfunctional_del.py to Unix format... dos2unix: converting file ./tests/fixtures/expr.py to Unix format... dos2unix: converting file ./tests/fixtures/expr_statement.py to Unix format... dos2unix: converting file ./tests/fixtures/fun_with_func_defs.py to Unix format... dos2unix: converting file ./tests/fixtures/global_nonlocal.py to Unix format... dos2unix: converting file ./tests/fixtures/import.py to Unix format... dos2unix: converting file ./tests/fixtures/indents_but_no_eol_before_eof.py to Unix format... dos2unix: converting file ./tests/fixtures/just_a_comment_without_nl.py to Unix format... dos2unix: converting file ./tests/fixtures/malicious_match.py to Unix format... dos2unix: converting file ./tests/fixtures/mixed_newlines.py to Unix format... dos2unix: converting file ./tests/fixtures/pep646.py to Unix format... dos2unix: converting file ./tests/fixtures/raise.py to Unix format... dos2unix: converting file ./tests/fixtures/smol_statements.py to Unix format... dos2unix: converting file ./tests/fixtures/spacious_spaces.py to Unix format... dos2unix: converting file ./tests/fixtures/starry_tries.py to Unix format... dos2unix: converting file ./tests/fixtures/suicidal_slices.py to Unix format... dos2unix: converting file ./tests/fixtures/super_strings.py to Unix format... dos2unix: converting file ./tests/fixtures/terrible_tries.py to Unix format... dos2unix: converting file ./tests/fixtures/trailing_comment_without_nl.py to Unix format... dos2unix: converting file ./tests/fixtures/trailing_whitespace.py to Unix format... dos2unix: converting file ./tests/fixtures/tuple_shenanigans.py to Unix format... dos2unix: converting file ./tests/fixtures/type_parameters.py to Unix format... dos2unix: converting file ./tests/fixtures/vast_emptiness.py to Unix format... dos2unix: converting file ./tests/fixtures/with_wickedness.py to Unix format... dos2unix: converting file ./tests/fixtures/wonky_walrus.py to Unix format... dos2unix: converting file ./Cargo.toml to Unix format... dos2unix: converting file ./.cargo/config.toml to Unix format... + RPM_EC=0 ++ jobs -p + exit 0 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.1HjSUx + umask 022 + cd /builddir/build/BUILD/rust-libcst-1.8.2-build + cd libcst-1.8.2 + /usr/bin/cargo2rpm --path Cargo.toml buildrequires --with-check + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/rust-libcst-1.8.2-1.fc42.buildreqs.nosrc.rpm Child return code was: 11 Dynamic buildrequires detected Going to install missing buildrequires. See root.log for details. ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noprep --noclean --target i686 --nodeps /builddir/build/SPECS/rust-libcst.spec'], chrootPath='/var/lib/mock/f42-build-side-115005-61035727-6588078/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=201600uid=1000gid=425user='mockbuild'unshare_net=TrueraiseExc=FalseprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.b1a_734z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.b1a_734z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', 'e7f501b52b144ccba4c7b76825a7b16a', '-D', '/var/lib/mock/f42-build-side-115005-61035727-6588078/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.b1a_734z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -br --noprep --noclean --target i686 --nodeps /builddir/build/SPECS/rust-libcst.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: i686 Building for target i686 setting SOURCE_DATE_EPOCH=1752364800 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.fJSAX2 + umask 022 + cd /builddir/build/BUILD/rust-libcst-1.8.2-build + cd libcst-1.8.2 + /usr/bin/cargo2rpm --path Cargo.toml buildrequires --with-check + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/rust-libcst-1.8.2-1.fc42.buildreqs.nosrc.rpm Child return code was: 11 Dynamic buildrequires detected Going to install missing buildrequires. See root.log for details. ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -ba --noprep --noclean --target i686 /builddir/build/SPECS/rust-libcst.spec'], chrootPath='/var/lib/mock/f42-build-side-115005-61035727-6588078/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=201600uid=1000gid=425user='mockbuild'unshare_net=TrueprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.b1a_734z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.b1a_734z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', 'fea7f500122148aa8a56689b7c24f2c9', '-D', '/var/lib/mock/f42-build-side-115005-61035727-6588078/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.b1a_734z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -ba --noprep --noclean --target i686 /builddir/build/SPECS/rust-libcst.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: i686 Building for target i686 setting SOURCE_DATE_EPOCH=1752364800 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.Z2XxWh + umask 022 + cd /builddir/build/BUILD/rust-libcst-1.8.2-build + cd libcst-1.8.2 + /usr/bin/cargo2rpm --path Cargo.toml buildrequires --with-check + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.6rSvc6 + umask 022 + cd /builddir/build/BUILD/rust-libcst-1.8.2-build + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd libcst-1.8.2 + /usr/bin/env CARGO_HOME=.cargo RUSTC_BOOTSTRAP=1 'RUSTFLAGS=-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' /usr/bin/cargo build -j64 -Z avoid-dev-deps --profile rpm Compiling proc-macro2 v1.0.95 Compiling unicode-ident v1.0.18 Compiling memchr v2.7.5 Compiling regex-syntax v0.8.5 Compiling paste v1.0.15 Compiling peg-runtime v0.8.5 Compiling thiserror v2.0.12 Compiling anstyle v1.0.11 Compiling unicode-width v0.2.0 Running `/usr/bin/rustc --crate-name build_script_build --edition=2021 /usr/share/cargo/registry/proc-macro2-1.0.95/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' --cfg 'feature="proc-macro"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "nightly", "proc-macro", "span-locations"))' -C metadata=cae0940125c6cb2f -C extra-filename=-f3359f0fb9456566 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/build/proc-macro2-f3359f0fb9456566 -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/usr/bin/rustc --crate-name unicode_ident --edition=2018 /usr/share/cargo/registry/unicode-ident-1.0.18/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=dcefd144d5ff9840 -C extra-filename=-55f6e005f2dbcf0c --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/usr/bin/rustc --crate-name memchr --edition=2021 /usr/share/cargo/registry/memchr-2.7.5/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="alloc"' --cfg 'feature="default"' --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("alloc", "core", "default", "libc", "logging", "rustc-dep-of-std", "std", "use_std"))' -C metadata=cec5df764a23eb46 -C extra-filename=-d5472c13b3d6260a --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/usr/bin/rustc --crate-name regex_syntax --edition=2021 /usr/share/cargo/registry/regex-syntax-0.8.5/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="std"' --cfg 'feature="unicode"' --cfg 'feature="unicode-age"' --cfg 'feature="unicode-bool"' --cfg 'feature="unicode-case"' --cfg 'feature="unicode-gencat"' --cfg 'feature="unicode-perl"' --cfg 'feature="unicode-script"' --cfg 'feature="unicode-segment"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("arbitrary", "default", "std", "unicode", "unicode-age", "unicode-bool", "unicode-case", "unicode-gencat", "unicode-perl", "unicode-script", "unicode-segment"))' -C metadata=e2431bc047493ffd -C extra-filename=-3eee5497a974c663 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/usr/bin/rustc --crate-name build_script_build --edition=2018 /usr/share/cargo/registry/paste-1.0.15/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=1f4cf28fcbf1f307 -C extra-filename=-8474ab21c50b8335 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/build/paste-8474ab21c50b8335 -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/usr/bin/rustc --crate-name build_script_build --edition=2021 /usr/share/cargo/registry/thiserror-2.0.12/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "std"))' -C metadata=9f6e68794910caf6 -C extra-filename=-4caa00bf1c775263 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/build/thiserror-4caa00bf1c775263 -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/usr/bin/rustc --crate-name peg_runtime --edition=2021 /usr/share/cargo/registry/peg-runtime-0.8.5/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("std", "unstable"))' -C metadata=51d679437419ac76 -C extra-filename=-fc09b67d6c715931 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/usr/bin/rustc --crate-name unicode_width --edition=2021 /usr/share/cargo/registry/unicode-width-0.2.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="cjk"' --cfg 'feature="default"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("cjk", "compiler_builtins", "core", "default", "no_std", "rustc-dep-of-std", "std"))' -C metadata=67bb71d388b54d1c -C extra-filename=-4655a807b9e37a94 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/usr/bin/rustc --crate-name anstyle --edition=2021 /usr/share/cargo/registry/anstyle-1.0.11/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --warn=rust_2018_idioms '--warn=clippy::zero_sized_map_values' '--warn=clippy::wildcard_imports' '--warn=clippy::verbose_file_reads' --warn=unused_qualifications --warn=unused_macro_rules --warn=unused_lifetimes --warn=unsafe_op_in_unsafe_fn --warn=unreachable_pub --warn=unnameable_types '--warn=clippy::uninlined_format_args' '--warn=clippy::trait_duplication_in_bounds' '--warn=clippy::todo' '--warn=clippy::string_to_string' '--warn=clippy::string_lit_as_bytes' '--warn=clippy::string_add_assign' '--warn=clippy::string_add' '--warn=clippy::str_to_string' '--warn=clippy::semicolon_if_nothing_returned' '--warn=clippy::self_named_module_files' '--warn=clippy::same_functions_in_if_condition' '--allow=clippy::result_large_err' '--warn=clippy::rest_pat_in_fully_bound_structs' '--warn=clippy::ref_option_ref' '--warn=clippy::redundant_feature_names' '--warn=clippy::rc_mutex' '--warn=clippy::ptr_as_ptr' '--warn=clippy::path_buf_push_overwrite' '--warn=clippy::negative_feature_names' '--warn=clippy::needless_for_each' '--allow=clippy::needless_continue' '--warn=clippy::mutex_integer' '--warn=clippy::mem_forget' '--warn=clippy::macro_use_imports' '--warn=clippy::lossy_float_literal' '--warn=clippy::linkedlist' '--allow=clippy::let_and_return' '--warn=clippy::large_types_passed_by_value' '--warn=clippy::large_stack_arrays' '--warn=clippy::large_digit_groups' '--warn=clippy::invalid_upcast_comparisons' '--warn=clippy::infinite_loop' '--warn=clippy::inefficient_to_string' '--warn=clippy::inconsistent_struct_constructor' '--warn=clippy::imprecise_flops' '--warn=clippy::implicit_clone' '--allow=clippy::if_same_then_else' '--warn=clippy::from_iter_instead_of_collect' '--warn=clippy::fn_params_excessive_bools' '--warn=clippy::float_cmp_const' '--warn=clippy::flat_map_option' '--warn=clippy::filter_map_next' '--warn=clippy::fallible_impl_from' '--warn=clippy::explicit_into_iter_loop' '--warn=clippy::explicit_deref_methods' '--warn=clippy::expl_impl_clone_on_copy' '--warn=clippy::enum_glob_use' '--warn=clippy::empty_enum' '--warn=clippy::doc_markdown' '--warn=clippy::debug_assert_with_mut_call' '--warn=clippy::dbg_macro' '--warn=clippy::create_dir' '--allow=clippy::collapsible_else_if' '--warn=clippy::checked_conversions' '--allow=clippy::branches_sharing_code' '--allow=clippy::bool_assert_comparison' --cfg 'feature="default"' --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "std"))' -C metadata=a335f3593c1aab51 -C extra-filename=-29d15de346590555 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/usr/bin/rustc --crate-name peg_runtime --edition=2021 /usr/share/cargo/registry/peg-runtime-0.8.5/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("std", "unstable"))' -C metadata=0fef85f12f938128 -C extra-filename=-7f46959e6187149e --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling annotate-snippets v0.11.5 Running `/usr/bin/rustc --crate-name annotate_snippets --edition=2021 /usr/share/cargo/registry/annotate-snippets-0.11.5/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --warn=rust_2018_idioms '--warn=clippy::zero_sized_map_values' '--warn=clippy::wildcard_imports' '--warn=clippy::verbose_file_reads' --warn=unused_qualifications --warn=unused_macro_rules --warn=unused_lifetimes --warn=unsafe_op_in_unsafe_fn --warn=unreachable_pub '--warn=clippy::uninlined_format_args' '--warn=clippy::trait_duplication_in_bounds' '--warn=clippy::todo' '--warn=clippy::string_to_string' '--warn=clippy::string_lit_as_bytes' '--warn=clippy::string_add_assign' '--warn=clippy::string_add' '--warn=clippy::str_to_string' '--warn=clippy::semicolon_if_nothing_returned' '--warn=clippy::self_named_module_files' '--warn=clippy::same_functions_in_if_condition' '--allow=clippy::result_large_err' '--warn=clippy::rest_pat_in_fully_bound_structs' '--warn=clippy::ref_option_ref' '--warn=clippy::redundant_feature_names' '--warn=clippy::rc_mutex' '--warn=clippy::ptr_as_ptr' '--warn=clippy::path_buf_push_overwrite' '--warn=clippy::negative_feature_names' '--warn=clippy::needless_for_each' '--warn=clippy::needless_continue' '--warn=clippy::mutex_integer' '--warn=clippy::mem_forget' '--warn=clippy::macro_use_imports' '--warn=clippy::lossy_float_literal' '--warn=clippy::linkedlist' '--allow=clippy::let_and_return' '--warn=clippy::large_types_passed_by_value' '--warn=clippy::large_stack_arrays' '--warn=clippy::large_digit_groups' '--warn=clippy::invalid_upcast_comparisons' '--warn=clippy::infinite_loop' '--warn=clippy::inefficient_to_string' '--warn=clippy::inconsistent_struct_constructor' '--warn=clippy::imprecise_flops' '--warn=clippy::implicit_clone' '--allow=clippy::if_same_then_else' '--warn=clippy::from_iter_instead_of_collect' '--warn=clippy::fn_params_excessive_bools' '--warn=clippy::float_cmp_const' '--warn=clippy::flat_map_option' '--warn=clippy::filter_map_next' '--warn=clippy::fallible_impl_from' '--warn=clippy::explicit_into_iter_loop' '--warn=clippy::explicit_deref_methods' '--warn=clippy::expl_impl_clone_on_copy' '--warn=clippy::enum_glob_use' '--warn=clippy::empty_enum' '--warn=clippy::doc_markdown' '--warn=clippy::debug_assert_with_mut_call' '--warn=clippy::dbg_macro' '--warn=clippy::create_dir' '--allow=clippy::collapsible_else_if' '--warn=clippy::checked_conversions' '--allow=clippy::branches_sharing_code' '--allow=clippy::bool_assert_comparison' --cfg 'feature="default"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "memchr", "simd", "testing-colors"))' -C metadata=c424e215a707339a -C extra-filename=-6a94540787ec50c7 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern anstyle=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libanstyle-29d15de346590555.rmeta --extern unicode_width=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libunicode_width-4655a807b9e37a94.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling aho-corasick v1.1.3 Running `/usr/bin/rustc --crate-name aho_corasick --edition=2021 /usr/share/cargo/registry/aho-corasick-1.1.3/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="perf-literal"' --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "logging", "perf-literal", "std"))' -C metadata=44df426194cd7c87 -C extra-filename=-ab869557dff442c7 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern memchr=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libmemchr-d5472c13b3d6260a.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/build/paste-8474ab21c50b8335/build-script-build` Running `/usr/bin/rustc --crate-name paste --edition=2018 /usr/share/cargo/registry/paste-1.0.15/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type proc-macro --emit=dep-info,link -C prefer-dynamic -C embed-bitcode=no -C debug-assertions=off --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=91d5b0cee15e3f66 -C extra-filename=-15a18b40cf04ef3a --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern proc_macro --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn --check-cfg 'cfg(no_literal_fromstr)' --check-cfg 'cfg(feature, values("protocol_feature_paste"))'` Running `/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/build/proc-macro2-f3359f0fb9456566/build-script-build` Running `/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/build/thiserror-4caa00bf1c775263/build-script-build` Running `/usr/bin/rustc --crate-name proc_macro2 --edition=2021 /usr/share/cargo/registry/proc-macro2-1.0.95/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' --cfg 'feature="proc-macro"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "nightly", "proc-macro", "span-locations"))' -C metadata=301593a9a5112701 -C extra-filename=-e337feb845d9f93c --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern unicode_ident=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libunicode_ident-55f6e005f2dbcf0c.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn --cfg wrap_proc_macro --cfg proc_macro_span --check-cfg 'cfg(fuzzing)' --check-cfg 'cfg(no_is_available)' --check-cfg 'cfg(no_literal_byte_character)' --check-cfg 'cfg(no_literal_c_string)' --check-cfg 'cfg(no_source_text)' --check-cfg 'cfg(proc_macro_span)' --check-cfg 'cfg(procmacro2_backtrace)' --check-cfg 'cfg(procmacro2_nightly_testing)' --check-cfg 'cfg(procmacro2_semver_exempt)' --check-cfg 'cfg(randomize_layout)' --check-cfg 'cfg(span_locations)' --check-cfg 'cfg(super_unstable)' --check-cfg 'cfg(wrap_proc_macro)'` Compiling quote v1.0.40 Running `/usr/bin/rustc --crate-name quote --edition=2018 /usr/share/cargo/registry/quote-1.0.40/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' --cfg 'feature="proc-macro"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "proc-macro"))' -C metadata=a983726ff53afe08 -C extra-filename=-821aeb82fe06467d --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern proc_macro2=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libproc_macro2-e337feb845d9f93c.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling syn v2.0.101 Running `/usr/bin/rustc --crate-name syn --edition=2021 /usr/share/cargo/registry/syn-2.0.101/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="clone-impls"' --cfg 'feature="default"' --cfg 'feature="derive"' --cfg 'feature="parsing"' --cfg 'feature="printing"' --cfg 'feature="proc-macro"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("clone-impls", "default", "derive", "extra-traits", "fold", "full", "parsing", "printing", "proc-macro", "test", "visit", "visit-mut"))' -C metadata=177c7325c8b8e527 -C extra-filename=-5a4262f5e37849ae --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern proc_macro2=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libproc_macro2-e337feb845d9f93c.rmeta --extern quote=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libquote-821aeb82fe06467d.rmeta --extern unicode_ident=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libunicode_ident-55f6e005f2dbcf0c.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling regex-automata v0.4.9 Running `/usr/bin/rustc --crate-name regex_automata --edition=2021 /usr/share/cargo/registry/regex-automata-0.4.9/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="alloc"' --cfg 'feature="dfa-onepass"' --cfg 'feature="hybrid"' --cfg 'feature="meta"' --cfg 'feature="nfa-backtrack"' --cfg 'feature="nfa-pikevm"' --cfg 'feature="nfa-thompson"' --cfg 'feature="perf-inline"' --cfg 'feature="perf-literal"' --cfg 'feature="perf-literal-multisubstring"' --cfg 'feature="perf-literal-substring"' --cfg 'feature="std"' --cfg 'feature="syntax"' --cfg 'feature="unicode"' --cfg 'feature="unicode-age"' --cfg 'feature="unicode-bool"' --cfg 'feature="unicode-case"' --cfg 'feature="unicode-gencat"' --cfg 'feature="unicode-perl"' --cfg 'feature="unicode-script"' --cfg 'feature="unicode-segment"' --cfg 'feature="unicode-word-boundary"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("alloc", "default", "dfa", "dfa-build", "dfa-onepass", "dfa-search", "hybrid", "internal-instrument", "internal-instrument-pikevm", "logging", "meta", "nfa", "nfa-backtrack", "nfa-pikevm", "nfa-thompson", "perf", "perf-inline", "perf-literal", "perf-literal-multisubstring", "perf-literal-substring", "std", "syntax", "unicode", "unicode-age", "unicode-bool", "unicode-case", "unicode-gencat", "unicode-perl", "unicode-script", "unicode-segment", "unicode-word-boundary"))' -C metadata=882678daca49a043 -C extra-filename=-c1ae447e5d745faa --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern aho_corasick=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libaho_corasick-ab869557dff442c7.rmeta --extern memchr=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libmemchr-d5472c13b3d6260a.rmeta --extern regex_syntax=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libregex_syntax-3eee5497a974c663.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling peg-macros v0.8.5 Running `/usr/bin/rustc --crate-name peg_macros --edition=2021 /usr/share/cargo/registry/peg-macros-0.8.5/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type proc-macro --emit=dep-info,link -C prefer-dynamic -C embed-bitcode=no -C debug-assertions=off --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("trace"))' -C metadata=d097650d0e8e0cd3 -C extra-filename=-02e80726d8910916 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern peg_runtime=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libpeg_runtime-fc09b67d6c715931.rlib --extern proc_macro2=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libproc_macro2-e337feb845d9f93c.rlib --extern quote=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libquote-821aeb82fe06467d.rlib --extern proc_macro --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling regex v1.11.1 Running `/usr/bin/rustc --crate-name regex --edition=2021 /usr/share/cargo/registry/regex-1.11.1/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="perf"' --cfg 'feature="perf-backtrack"' --cfg 'feature="perf-cache"' --cfg 'feature="perf-dfa"' --cfg 'feature="perf-inline"' --cfg 'feature="perf-literal"' --cfg 'feature="perf-onepass"' --cfg 'feature="std"' --cfg 'feature="unicode"' --cfg 'feature="unicode-age"' --cfg 'feature="unicode-bool"' --cfg 'feature="unicode-case"' --cfg 'feature="unicode-gencat"' --cfg 'feature="unicode-perl"' --cfg 'feature="unicode-script"' --cfg 'feature="unicode-segment"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "logging", "pattern", "perf", "perf-backtrack", "perf-cache", "perf-dfa", "perf-dfa-full", "perf-inline", "perf-literal", "perf-onepass", "std", "unicode", "unicode-age", "unicode-bool", "unicode-case", "unicode-gencat", "unicode-perl", "unicode-script", "unicode-segment", "unstable", "use_std"))' -C metadata=bb5fb1711f9bda0c -C extra-filename=-d71da3c56b783657 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern aho_corasick=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libaho_corasick-ab869557dff442c7.rmeta --extern memchr=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libmemchr-d5472c13b3d6260a.rmeta --extern regex_automata=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libregex_automata-c1ae447e5d745faa.rmeta --extern regex_syntax=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libregex_syntax-3eee5497a974c663.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling peg v0.8.5 Running `/usr/bin/rustc --crate-name peg --edition=2021 /usr/share/cargo/registry/peg-0.8.5/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "std", "trace", "unstable"))' -C metadata=569d45200d23bb4a -C extra-filename=-f6c4028cf8584f3c --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern peg_macros=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libpeg_macros-02e80726d8910916.so --extern peg_runtime=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libpeg_runtime-7f46959e6187149e.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling thiserror-impl v2.0.12 Compiling libcst_derive v1.8.2 Running `/usr/bin/rustc --crate-name thiserror_impl --edition=2021 /usr/share/cargo/registry/thiserror-impl-2.0.12/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type proc-macro --emit=dep-info,link -C prefer-dynamic -C embed-bitcode=no -C debug-assertions=off --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=11b71dfd47351a58 -C extra-filename=-50710ea7c5888a2c --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern proc_macro2=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libproc_macro2-e337feb845d9f93c.rlib --extern quote=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libquote-821aeb82fe06467d.rlib --extern syn=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libsyn-5a4262f5e37849ae.rlib --extern proc_macro --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/usr/bin/rustc --crate-name libcst_derive --edition=2018 /usr/share/cargo/registry/libcst_derive-1.8.2/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type proc-macro --emit=dep-info,link -C prefer-dynamic -C embed-bitcode=no -C debug-assertions=off --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=7962a2f4447f47ad -C extra-filename=-e0e9d48a87c94ef8 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern quote=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libquote-821aeb82fe06467d.rlib --extern syn=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libsyn-5a4262f5e37849ae.rlib --extern proc_macro --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/usr/bin/rustc --crate-name thiserror --edition=2021 /usr/share/cargo/registry/thiserror-2.0.12/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "std"))' -C metadata=bd206ed6b355f736 -C extra-filename=-929d49b8c2dc87ae --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern thiserror_impl=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libthiserror_impl-50710ea7c5888a2c.so --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn --cfg error_generic_member_access --check-cfg 'cfg(error_generic_member_access)' --check-cfg 'cfg(thiserror_nightly_testing)' --check-cfg 'cfg(thiserror_no_backtrace_type)'` Compiling libcst v1.8.2 (/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2) Running `/usr/bin/rustc --crate-name libcst_native --edition=2018 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type rlib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="default"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "trace"))' -C metadata=8e717f70c1c834e1 -C extra-filename=-d5080bd7561ff447 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern annotate_snippets=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libannotate_snippets-6a94540787ec50c7.rmeta --extern libcst_derive=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/liblibcst_derive-e0e9d48a87c94ef8.so --extern memchr=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libmemchr-d5472c13b3d6260a.rmeta --extern paste=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libpaste-15a18b40cf04ef3a.so --extern peg=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libpeg-f6c4028cf8584f3c.rmeta --extern regex=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libregex-d71da3c56b783657.rmeta --extern thiserror=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libthiserror-929d49b8c2dc87ae.rmeta -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` warning: unexpected `cfg` condition value: `py` --> src/lib.rs:20:7 | 20 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration = note: `#[warn(unexpected_cfgs)]` on by default warning: unexpected `cfg` condition value: `py` --> src/nodes/whitespace.rs:6:7 | 6 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/whitespace.rs:12:12 | 12 | #[cfg_attr(feature = "py", derive(TryIntoPy))] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/whitespace.rs:22:12 | 22 | #[cfg_attr(feature = "py", derive(TryIntoPy))] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/whitespace.rs:38:12 | 38 | #[cfg_attr(feature = "py", derive(TryIntoPy))] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/whitespace.rs:67:12 | 67 | #[cfg_attr(feature = "py", derive(TryIntoPy))] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/whitespace.rs:85:12 | 85 | #[cfg_attr(feature = "py", derive(TryIntoPy))] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/whitespace.rs:134:12 | 134 | #[cfg_attr(feature = "py", derive(TryIntoPy))] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/whitespace.rs:156:12 | 156 | #[cfg_attr(feature = "py", derive(TryIntoPy))] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:32:7 | 32 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:39:1 | 39 | #[cst_node(Inflate, Codegen)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:55:1 | 55 | #[cst_node(Inflate, Codegen)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:84:1 | 84 | #[cst_node(Inflate, Codegen)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:90:1 | 90 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:184:1 | 184 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:243:1 | 243 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:290:1 | 290 | #[cst_node(Codegen, Inflate)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:333:1 | 333 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:356:1 | 356 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:379:1 | 379 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:402:1 | 402 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:427:1 | 427 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:466:1 | 466 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:503:1 | 503 | #[cst_node(Codegen, ParenthesizedNode, Inflate)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:513:1 | 513 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:561:1 | 561 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:563:16 | 563 | #[cfg_attr(feature = "py", no_py_default)] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:695:1 | 695 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:735:1 | 735 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:773:1 | 773 | #[cst_node(Inflate)] | ^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:795:1 | 795 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:960:1 | 960 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1008:1 | 1008 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1029:16 | 1029 | #[cfg_attr(feature = "py", skip_py)] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1086:1 | 1086 | #[cst_node(Inflate, Codegen)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1092:1 | 1092 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1140:1 | 1140 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1185:1 | 1185 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1237:1 | 1237 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1293:1 | 1293 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1351:1 | 1351 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1421:1 | 1421 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1447:1 | 1447 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1492:1 | 1492 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1537:1 | 1537 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1640:1 | 1640 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1701:1 | 1701 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1844:1 | 1844 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1889:1 | 1889 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1959:1 | 1959 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2029:1 | 2029 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2089:1 | 2089 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2149:1 | 2149 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2191:1 | 2191 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2236:1 | 2236 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2359:1 | 2359 | #[cst_node(Codegen, ParenthesizedNode, Inflate)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2390:1 | 2390 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2431:1 | 2431 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2516:1 | 2516 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2592:1 | 2592 | #[cst_node(Codegen, Inflate, ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2603:1 | 2603 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2660:1 | 2660 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2718:1 | 2718 | #[cst_node(Codegen, Inflate, ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2724:1 | 2724 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2776:1 | 2776 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2819:1 | 2819 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2864:1 | 2864 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2909:1 | 2909 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2967:1 | 2967 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3044:1 | 3044 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3109:1 | 3109 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3195:1 | 3195 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3260:1 | 3260 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3324:1 | 3324 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3349:1 | 3349 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3381:1 | 3381 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3408:1 | 3408 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3438:1 | 3438 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3468:1 | 3468 | #[cst_node(Inflate, Codegen)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3475:1 | 3475 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3529:1 | 3529 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3565:1 | 3565 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:23:7 | 23 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2524:7 | 2524 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:29:1 | 29 | #[cst_node(Default)] | ^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:81:1 | 81 | #[cst_node(Inflate)] | ^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:141:1 | 141 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:174:1 | 174 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:194:1 | 194 | #[cst_node(ParenthesizedNode, Default)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:222:1 | 222 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:321:1 | 321 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:393:1 | 393 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:420:1 | 420 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:447:1 | 447 | #[cst_node(ParenthesizedNode, Codegen, Inflate)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:480:1 | 480 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:502:1 | 502 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:532:1 | 532 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:562:1 | 562 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:591:1 | 591 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:625:1 | 625 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:658:1 | 658 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:695:1 | 695 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:732:1 | 732 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:797:1 | 797 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:834:1 | 834 | #[cst_node(Codegen, Inflate)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:849:1 | 849 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:874:1 | 874 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1001:1 | 1001 | #[cst_node(ParenthesizedNode, Default)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1043:1 | 1043 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1076:1 | 1076 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1117:1 | 1117 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1142:1 | 1142 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1167:1 | 1167 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1208:1 | 1208 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1270:1 | 1270 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1302:1 | 1302 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1334:1 | 1334 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1425:1 | 1425 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1443:1 | 1443 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1481:1 | 1481 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1532:1 | 1532 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1582:1 | 1582 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1741:1 | 1741 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1785:1 | 1785 | #[cst_node(Codegen, Inflate)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1791:1 | 1791 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1833:1 | 1833 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1835:16 | 1835 | #[cfg_attr(feature = "py", no_py_default)] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1837:16 | 1837 | #[cfg_attr(feature = "py", no_py_default)] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1882:1 | 1882 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1906:1 | 1906 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1960:1 | 1960 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2030:1 | 2030 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2087:1 | 2087 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2129:1 | 2129 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2158:1 | 2158 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2208:1 | 2208 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2247:1 | 2247 | #[cst_node(Codegen, Inflate)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2264:1 | 2264 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2308:1 | 2308 | #[cst_node(ParenthesizedNode, Default)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2337:1 | 2337 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2362:1 | 2362 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2430:1 | 2430 | #[cst_node(Codegen, Inflate)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2436:1 | 2436 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2473:1 | 2473 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:15:7 | 15 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:20:1 | 20 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:55:1 | 55 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:106:1 | 106 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:143:1 | 143 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:184:1 | 184 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:206:1 | 206 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:287:1 | 287 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:359:1 | 359 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:708:1 | 708 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:1016:1 | 1016 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:1051:1 | 1051 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:1398:1 | 1398 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/module.rs:19:7 | 19 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/module.rs:26:1 | 26 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/traits.rs:119:7 | 119 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unused imports: `DeflatedAsynchronous as Asynchronous` and `DeflatedFormattedStringText as FormattedStringText` --> src/nodes/mod.rs:56:29 | 56 | DeflatedArg as Arg, DeflatedAsynchronous as Asynchronous, DeflatedAttribute as Attribute, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ... 67 | DeflatedFormattedStringText as FormattedStringText, DeflatedFrom as From, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: `#[warn(unused_imports)]` on by default warning: unused import: `DeflatedImportStar as ImportStar` --> src/nodes/mod.rs:90:9 | 90 | DeflatedImportStar as ImportStar, DeflatedSemicolon as Semicolon, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ warning: unexpected `cfg` condition value: `py` --> src/parser/errors.rs:28:7 | 28 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: field `string_start` is never read --> src/tokenizer/core/string_types.rs:74:9 | 70 | pub struct FStringNode { | ----------- field in this struct ... 74 | pub string_start: Option, | ^^^^^^^^^^^^ | = note: `FStringNode` has a derived impl for the trait `Clone`, but this is intentionally ignored during dead code analysis = note: `#[warn(dead_code)]` on by default warning: `libcst` (lib) generated 164 warnings (run `cargo fix --lib -p libcst` to apply 2 suggestions) Running `/usr/bin/rustc --crate-name parse --edition=2018 src/bin.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="default"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "trace"))' -C metadata=d20b41576d1fce17 -C extra-filename=-5939e38c76f1eff3 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern annotate_snippets=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libannotate_snippets-6a94540787ec50c7.rlib --extern libcst_native=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/liblibcst_native-d5080bd7561ff447.rlib --extern libcst_derive=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/liblibcst_derive-e0e9d48a87c94ef8.so --extern memchr=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libmemchr-d5472c13b3d6260a.rlib --extern paste=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libpaste-15a18b40cf04ef3a.so --extern peg=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libpeg-f6c4028cf8584f3c.rlib --extern regex=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libregex-d71da3c56b783657.rlib --extern thiserror=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libthiserror-929d49b8c2dc87ae.rlib -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Finished `rpm` profile [optimized + debuginfo] target(s) in 43.54s + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.mPZLN3 + umask 022 + cd /builddir/build/BUILD/rust-libcst-1.8.2-build + '[' /builddir/build/BUILD/rust-libcst-1.8.2-build/BUILDROOT '!=' / ']' + rm -rf /builddir/build/BUILD/rust-libcst-1.8.2-build/BUILDROOT ++ dirname /builddir/build/BUILD/rust-libcst-1.8.2-build/BUILDROOT + mkdir -p /builddir/build/BUILD/rust-libcst-1.8.2-build + mkdir /builddir/build/BUILD/rust-libcst-1.8.2-build/BUILDROOT + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd libcst-1.8.2 + set -euo pipefail ++ /usr/bin/cargo2rpm --path Cargo.toml is-lib + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' ++ /usr/bin/cargo2rpm --path Cargo.toml name + CRATE_NAME=libcst ++ /usr/bin/cargo2rpm --path Cargo.toml version + CRATE_VERSION=1.8.2 + REG_DIR=/builddir/build/BUILD/rust-libcst-1.8.2-build/BUILDROOT/usr/share/cargo/registry/libcst-1.8.2 + /usr/bin/mkdir -p /builddir/build/BUILD/rust-libcst-1.8.2-build/BUILDROOT/usr/share/cargo/registry/libcst-1.8.2 + /usr/bin/awk -i inplace -v INPLACE_SUFFIX=.deps '/^\[((.+\.)?((dev|build)-)?dependencies|features)/{f=1;next} /^\[/{f=0}; !f' Cargo.toml + grep -w -E -v 'Cargo.(lock|toml.orig)' + /usr/bin/env CARGO_HOME=.cargo RUSTC_BOOTSTRAP=1 'RUSTFLAGS=-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' /usr/bin/cargo package -l + xargs -d '\n' /usr/bin/cp --parents -a -t /builddir/build/BUILD/rust-libcst-1.8.2-build/BUILDROOT/usr/share/cargo/registry/libcst-1.8.2 warning: no (git) VCS found for `/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2` + /usr/bin/mv Cargo.toml.deps Cargo.toml + /usr/bin/cp -a Cargo.toml /builddir/build/BUILD/rust-libcst-1.8.2-build/BUILDROOT/usr/share/cargo/registry/libcst-1.8.2/Cargo.toml + /usr/bin/rm -f /builddir/build/BUILD/rust-libcst-1.8.2-build/BUILDROOT/usr/share/cargo/registry/libcst-1.8.2/Cargo.toml.deps + echo '{"files":{},"package":""}' ++ /usr/bin/cargo2rpm --path Cargo.toml is-bin + '[' 1 -eq 1 ']' + '[' 0 -eq 1 ']' + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-ldconfig + /usr/lib/rpm/brp-compress + /usr/lib/rpm/brp-strip /usr/bin/strip + /usr/lib/rpm/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump + /usr/lib/rpm/redhat/brp-strip-lto /usr/bin/strip + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/redhat/brp-mangle-shebangs + /usr/lib/rpm/brp-remove-la-files + env /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j64 + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/bin/add-determinism --brp -j64 /builddir/build/BUILD/rust-libcst-1.8.2-build/BUILDROOT Scanned 15 directories and 68 files, processed 0 inodes, 0 modified (0 replaced + 0 rewritten), 0 unsupported format, 0 errors Reading /builddir/build/BUILD/rust-libcst-1.8.2-build/SPECPARTS/rpm-debuginfo.specpart Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.6pJp3e + umask 022 + cd /builddir/build/BUILD/rust-libcst-1.8.2-build + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd libcst-1.8.2 + /usr/bin/env CARGO_HOME=.cargo RUSTC_BOOTSTRAP=1 'RUSTFLAGS=-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' /usr/bin/cargo test -j64 -Z avoid-dev-deps --profile rpm --no-fail-fast Fresh unicode-ident v1.0.18 Fresh proc-macro2 v1.0.95 Fresh quote v1.0.40 Compiling crossbeam-utils v0.8.21 Fresh syn v2.0.101 Fresh memchr v2.7.5 Compiling rayon-core v1.12.1 Fresh regex-syntax v0.8.5 Fresh anstyle v1.0.11 Fresh unicode-width v0.2.0 Compiling either v1.15.0 Fresh peg-runtime v0.8.5 Compiling difference v2.0.0 Fresh aho-corasick v1.1.3 Fresh thiserror-impl v2.0.12 Fresh peg-macros v0.8.5 Fresh libcst_derive v1.8.2 Fresh annotate-snippets v0.11.5 Running `/usr/bin/rustc --crate-name build_script_build --edition=2021 /usr/share/cargo/registry/crossbeam-utils-0.8.21/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no --warn=unexpected_cfgs '--allow=clippy::lint_groups_priority' '--allow=clippy::declare_interior_mutable_const' --check-cfg 'cfg(crossbeam_loom)' --check-cfg 'cfg(crossbeam_sanitize)' -C debug-assertions=off --cfg 'feature="default"' --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "nightly", "std"))' -C metadata=4e617100e38080b9 -C extra-filename=-bda1f43176ecb405 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/build/crossbeam-utils-bda1f43176ecb405 -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Fresh regex-automata v0.4.9 Fresh paste v1.0.15 Fresh peg v0.8.5 Fresh thiserror v2.0.12 Running `/usr/bin/rustc --crate-name build_script_build --edition=2021 /usr/share/cargo/registry/rayon-core-1.12.1/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=249ff912a5cecaf8 -C extra-filename=-60742602002a5330 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/build/rayon-core-60742602002a5330 -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Fresh regex v1.11.1 Running `/usr/bin/rustc --crate-name either --edition=2021 /usr/share/cargo/registry/either-1.15.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="std"' --cfg 'feature="use_std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "serde", "std", "use_std"))' -C metadata=1e6e839284bcbdcb -C extra-filename=-1ebe7cdeaaa6c83a --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` warning: unexpected `cfg` condition value: `py` --> src/lib.rs:20:7 | 20 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration = note: `#[warn(unexpected_cfgs)]` on by default warning: unexpected `cfg` condition value: `py` --> src/nodes/whitespace.rs:6:7 | 6 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/whitespace.rs:12:12 | 12 | #[cfg_attr(feature = "py", derive(TryIntoPy))] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/whitespace.rs:22:12 | 22 | #[cfg_attr(feature = "py", derive(TryIntoPy))] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/whitespace.rs:38:12 | 38 | #[cfg_attr(feature = "py", derive(TryIntoPy))] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/whitespace.rs:67:12 | 67 | #[cfg_attr(feature = "py", derive(TryIntoPy))] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/whitespace.rs:85:12 | 85 | #[cfg_attr(feature = "py", derive(TryIntoPy))] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/whitespace.rs:134:12 | 134 | #[cfg_attr(feature = "py", derive(TryIntoPy))] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/whitespace.rs:156:12 | 156 | #[cfg_attr(feature = "py", derive(TryIntoPy))] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:32:7 | 32 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:39:1 | 39 | #[cst_node(Inflate, Codegen)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:55:1 | 55 | #[cst_node(Inflate, Codegen)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:84:1 | 84 | #[cst_node(Inflate, Codegen)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:90:1 | 90 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:184:1 | 184 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:243:1 | 243 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:290:1 | 290 | #[cst_node(Codegen, Inflate)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:333:1 | 333 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:356:1 | 356 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:379:1 | 379 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:402:1 | 402 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:427:1 | 427 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:466:1 | 466 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:503:1 | 503 | #[cst_node(Codegen, ParenthesizedNode, Inflate)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:513:1 | 513 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:561:1 | 561 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:563:16 | 563 | #[cfg_attr(feature = "py", no_py_default)] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:695:1 | 695 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:735:1 | 735 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:773:1 | 773 | #[cst_node(Inflate)] | ^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:795:1 | 795 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:960:1 | 960 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1008:1 | 1008 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1029:16 | 1029 | #[cfg_attr(feature = "py", skip_py)] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1086:1 | 1086 | #[cst_node(Inflate, Codegen)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1092:1 | 1092 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1140:1 | 1140 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1185:1 | 1185 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1237:1 | 1237 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1293:1 | 1293 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1351:1 | 1351 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1421:1 | 1421 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1447:1 | 1447 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1492:1 | 1492 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1537:1 | 1537 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1640:1 | 1640 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1701:1 | 1701 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1844:1 | 1844 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1889:1 | 1889 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:1959:1 | 1959 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2029:1 | 2029 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2089:1 | 2089 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2149:1 | 2149 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2191:1 | 2191 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2236:1 | 2236 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2359:1 | 2359 | #[cst_node(Codegen, ParenthesizedNode, Inflate)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2390:1 | 2390 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2431:1 | 2431 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2516:1 | 2516 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2592:1 | 2592 | #[cst_node(Codegen, Inflate, ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2603:1 | 2603 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2660:1 | 2660 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2718:1 | 2718 | #[cst_node(Codegen, Inflate, ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2724:1 | 2724 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2776:1 | 2776 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2819:1 | 2819 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2864:1 | 2864 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2909:1 | 2909 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:2967:1 | 2967 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3044:1 | 3044 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3109:1 | 3109 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3195:1 | 3195 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3260:1 | 3260 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3324:1 | 3324 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3349:1 | 3349 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3381:1 | 3381 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3408:1 | 3408 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3438:1 | 3438 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3468:1 | 3468 | #[cst_node(Inflate, Codegen)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3475:1 | 3475 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3529:1 | 3529 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/statement.rs:3565:1 | 3565 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:23:7 | 23 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2524:7 | 2524 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:29:1 | 29 | #[cst_node(Default)] | ^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:81:1 | 81 | #[cst_node(Inflate)] | ^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:141:1 | 141 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:174:1 | 174 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:194:1 | 194 | #[cst_node(ParenthesizedNode, Default)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:222:1 | 222 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:321:1 | 321 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:393:1 | 393 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:420:1 | 420 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:447:1 | 447 | #[cst_node(ParenthesizedNode, Codegen, Inflate)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:480:1 | 480 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:502:1 | 502 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:532:1 | 532 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:562:1 | 562 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:591:1 | 591 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:625:1 | 625 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:658:1 | 658 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:695:1 | 695 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:732:1 | 732 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:797:1 | 797 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:834:1 | 834 | #[cst_node(Codegen, Inflate)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:849:1 | 849 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:874:1 | 874 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1001:1 | 1001 | #[cst_node(ParenthesizedNode, Default)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1043:1 | 1043 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1076:1 | 1076 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1117:1 | 1117 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1142:1 | 1142 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1167:1 | 1167 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1208:1 | 1208 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1270:1 | 1270 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1302:1 | 1302 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1334:1 | 1334 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1425:1 | 1425 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1443:1 | 1443 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1481:1 | 1481 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1532:1 | 1532 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1582:1 | 1582 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1741:1 | 1741 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1785:1 | 1785 | #[cst_node(Codegen, Inflate)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1791:1 | 1791 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1833:1 | 1833 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1835:16 | 1835 | #[cfg_attr(feature = "py", no_py_default)] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1837:16 | 1837 | #[cfg_attr(feature = "py", no_py_default)] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1882:1 | 1882 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1906:1 | 1906 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:1960:1 | 1960 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2030:1 | 2030 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2087:1 | 2087 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2129:1 | 2129 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2158:1 | 2158 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2208:1 | 2208 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2247:1 | 2247 | #[cst_node(Codegen, Inflate)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2264:1 | 2264 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2308:1 | 2308 | #[cst_node(ParenthesizedNode, Default)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2337:1 | 2337 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2362:1 | 2362 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2430:1 | 2430 | #[cst_node(Codegen, Inflate)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2436:1 | 2436 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/expression.rs:2473:1 | 2473 | #[cst_node(ParenthesizedNode)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:15:7 | 15 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:20:1 | 20 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:55:1 | 55 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:106:1 | 106 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:143:1 | 143 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:184:1 | 184 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:206:1 | 206 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:287:1 | 287 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:359:1 | 359 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:708:1 | 708 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:1016:1 | 1016 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:1051:1 | 1051 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/op.rs:1398:1 | 1398 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/module.rs:19:7 | 19 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unexpected `cfg` condition value: `py` --> src/nodes/module.rs:26:1 | 26 | #[cst_node] | ^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `cst_node` crate for guidance on how handle this unexpected cfg = help: the attribute macro `cst_node` may come from an old version of the `libcst_derive` crate, try updating your dependency with `cargo update -p libcst_derive` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `cst_node` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `py` --> src/nodes/traits.rs:119:7 | 119 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: unused imports: `DeflatedAsynchronous as Asynchronous` and `DeflatedFormattedStringText as FormattedStringText` --> src/nodes/mod.rs:56:29 | 56 | DeflatedArg as Arg, DeflatedAsynchronous as Asynchronous, DeflatedAttribute as Attribute, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ... 67 | DeflatedFormattedStringText as FormattedStringText, DeflatedFrom as From, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: `#[warn(unused_imports)]` on by default warning: unused import: `DeflatedImportStar as ImportStar` --> src/nodes/mod.rs:90:9 | 90 | DeflatedImportStar as ImportStar, DeflatedSemicolon as Semicolon, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ warning: unexpected `cfg` condition value: `py` --> src/parser/errors.rs:28:7 | 28 | #[cfg(feature = "py")] | ^^^^^^^^^^^^^^ | = note: expected values for `feature` are: `default` and `trace` = help: consider adding `py` as a feature in `Cargo.toml` = note: see for more information about checking conditional configuration warning: field `string_start` is never read --> src/tokenizer/core/string_types.rs:74:9 | 70 | pub struct FStringNode { | ----------- field in this struct ... 74 | pub string_start: Option, | ^^^^^^^^^^^^ | = note: `FStringNode` has a derived impl for the trait `Clone`, but this is intentionally ignored during dead code analysis = note: `#[warn(dead_code)]` on by default Running `/usr/bin/rustc --crate-name difference --edition=2015 /usr/share/cargo/registry/difference-2.0.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="default"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default"))' -C metadata=85b3ed1c9f1895e6 -C extra-filename=-3bfb3604f59c7b68 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` warning: `libcst` (lib) generated 164 warnings (run `cargo fix --lib -p libcst` to apply 2 suggestions) Compiling itertools v0.14.0 Running `/usr/bin/rustc --crate-name itertools --edition=2018 /usr/share/cargo/registry/itertools-0.14.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="use_alloc"' --cfg 'feature="use_std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "use_alloc", "use_std"))' -C metadata=5f5d8544fe699a7d -C extra-filename=-65818eb399d0e8eb --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern either=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libeither-1ebe7cdeaaa6c83a.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/build/rayon-core-60742602002a5330/build-script-build` Running `/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/build/crossbeam-utils-bda1f43176ecb405/build-script-build` Running `/usr/bin/rustc --crate-name crossbeam_utils --edition=2021 /usr/share/cargo/registry/crossbeam-utils-0.8.21/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --warn=unexpected_cfgs '--allow=clippy::lint_groups_priority' '--allow=clippy::declare_interior_mutable_const' --check-cfg 'cfg(crossbeam_loom)' --check-cfg 'cfg(crossbeam_sanitize)' --cfg 'feature="default"' --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "nightly", "std"))' -C metadata=73b0a671012840e6 -C extra-filename=-95667b6e5c3da1b4 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn --check-cfg 'cfg(crossbeam_no_atomic,crossbeam_sanitize_thread)'` Compiling crossbeam-epoch v0.9.18 Running `/usr/bin/rustc --crate-name crossbeam_epoch --edition=2021 /usr/share/cargo/registry/crossbeam-epoch-0.9.18/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --cfg 'feature="alloc"' --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("alloc", "default", "nightly", "std"))' -C metadata=bdf95a455efcb4da -C extra-filename=-cb0a0e92d766cb19 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern crossbeam_utils=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libcrossbeam_utils-95667b6e5c3da1b4.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling crossbeam-deque v0.8.6 Running `/usr/bin/rustc --crate-name crossbeam_deque --edition=2021 /usr/share/cargo/registry/crossbeam-deque-0.8.6/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --warn=unexpected_cfgs '--allow=clippy::lint_groups_priority' '--allow=clippy::declare_interior_mutable_const' --check-cfg 'cfg(crossbeam_loom)' --check-cfg 'cfg(crossbeam_sanitize)' --cfg 'feature="default"' --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "std"))' -C metadata=cb79d003568b7b9c -C extra-filename=-1492173446ff176a --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern crossbeam_epoch=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libcrossbeam_epoch-cb0a0e92d766cb19.rmeta --extern crossbeam_utils=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libcrossbeam_utils-95667b6e5c3da1b4.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/usr/bin/rustc --crate-name rayon_core --edition=2021 /usr/share/cargo/registry/rayon-core-1.12.1/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=f26254b1124054b8 -C extra-filename=-8873314ff699cd86 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern crossbeam_deque=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libcrossbeam_deque-1492173446ff176a.rmeta --extern crossbeam_utils=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libcrossbeam_utils-95667b6e5c3da1b4.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling rayon v1.10.0 Running `/usr/bin/rustc --crate-name rayon --edition=2021 /usr/share/cargo/registry/rayon-1.10.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=72cf90c7924adddd -C extra-filename=-739122b07270d3a5 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern either=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libeither-1ebe7cdeaaa6c83a.rmeta --extern rayon_core=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/librayon_core-8873314ff699cd86.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling libcst v1.8.2 (/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2) Running `/usr/bin/rustc --crate-name parse --edition=2018 src/bin.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --emit=dep-info,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --test --cfg 'feature="default"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "trace"))' -C metadata=5ea370c7c05839a4 -C extra-filename=-58c354d8854ec2a5 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern annotate_snippets=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libannotate_snippets-6a94540787ec50c7.rlib --extern difference=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libdifference-3bfb3604f59c7b68.rlib --extern itertools=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libitertools-65818eb399d0e8eb.rlib --extern libcst_native=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/liblibcst_native-d5080bd7561ff447.rlib --extern libcst_derive=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/liblibcst_derive-e0e9d48a87c94ef8.so --extern memchr=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libmemchr-d5472c13b3d6260a.rlib --extern paste=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libpaste-15a18b40cf04ef3a.so --extern peg=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libpeg-f6c4028cf8584f3c.rlib --extern rayon=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/librayon-739122b07270d3a5.rlib --extern regex=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libregex-d71da3c56b783657.rlib --extern thiserror=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libthiserror-929d49b8c2dc87ae.rlib -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/usr/bin/rustc --crate-name libcst_native --edition=2018 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --emit=dep-info,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2 --test --cfg 'feature="default"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "trace"))' -C metadata=01d615c392f7729a -C extra-filename=-76884461b4d55a56 --out-dir /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern annotate_snippets=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libannotate_snippets-6a94540787ec50c7.rlib --extern difference=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libdifference-3bfb3604f59c7b68.rlib --extern itertools=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libitertools-65818eb399d0e8eb.rlib --extern libcst_derive=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/liblibcst_derive-e0e9d48a87c94ef8.so --extern memchr=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libmemchr-d5472c13b3d6260a.rlib --extern paste=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libpaste-15a18b40cf04ef3a.so --extern peg=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libpeg-f6c4028cf8584f3c.rlib --extern rayon=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/librayon-739122b07270d3a5.rlib --extern regex=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libregex-d71da3c56b783657.rlib --extern thiserror=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libthiserror-929d49b8c2dc87ae.rlib -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` warning: `libcst` (lib test) generated 164 warnings (164 duplicates) Finished `rpm` profile [optimized + debuginfo] target(s) in 30.36s Running `/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libcst_native-76884461b4d55a56` running 50 tests test test::bol_offset_first_line ... ok test test::bol_offset_last_line ... ok test test::bol_offset_second_line ... ok test test::test_simple ... ok test test::test_funcdef_params ... ok test tokenizer::tests::test_add_dedents_for_dangling_indent_with_comment ... ok test tokenizer::tests::test_blankline ... ok test test::test_bare_minimum_funcdef ... ok test tokenizer::tests::test_add_dedents_for_dangling_indent ... ok test tokenizer::tests::test_async_await ... ok test tokenizer::tests::test_fake_newline_when_at_bol ... ok test tokenizer::tests::test_fraction ... ok test tokenizer::tests::test_add_dedents_after_fake_newline ... ok test tokenizer::tests::test_fake_newline ... ok test test::test_single_statement_with_no_newline ... ok test tokenizer::tests::test_indent_dedent ... ok test tokenizer::tests::test_integer_binary ... ok test tokenizer::tests::test_integer_decimal ... ok test tokenizer::tests::test_fstring_escapes ... ok test tokenizer::tests::test_integer_hexadecimal ... ok test tokenizer::tests::test_inconsistent_indentation_at_eof ... ok test tokenizer::tests::test_integer_leading_zeros ... ok test tokenizer::tests::test_indentifier ... ok test tokenizer::tests::test_integer_octal ... ok test tokenizer::tests::test_nested_f_string_specs ... ok test tokenizer::tests::test_nested_f_strings ... ok test tokenizer::tests::test_no_fake_newline_for_empty_input ... ok test tokenizer::tests::test_newline ... ok test tokenizer::tests::test_no_fake_newline_for_only_whitespaces ... ok test tokenizer::tests::test_string ... ok test tokenizer::tests::test_operator ... ok test tokenizer::text_position::char_width::tests::test_ascii_no_newlines ... ok test tokenizer::tests::test_string_triple_quoted ... ok test tokenizer::tests::test_string_prefix ... ok test tokenizer::tests::test_split_fstring ... ok test tokenizer::text_position::char_width::tests::test_newlines ... ok test tokenizer::text_position::char_width::tests::test_empty ... ok test tokenizer::text_position::char_width::tests::test_unicode_no_newlines ... ok test tokenizer::text_position::tests::test_ascii ... ok test tokenizer::text_position::tests::test_empty ... ok test tokenizer::text_position::tests::test_newline_cr ... ok test tokenizer::text_position::tests::test_newline_cr_lf ... ok test tokenizer::text_position::tests::test_newline_lf ... ok test tokenizer::text_position::tests::test_unicode ... ok test tokenizer::whitespace_parser::tests::config_mixed_newlines ... ok test tokenizer::whitespace_parser::tests::comment_until_eof ... ok test tokenizer::whitespace_parser::tests::no_comment ... ok test tokenizer::whitespace_parser::tests::simple_whitespace_line_continuations ... ok test tokenizer::whitespace_parser::tests::simple_whitespace_mixed ... ok test tokenizer::whitespace_parser::tests::single_comment ... ok test result: ok. 50 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s Running `/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/parse-58c354d8854ec2a5` running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s Doc-tests libcst_native Running `/usr/bin/rustdoc --edition=2018 --crate-type rlib --color auto --crate-name libcst_native --test src/lib.rs --test-run-directory /builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2 -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps --extern annotate_snippets=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libannotate_snippets-6a94540787ec50c7.rlib --extern difference=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libdifference-3bfb3604f59c7b68.rlib --extern itertools=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libitertools-65818eb399d0e8eb.rlib --extern libcst_native=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/liblibcst_native-d5080bd7561ff447.rlib --extern libcst_derive=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/liblibcst_derive-e0e9d48a87c94ef8.so --extern memchr=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libmemchr-d5472c13b3d6260a.rlib --extern paste=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libpaste-15a18b40cf04ef3a.so --extern peg=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libpeg-f6c4028cf8584f3c.rlib --extern rayon=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/librayon-739122b07270d3a5.rlib --extern regex=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libregex-d71da3c56b783657.rlib --extern thiserror=/builddir/build/BUILD/rust-libcst-1.8.2-build/libcst-1.8.2/target/rpm/deps/libthiserror-929d49b8c2dc87ae.rlib -C embed-bitcode=no --cfg 'feature="default"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "trace"))' --error-format human` running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s + RPM_EC=0 ++ jobs -p + exit 0 Processing files: rust-libcst-devel-1.8.2-1.fc42.noarch warning: File listed twice: /usr/share/cargo/registry/libcst-1.8.2/LICENSE warning: File listed twice: /usr/share/cargo/registry/libcst-1.8.2/README.md warning: File listed twice: /usr/share/cargo/registry/libcst-1.8.2/src/tokenizer/core/LICENSE Provides: crate(libcst) = 1.8.2 rust-libcst-devel = 1.8.2-1.fc42 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: (crate(annotate-snippets/default) >= 0.11.5 with crate(annotate-snippets/default) < 0.12.0~) (crate(libcst_derive/default) >= 1.8.2 with crate(libcst_derive/default) < 2.0.0~) (crate(memchr/default) >= 2.7.4 with crate(memchr/default) < 3.0.0~) (crate(paste/default) >= 1.0.15 with crate(paste/default) < 2.0.0~) (crate(peg/default) >= 0.8.5 with crate(peg/default) < 0.9.0~) (crate(regex/default) >= 1.11.1 with crate(regex/default) < 2.0.0~) (crate(thiserror/default) >= 2.0.12 with crate(thiserror/default) < 3.0.0~) cargo rust >= 1.70 Processing files: rust-libcst+default-devel-1.8.2-1.fc42.noarch Provides: crate(libcst/default) = 1.8.2 rust-libcst+default-devel = 1.8.2-1.fc42 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: cargo crate(libcst) = 1.8.2 Processing files: rust-libcst+trace-devel-1.8.2-1.fc42.noarch Provides: crate(libcst/trace) = 1.8.2 rust-libcst+trace-devel = 1.8.2-1.fc42 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: (crate(peg/trace) >= 0.8.5 with crate(peg/trace) < 0.9.0~) cargo crate(libcst) = 1.8.2 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILD/rust-libcst-1.8.2-build/BUILDROOT Wrote: /builddir/build/SRPMS/rust-libcst-1.8.2-1.fc42.src.rpm Wrote: /builddir/build/RPMS/rust-libcst+default-devel-1.8.2-1.fc42.noarch.rpm Wrote: /builddir/build/RPMS/rust-libcst+trace-devel-1.8.2-1.fc42.noarch.rpm Wrote: /builddir/build/RPMS/rust-libcst-devel-1.8.2-1.fc42.noarch.rpm RPM build warnings: File listed twice: /usr/share/cargo/registry/libcst-1.8.2/LICENSE File listed twice: /usr/share/cargo/registry/libcst-1.8.2/README.md File listed twice: /usr/share/cargo/registry/libcst-1.8.2/src/tokenizer/core/LICENSE Child return code was: 0