Mock Version: 6.5 Mock Version: 6.5 Mock Version: 6.5 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target riscv64 --nodeps /builddir/build/SPECS/rust-libcst.spec'], chrootPath='/var/lib/mock/f45-build-42967-797/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=864000uid=995gid=135user='mockbuild'unshare_net=TrueprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.ljdamoxh:/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.ljdamoxh:/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', '9d4aaf6d069549e1affef3885e179571', '-D', '/var/lib/mock/f45-build-42967-797/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.ljdamoxh:/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 riscv64 --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: riscv64 Building for target riscv64 setting SOURCE_DATE_EPOCH=1784246400 Wrote: /builddir/build/SRPMS/rust-libcst-1.8.6-3.fc45.src.rpm Child return code was: 0 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noclean --target riscv64 --nodeps /builddir/build/SPECS/rust-libcst.spec'], chrootPath='/var/lib/mock/f45-build-42967-797/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=864000uid=995gid=135user='mockbuild'unshare_net=TrueraiseExc=FalseprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.ljdamoxh:/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.ljdamoxh:/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', '40a811b1b8564e66b1374142d2f0680e', '-D', '/var/lib/mock/f45-build-42967-797/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.ljdamoxh:/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 riscv64 --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: riscv64 Building for target riscv64 setting SOURCE_DATE_EPOCH=1784246400 Executing(mkbuilddir): /bin/sh -e /var/tmp/rpm-tmp.x8Zuh7 Creating(rpmbuild.env): /builddir/build/BUILD/rust-libcst-1.8.6-build/rpmbuild.env RPM_SOURCE_DIR="/builddir/build/SOURCES" RPM_BUILD_DIR="/builddir/build/BUILD/rust-libcst-1.8.6-build" RPM_OPT_FLAGS="-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -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 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer" RPM_LD_FLAGS="-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes " RPM_ARCH="riscv64" RPM_OS="linux" RPM_BUILD_NCPUS="8" RPM_SPECPARTS_DIR="/builddir/build/BUILD/rust-libcst-1.8.6-build/SPECPARTS" export RPM_SOURCE_DIR RPM_BUILD_DIR RPM_OPT_FLAGS RPM_ARCH RPM_OS RPM_BUILD_NCPUS RPM_SPECPARTS_DIR RPM_LD_FLAGS RPM_DOC_DIR="/usr/share/doc" export RPM_DOC_DIR RPM_PACKAGE_NAME="rust-libcst" RPM_PACKAGE_VERSION="1.8.6" RPM_PACKAGE_RELEASE="3.fc45" export RPM_PACKAGE_NAME RPM_PACKAGE_VERSION RPM_PACKAGE_RELEASE LANG=C.UTF-8 export LANG unset CDPATH DISPLAY ||: unset DEBUGINFOD_URLS ||: unset RPM_CONFIG_DIR ||: RPM_BUILD_ROOT="/builddir/build/BUILD/rust-libcst-1.8.6-build/BUILDROOT" export RPM_BUILD_ROOT PKG_CONFIG_PATH="${PKG_CONFIG_PATH}:/usr/lib64/pkgconfig:/usr/share/pkgconfig" export PKG_CONFIG_PATH CONFIG_SITE=${CONFIG_SITE:-NONE} export CONFIG_SITE Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.4EUgU6 + umask 022 + cd /builddir/build/BUILD/rust-libcst-1.8.6-build + cd /builddir/build/BUILD/rust-libcst-1.8.6-build + rm -rf libcst-1.8.6 + /usr/bin/rpmuncompress -x /builddir/build/SOURCES/libcst-1.8.6.crate + STATUS=0 + '[' 0 -ne 0 ']' + cd libcst-1.8.6 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/bin/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 + dos2unix --keepdate tests/fixtures/type_parameters.py dos2unix: converting file tests/fixtures/type_parameters.py to Unix format... + RPM_EC=0 ++ jobs -p + exit 0 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.AP25hd + umask 022 + cd /builddir/build/BUILD/rust-libcst-1.8.6-build + cd libcst-1.8.6 + /usr/bin/cargo2rpm --path Cargo.toml buildrequires --with-check + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/rust-libcst-1.8.6-3.fc45.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 riscv64 --nodeps /builddir/build/SPECS/rust-libcst.spec'], chrootPath='/var/lib/mock/f45-build-42967-797/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=864000uid=995gid=135user='mockbuild'unshare_net=TrueraiseExc=FalseprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.ljdamoxh:/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.ljdamoxh:/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', '0217f45d7ae346f3a157878d8833fd5d', '-D', '/var/lib/mock/f45-build-42967-797/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.ljdamoxh:/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 riscv64 --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: riscv64 Building for target riscv64 setting SOURCE_DATE_EPOCH=1784246400 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.gxckmY + umask 022 + cd /builddir/build/BUILD/rust-libcst-1.8.6-build + cd libcst-1.8.6 + /usr/bin/cargo2rpm --path Cargo.toml buildrequires --with-check + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/rust-libcst-1.8.6-3.fc45.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 riscv64 --nodeps /builddir/build/SPECS/rust-libcst.spec'], chrootPath='/var/lib/mock/f45-build-42967-797/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=864000uid=995gid=135user='mockbuild'unshare_net=TrueprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.ljdamoxh:/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.ljdamoxh:/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', '183b0a83d04d488097301a0c8822eef1', '-D', '/var/lib/mock/f45-build-42967-797/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.ljdamoxh:/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 riscv64 --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: riscv64 Building for target riscv64 setting SOURCE_DATE_EPOCH=1784246400 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.HFyJ7f + umask 022 + cd /builddir/build/BUILD/rust-libcst-1.8.6-build + cd libcst-1.8.6 + /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.wCwqgp + umask 022 + cd /builddir/build/BUILD/rust-libcst-1.8.6-build + CFLAGS='-O2 -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 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -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 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -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 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -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 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd libcst-1.8.6 + /usr/bin/env CARGO_HOME=.cargo RUSTC_BOOTSTRAP=1 'RUSTFLAGS=-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' /usr/bin/cargo build -j8 -Z avoid-dev-deps --profile rpm Compiling proc-macro2 v1.0.107 Compiling quote v1.0.47 Compiling unicode-ident v1.0.24 Compiling memchr v2.8.3 Compiling regex-syntax v0.8.11 Compiling paste v1.0.15 Compiling thiserror v2.0.20 Compiling peg-runtime v0.8.5 Running `/usr/bin/rustc --crate-name build_script_build --edition=2021 /usr/share/cargo/registry/quote-1.0.47/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", "proc-macro"))' -C metadata=3fad9f6bd74d31a8 -C extra-filename=-ce4bd2486ce4dd3b --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/build/quote-ce4bd2486ce4dd3b -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -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/proc-macro2-1.0.107/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=075dd25a5e64132b -C extra-filename=-c125fbcac5d5ebb7 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/build/proc-macro2-c125fbcac5d5ebb7 -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/usr/bin/rustc --crate-name unicode_ident --edition=2021 /usr/share/cargo/registry/unicode-ident-1.0.24/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=4e09a2d83e4b8f87 -C extra-filename=-b90bb588e120788f --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -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.8.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="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=70df40e40c07576b -C extra-filename=-eb7735759febd272 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -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.20/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=84af547b5421c690 -C extra-filename=-bc1115f7ac848cf2 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/build/thiserror-bc1115f7ac848cf2 -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -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=152aecda79066814 -C extra-filename=-d50ab6827a49dae0 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/build/paste-d50ab6827a49dae0 -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -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.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 --allow=unexpected_cfgs --check-cfg 'cfg(docsrs_regex)' --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=cac23ab55ecbb466 -C extra-filename=-807a227343fe1ca1 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -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=9c15ace11004ec99 -C extra-filename=-165d78eb07e080dc --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling unicode-width v0.2.2 Running `/usr/bin/rustc --crate-name unicode_width --edition=2021 /usr/share/cargo/registry/unicode-width-0.2.2/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", "core", "default", "no_std", "rustc-dep-of-std", "std"))' -C metadata=79c1082895f60e14 -C extra-filename=-d796c061ffe15885 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -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=f96dec8819ca7729 -C extra-filename=-e94f846f0d4541d7 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/build/paste-d50ab6827a49dae0/build-script-build` Running `/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/build/quote-ce4bd2486ce4dd3b/build-script-build` Compiling aho-corasick v1.1.5 Running `/usr/bin/rustc --crate-name aho_corasick --edition=2021 /usr/share/cargo/registry/aho-corasick-1.1.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="perf-literal"' --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "logging", "perf-literal", "std"))' -C metadata=813fabf2737e1418 -C extra-filename=-021e8b281f17db64 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern memchr=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libmemchr-eb7735759febd272.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling anstyle v1.0.14 Running `/usr/bin/rustc --crate-name anstyle --edition=2021 /usr/share/cargo/registry/anstyle-1.0.14/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_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_enums' '--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=16a3c2fc91e06945 -C extra-filename=-f079b55464365c09 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/build/proc-macro2-c125fbcac5d5ebb7/build-script-build` Running `/usr/bin/rustc --crate-name proc_macro2 --edition=2021 /usr/share/cargo/registry/proc-macro2-1.0.107/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=5bb2cfce89d7d922 -C extra-filename=-27e3291d30a3dfa3 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern unicode_ident=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libunicode_ident-b90bb588e120788f.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn --cfg wrap_proc_macro --cfg proc_macro_span --cfg proc_macro_span_location --cfg proc_macro_span_file --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(proc_macro_span_file)' --check-cfg 'cfg(proc_macro_span_location)' --check-cfg 'cfg(procmacro2_backtrace)' --check-cfg 'cfg(procmacro2_build_probe)' --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 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=9ebb37f445e913e7 -C extra-filename=-c83ae72c36bb1eec --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern anstyle=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libanstyle-f079b55464365c09.rmeta --extern unicode_width=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libunicode_width-d796c061ffe15885.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` 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=374e38fe88b897af -C extra-filename=-ef67be6a2fe550e0 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern proc_macro --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -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.6-build/libcst-1.8.6/target/rpm/build/thiserror-bc1115f7ac848cf2/build-script-build` Running `/usr/bin/rustc --crate-name quote --edition=2021 /usr/share/cargo/registry/quote-1.0.47/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=5858b72bfb0bed64 -C extra-filename=-80917f750cdbe7cc --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern proc_macro2=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libproc_macro2-27e3291d30a3dfa3.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn --check-cfg 'cfg(no_diagnostic_namespace)'` Compiling syn v3.0.4 Compiling syn v2.0.119 Running `/usr/bin/rustc --crate-name syn --edition=2021 /usr/share/cargo/registry/syn-3.0.4/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=0f9ad80056bc7917 -C extra-filename=-4cf3d45d7392e1fa --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern proc_macro2=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libproc_macro2-27e3291d30a3dfa3.rmeta --extern quote=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libquote-80917f750cdbe7cc.rmeta --extern unicode_ident=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libunicode_ident-b90bb588e120788f.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/usr/bin/rustc --crate-name syn --edition=2021 /usr/share/cargo/registry/syn-2.0.119/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=1f75ec607a54634d -C extra-filename=-660c2e0d0e05897d --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern proc_macro2=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libproc_macro2-27e3291d30a3dfa3.rmeta --extern quote=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libquote-80917f750cdbe7cc.rmeta --extern unicode_ident=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libunicode_ident-b90bb588e120788f.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling regex-automata v0.4.18 Running `/usr/bin/rustc --crate-name regex_automata --edition=2021 /usr/share/cargo/registry/regex-automata-0.4.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 --allow=unexpected_cfgs --check-cfg 'cfg(docsrs_regex)' --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=befeac0f7c13ffa1 -C extra-filename=-b45360bd2e3335de --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern aho_corasick=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libaho_corasick-021e8b281f17db64.rmeta --extern memchr=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libmemchr-eb7735759febd272.rmeta --extern regex_syntax=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libregex_syntax-807a227343fe1ca1.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -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=434bf8b8133244b7 -C extra-filename=-592af04556359d0d --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern peg_runtime=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libpeg_runtime-165d78eb07e080dc.rlib --extern proc_macro2=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libproc_macro2-27e3291d30a3dfa3.rlib --extern quote=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libquote-80917f750cdbe7cc.rlib --extern proc_macro --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling regex v1.13.1 Running `/usr/bin/rustc --crate-name regex --edition=2021 /usr/share/cargo/registry/regex-1.13.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 --allow=unexpected_cfgs --check-cfg 'cfg(docsrs_regex)' --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=82fc668440254852 -C extra-filename=-8e4c91a207e2f9f7 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern aho_corasick=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libaho_corasick-021e8b281f17db64.rmeta --extern memchr=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libmemchr-eb7735759febd272.rmeta --extern regex_automata=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libregex_automata-b45360bd2e3335de.rmeta --extern regex_syntax=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libregex_syntax-807a227343fe1ca1.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -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=18c31630da124bbe -C extra-filename=-8060f164137eb297 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern peg_macros=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libpeg_macros-592af04556359d0d.so --extern peg_runtime=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libpeg_runtime-e94f846f0d4541d7.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling thiserror-impl v2.0.20 Running `/usr/bin/rustc --crate-name thiserror_impl --edition=2021 /usr/share/cargo/registry/thiserror-impl-2.0.20/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=d704269fae569ce8 -C extra-filename=-d412268dcd7345f0 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern proc_macro2=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libproc_macro2-27e3291d30a3dfa3.rlib --extern quote=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libquote-80917f750cdbe7cc.rlib --extern syn=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libsyn-4cf3d45d7392e1fa.rlib --extern proc_macro --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling libcst_derive v1.8.6 Running `/usr/bin/rustc --crate-name libcst_derive --edition=2018 /usr/share/cargo/registry/libcst_derive-1.8.6/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=f733609f2f797314 -C extra-filename=-7b62f9686e2d2fcc --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern quote=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libquote-80917f750cdbe7cc.rlib --extern syn=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libsyn-660c2e0d0e05897d.rlib --extern proc_macro --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -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.20/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=77dc12e86860da8d -C extra-filename=-7a8e026ecce6c013 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern thiserror_impl=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libthiserror_impl-d412268dcd7345f0.so --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -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.6 (/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6) 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=a18efc53c4d1655b -C extra-filename=-5d31d91ffdbcd127 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern annotate_snippets=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libannotate_snippets-c83ae72c36bb1eec.rmeta --extern libcst_derive=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/liblibcst_derive-7b62f9686e2d2fcc.so --extern memchr=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libmemchr-eb7735759febd272.rmeta --extern paste=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libpaste-ef67be6a2fe550e0.so --extern peg=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libpeg-8060f164137eb297.rmeta --extern regex=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libregex-8e4c91a207e2f9f7.rmeta --extern thiserror=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libthiserror-7a8e026ecce6c013.rmeta -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` 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 = note: `#[warn(unexpected_cfgs)]` on by default 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/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 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: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:481:1 | 481 | #[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:503:1 | 503 | #[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:533:1 | 533 | #[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:563:1 | 563 | #[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:592:1 | 592 | #[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:626:1 | 626 | #[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:659:1 | 659 | #[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:696:1 | 696 | #[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:733:1 | 733 | #[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:798:1 | 798 | #[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:835:1 | 835 | #[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:850:1 | 850 | #[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:875:1 | 875 | #[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:1002:1 | 1002 | #[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:1044:1 | 1044 | #[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:1077:1 | 1077 | #[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:1118:1 | 1118 | #[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:1143:1 | 1143 | #[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:1168:1 | 1168 | #[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:1209:1 | 1209 | #[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:1271:1 | 1271 | #[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:1303:1 | 1303 | #[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:1335:1 | 1335 | #[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:1426:1 | 1426 | #[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:1444:1 | 1444 | #[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:1482:1 | 1482 | #[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:1533:1 | 1533 | #[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:1583:1 | 1583 | #[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:1742:1 | 1742 | #[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:1786:1 | 1786 | #[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:1792:1 | 1792 | #[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:1834:1 | 1834 | #[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:1836:16 | 1836 | #[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:1838:16 | 1838 | #[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:1883:1 | 1883 | #[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:1907:1 | 1907 | #[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:1961:1 | 1961 | #[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:2031:1 | 2031 | #[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:2088:1 | 2088 | #[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:2130:1 | 2130 | #[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:2159:1 | 2159 | #[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:2209:1 | 2209 | #[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:2248:1 | 2248 | #[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:2267:1 | 2267 | #[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:2311:1 | 2311 | #[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:2340:1 | 2340 | #[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:2365:1 | 2365 | #[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:2434:1 | 2434 | #[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:2471:1 | 2471 | #[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:2476:1 | 2476 | #[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:2501:1 | 2501 | #[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:2569:1 | 2569 | #[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:2575:1 | 2575 | #[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:2612:1 | 2612 | #[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: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: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/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/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/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:2663:7 | 2663 | #[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: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/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/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`, `DeflatedFormattedStringText as FormattedStringText`, and `DeflatedTemplatedStringText as TemplatedStringText` --> src/nodes/mod.rs:57:29 | 57 | DeflatedArg as Arg, DeflatedAsynchronous as Asynchronous, DeflatedAttribute as Attribute, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ... 68 | DeflatedFormattedStringText as FormattedStringText, DeflatedFrom as From, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ... 85 | DeflatedTemplatedStringText as TemplatedStringText, DeflatedTuple as Tuple, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default warning: unused import: `DeflatedImportStar as ImportStar` --> src/nodes/mod.rs:94:9 | 94 | 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:80:9 | 76 | pub struct FTStringNode { | ------------ field in this struct ... 80 | pub string_start: Option, | ^^^^^^^^^^^^ | = note: `FTStringNode` has a derived impl for the trait `Clone`, but this is intentionally ignored during dead code analysis = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default warning: methods `lpar` and `rpar` are never used --> src/nodes/traits.rs:57:8 | 56 | pub trait ParenthesizedDeflatedNode<'r, 'a> { | ------------------------- methods in this trait 57 | fn lpar(&self) -> &Vec>; | ^^^^ 58 | fn rpar(&self) -> &Vec>; | ^^^^ warning: hiding a lifetime that's elided elsewhere is confusing --> src/lib.rs:23:23 | 23 | pub fn tokenize(text: &str) -> Result> { | ^^^^ ^^^^^^^^^^^^^^^^^^ | | | | | | | the same lifetime is hidden here | | the same lifetime is hidden here | the lifetime is elided here | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default help: use `'_` for type paths | 23 | pub fn tokenize(text: &str) -> Result<'_, Vec>> { | +++ ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/lib.rs:61:30 | 61 | pub fn parse_statement(text: &str) -> Result { | ^^^^ ^^^^^^^^^^^^^^^^^ | | | | | | | the same lifetime is hidden here | | the same lifetime is hidden here | the lifetime is elided here | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing help: use `'_` for type paths | 61 | pub fn parse_statement(text: &str) -> Result<'_, Statement<'_>> { | +++ ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/lib.rs:70:31 | 70 | pub fn parse_expression(text: &str) -> Result { | ^^^^ ^^^^^^^^^^^^^^^^^^ | | | | | | | the same lifetime is hidden here | | the same lifetime is hidden here | the lifetime is elided here | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing help: use `'_` for type paths | 70 | pub fn parse_expression(text: &str) -> Result<'_, Expression<'_>> { | +++ ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/parser/numbers.rs:43:33 | 43 | pub(crate) fn parse_number(raw: &str) -> Expression { | ^^^^ ^^^^^^^^^^ | | | | | the same lifetime is hidden here | | the same lifetime is hidden here | the lifetime is elided here | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing help: use `'_` for type paths | 43 | pub(crate) fn parse_number(raw: &str) -> Expression<'_> { | ++++ warning: `libcst` (lib) generated 173 warnings (run `cargo fix --lib -p libcst` to apply 6 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=2e21a3a77368d6b2 -C extra-filename=-6f3d8360115ee161 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern annotate_snippets=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libannotate_snippets-c83ae72c36bb1eec.rlib --extern libcst_native=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/liblibcst_native-5d31d91ffdbcd127.rlib --extern libcst_derive=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/liblibcst_derive-7b62f9686e2d2fcc.so --extern memchr=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libmemchr-eb7735759febd272.rlib --extern paste=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libpaste-ef67be6a2fe550e0.so --extern peg=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libpeg-8060f164137eb297.rlib --extern regex=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libregex-8e4c91a207e2f9f7.rlib --extern thiserror=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libthiserror-7a8e026ecce6c013.rlib -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Finished `rpm` profile [optimized + debuginfo] target(s) in 4m 15s + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.R439FV + umask 022 + cd /builddir/build/BUILD/rust-libcst-1.8.6-build + '[' /builddir/build/BUILD/rust-libcst-1.8.6-build/BUILDROOT '!=' / ']' + rm -rf /builddir/build/BUILD/rust-libcst-1.8.6-build/BUILDROOT ++ dirname /builddir/build/BUILD/rust-libcst-1.8.6-build/BUILDROOT + mkdir -p /builddir/build/BUILD/rust-libcst-1.8.6-build + mkdir /builddir/build/BUILD/rust-libcst-1.8.6-build/BUILDROOT + CFLAGS='-O2 -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 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -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 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -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 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -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 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd libcst-1.8.6 + 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.6 + REG_DIR=/builddir/build/BUILD/rust-libcst-1.8.6-build/BUILDROOT/usr/share/cargo/registry/libcst-1.8.6 + /usr/bin/mkdir -p /builddir/build/BUILD/rust-libcst-1.8.6-build/BUILDROOT/usr/share/cargo/registry/libcst-1.8.6 + /usr/bin/awk -i inplace -v INPLACE_SUFFIX=.deps '/^\[((.+\.)?((dev|build)-)?dependencies|features)/{f=1;next} /^\[/{f=0}; !f' Cargo.toml + /usr/bin/env CARGO_HOME=.cargo RUSTC_BOOTSTRAP=1 'RUSTFLAGS=-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' /usr/bin/cargo package -l + grep -w -E -v 'Cargo.(lock|toml.orig)' + xargs -d '\n' /usr/bin/cp --parents -a -t /builddir/build/BUILD/rust-libcst-1.8.6-build/BUILDROOT/usr/share/cargo/registry/libcst-1.8.6 warning: no (git) VCS found for `/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6` + /usr/bin/mv Cargo.toml.deps Cargo.toml + /usr/bin/cp -a Cargo.toml /builddir/build/BUILD/rust-libcst-1.8.6-build/BUILDROOT/usr/share/cargo/registry/libcst-1.8.6/Cargo.toml + /usr/bin/rm -f /builddir/build/BUILD/rust-libcst-1.8.6-build/BUILDROOT/usr/share/cargo/registry/libcst-1.8.6/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 + COMPRESS='gzip -9 -n' + COMPRESS_EXT=.gz + /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/check-rpaths + /usr/lib/rpm/redhat/brp-mangle-shebangs + /usr/lib/rpm/brp-remove-la-files + /usr/lib/rpm/redhat/brp-python-rpm-in-distinfo + env /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j8 + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/bin/add-det --brp -j8 /builddir/build/BUILD/rust-libcst-1.8.6-build/BUILDROOT Scanned 15 directories and 68 files, processed 0 inodes, 0 modified (0 replaced + 0 rewritten), 0 unsupported format, 0 errors + /usr/bin/linkdupes --brp /builddir/build/BUILD/rust-libcst-1.8.6-build/BUILDROOT/usr Scanned 14 directories and 68 files, considered 68 files, read 0 files, linked 0 files, 0 errors sum of sizes of linked files: 0 bytes Reading /builddir/build/BUILD/rust-libcst-1.8.6-build/SPECPARTS/rpm-debuginfo.specpart Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.vJliNo + umask 022 + cd /builddir/build/BUILD/rust-libcst-1.8.6-build + CFLAGS='-O2 -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 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -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 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -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 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -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 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd libcst-1.8.6 + /usr/bin/env CARGO_HOME=.cargo RUSTC_BOOTSTRAP=1 'RUSTFLAGS=-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' /usr/bin/cargo test -j8 -Z avoid-dev-deps --profile rpm --no-fail-fast Fresh unicode-ident v1.0.24 Compiling crossbeam-utils v0.8.23 Compiling crossbeam-epoch v0.9.21 Fresh memchr v2.8.3 Compiling crossbeam-deque v0.8.8 Fresh regex-syntax v0.8.11 Running `/usr/bin/rustc --crate-name build_script_build --edition=2021 /usr/share/cargo/registry/crossbeam-utils-0.8.23/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=a237a16a1b4a56da -C extra-filename=-8d6f6b6ad271d884 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/build/crossbeam-utils-8d6f6b6ad271d884 -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -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/crossbeam-epoch-0.9.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="alloc"' --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("alloc", "default", "nightly", "std"))' -C metadata=e081ec791173b394 -C extra-filename=-8cbec46a287d6ef4 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/build/crossbeam-epoch-8cbec46a287d6ef4 -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Fresh proc-macro2 v1.0.107 Fresh aho-corasick v1.1.5 Running `/usr/bin/rustc --crate-name build_script_build --edition=2021 /usr/share/cargo/registry/crossbeam-deque-0.8.8/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", "std"))' -C metadata=8c4c70634f43bdd6 -C extra-filename=-63f233d7d4117ff4 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/build/crossbeam-deque-63f233d7d4117ff4 -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Fresh quote v1.0.47 Compiling rayon-core v1.13.0 Fresh regex-automata v0.4.18 Running `/usr/bin/rustc --crate-name build_script_build --edition=2021 /usr/share/cargo/registry/rayon-core-1.13.0/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=d6c916d07f3bc3c4 -C extra-filename=-1334c4a3a93f9373 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/build/rayon-core-1334c4a3a93f9373 -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Fresh syn v3.0.4 Fresh syn v2.0.119 Fresh peg-macros v0.8.5 Fresh thiserror-impl v2.0.20 Fresh unicode-width v0.2.2 Compiling either v1.17.0 Fresh anstyle v1.0.14 Fresh peg-runtime v0.8.5 Fresh annotate-snippets v0.11.5 Fresh thiserror v2.0.20 Running `/usr/bin/rustc --crate-name either --edition=2021 /usr/share/cargo/registry/either-1.17.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=6c4c50da832d00c9 -C extra-filename=-0e3c851e881c60aa --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Fresh peg v0.8.5 Fresh libcst_derive v1.8.6 Fresh paste v1.0.15 Fresh regex v1.13.1 Compiling difference v2.0.0 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 = note: `#[warn(unexpected_cfgs)]` on by default 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/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 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: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:481:1 | 481 | #[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:503:1 | 503 | #[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:533:1 | 533 | #[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:563:1 | 563 | #[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:592:1 | 592 | #[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:626:1 | 626 | #[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:659:1 | 659 | #[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:696:1 | 696 | #[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:733:1 | 733 | #[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:798:1 | 798 | #[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:835:1 | 835 | #[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:850:1 | 850 | #[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:875:1 | 875 | #[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:1002:1 | 1002 | #[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:1044:1 | 1044 | #[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:1077:1 | 1077 | #[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:1118:1 | 1118 | #[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:1143:1 | 1143 | #[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:1168:1 | 1168 | #[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:1209:1 | 1209 | #[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:1271:1 | 1271 | #[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:1303:1 | 1303 | #[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:1335:1 | 1335 | #[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:1426:1 | 1426 | #[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:1444:1 | 1444 | #[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:1482:1 | 1482 | #[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:1533:1 | 1533 | #[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:1583:1 | 1583 | #[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:1742:1 | 1742 | #[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:1786:1 | 1786 | #[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:1792:1 | 1792 | #[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:1834:1 | 1834 | #[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:1836:16 | 1836 | #[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:1838:16 | 1838 | #[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:1883:1 | 1883 | #[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:1907:1 | 1907 | #[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:1961:1 | 1961 | #[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:2031:1 | 2031 | #[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:2088:1 | 2088 | #[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:2130:1 | 2130 | #[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:2159:1 | 2159 | #[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:2209:1 | 2209 | #[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:2248:1 | 2248 | #[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:2267:1 | 2267 | #[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:2311:1 | 2311 | #[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:2340:1 | 2340 | #[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:2365:1 | 2365 | #[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:2434:1 | 2434 | #[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:2471:1 | 2471 | #[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:2476:1 | 2476 | #[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:2501:1 | 2501 | #[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:2569:1 | 2569 | #[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:2575:1 | 2575 | #[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:2612:1 | 2612 | #[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: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: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/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/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/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:2663:7 | 2663 | #[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: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/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/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`, `DeflatedFormattedStringText as FormattedStringText`, and `DeflatedTemplatedStringText as TemplatedStringText` --> src/nodes/mod.rs:57:29 | 57 | DeflatedArg as Arg, DeflatedAsynchronous as Asynchronous, DeflatedAttribute as Attribute, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ... 68 | DeflatedFormattedStringText as FormattedStringText, DeflatedFrom as From, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ... 85 | DeflatedTemplatedStringText as TemplatedStringText, DeflatedTuple as Tuple, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default warning: unused import: `DeflatedImportStar as ImportStar` --> src/nodes/mod.rs:94:9 | 94 | 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:80:9 | 76 | pub struct FTStringNode { | ------------ field in this struct ... 80 | pub string_start: Option, | ^^^^^^^^^^^^ | = note: `FTStringNode` has a derived impl for the trait `Clone`, but this is intentionally ignored during dead code analysis = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default warning: methods `lpar` and `rpar` are never used --> src/nodes/traits.rs:57:8 | 56 | pub trait ParenthesizedDeflatedNode<'r, 'a> { | ------------------------- methods in this trait 57 | fn lpar(&self) -> &Vec>; | ^^^^ 58 | fn rpar(&self) -> &Vec>; | ^^^^ warning: hiding a lifetime that's elided elsewhere is confusing --> src/lib.rs:23:23 | 23 | pub fn tokenize(text: &str) -> Result> { | ^^^^ ^^^^^^^^^^^^^^^^^^ | | | | | | | the same lifetime is hidden here | | the same lifetime is hidden here | the lifetime is elided here | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default help: use `'_` for type paths | 23 | pub fn tokenize(text: &str) -> Result<'_, Vec>> { | +++ ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/lib.rs:61:30 | 61 | pub fn parse_statement(text: &str) -> Result { | ^^^^ ^^^^^^^^^^^^^^^^^ | | | | | | | the same lifetime is hidden here | | the same lifetime is hidden here | the lifetime is elided here | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing help: use `'_` for type paths | 61 | pub fn parse_statement(text: &str) -> Result<'_, Statement<'_>> { | +++ ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/lib.rs:70:31 | 70 | pub fn parse_expression(text: &str) -> Result { | ^^^^ ^^^^^^^^^^^^^^^^^^ | | | | | | | the same lifetime is hidden here | | the same lifetime is hidden here | the lifetime is elided here | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing help: use `'_` for type paths | 70 | pub fn parse_expression(text: &str) -> Result<'_, Expression<'_>> { | +++ ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/parser/numbers.rs:43:33 | 43 | pub(crate) fn parse_number(raw: &str) -> Expression { | ^^^^ ^^^^^^^^^^ | | | | | the same lifetime is hidden here | | the same lifetime is hidden here | the lifetime is elided here | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing help: use `'_` for type paths | 43 | pub(crate) fn parse_number(raw: &str) -> Expression<'_> { | ++++ 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=2d8e968a6536df57 -C extra-filename=-9c4b33aa3e86c4ee --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` warning: `libcst` (lib) generated 173 warnings (run `cargo fix --lib -p libcst` to apply 6 suggestions) Running `/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/build/rayon-core-1334c4a3a93f9373/build-script-build` Running `/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/build/crossbeam-epoch-8cbec46a287d6ef4/build-script-build` Running `/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/build/crossbeam-deque-63f233d7d4117ff4/build-script-build` 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=ea576734445d464f -C extra-filename=-7d19ca41e12c3426 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern either=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libeither-0e3c851e881c60aa.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Running `/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/build/crossbeam-utils-8d6f6b6ad271d884/build-script-build` Running `/usr/bin/rustc --crate-name crossbeam_utils --edition=2021 /usr/share/cargo/registry/crossbeam-utils-0.8.23/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=f7c5764cab4d22d1 -C extra-filename=-67d0396294388d06 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn --check-cfg 'cfg(crossbeam_no_atomic,crossbeam_sanitize_thread)'` Running `/usr/bin/rustc --crate-name crossbeam_epoch --edition=2021 /usr/share/cargo/registry/crossbeam-epoch-0.9.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="alloc"' --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("alloc", "default", "nightly", "std"))' -C metadata=08036ba16fc12926 -C extra-filename=-25a78554006a775e --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern crossbeam_utils=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libcrossbeam_utils-67d0396294388d06.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn --check-cfg 'cfg(crossbeam_sanitize_thread)'` Running `/usr/bin/rustc --crate-name crossbeam_deque --edition=2021 /usr/share/cargo/registry/crossbeam-deque-0.8.8/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=6766c807617daa7b -C extra-filename=-5dae0cd8fe79ef9e --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern crossbeam_epoch=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libcrossbeam_epoch-25a78554006a775e.rmeta --extern crossbeam_utils=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libcrossbeam_utils-67d0396294388d06.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn --check-cfg 'cfg(crossbeam_sanitize_thread)'` Running `/usr/bin/rustc --crate-name rayon_core --edition=2021 /usr/share/cargo/registry/rayon-core-1.13.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=197942021e164fe6 -C extra-filename=-d39c2cba19561829 --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern crossbeam_deque=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libcrossbeam_deque-5dae0cd8fe79ef9e.rmeta --extern crossbeam_utils=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libcrossbeam_utils-67d0396294388d06.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling rayon v1.12.0 Running `/usr/bin/rustc --crate-name rayon --edition=2021 /usr/share/cargo/registry/rayon-1.12.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=3e23d289dbd28e94 -C extra-filename=-0efdf445a60f999f --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern either=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libeither-0e3c851e881c60aa.rmeta --extern rayon_core=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/librayon_core-d39c2cba19561829.rmeta --cap-lints allow -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` Compiling libcst v1.8.6 (/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6) 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=65a6a4f0679172eb -C extra-filename=-bf3716f842f31e8e --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern annotate_snippets=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libannotate_snippets-c83ae72c36bb1eec.rlib --extern difference=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libdifference-9c4b33aa3e86c4ee.rlib --extern itertools=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libitertools-7d19ca41e12c3426.rlib --extern libcst_derive=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/liblibcst_derive-7b62f9686e2d2fcc.so --extern memchr=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libmemchr-eb7735759febd272.rlib --extern paste=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libpaste-ef67be6a2fe550e0.so --extern peg=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libpeg-8060f164137eb297.rlib --extern rayon=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/librayon-0efdf445a60f999f.rlib --extern regex=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libregex-8e4c91a207e2f9f7.rlib --extern thiserror=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libthiserror-7a8e026ecce6c013.rlib -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` 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=10d66840d8abe03f -C extra-filename=-fdcbca10f2c202bd --out-dir /builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps --extern annotate_snippets=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libannotate_snippets-c83ae72c36bb1eec.rlib --extern difference=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libdifference-9c4b33aa3e86c4ee.rlib --extern itertools=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libitertools-7d19ca41e12c3426.rlib --extern libcst_native=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/liblibcst_native-5d31d91ffdbcd127.rlib --extern libcst_derive=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/liblibcst_derive-7b62f9686e2d2fcc.so --extern memchr=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libmemchr-eb7735759febd272.rlib --extern paste=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libpaste-ef67be6a2fe550e0.so --extern peg=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libpeg-8060f164137eb297.rlib --extern rayon=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/librayon-0efdf445a60f999f.rlib --extern regex=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libregex-8e4c91a207e2f9f7.rlib --extern thiserror=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libthiserror-7a8e026ecce6c013.rlib -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn` warning: hiding a lifetime that's elided elsewhere is confusing --> src/tokenizer/whitespace_parser.rs:461:38 | 461 | fn _parse_simple_whitespace(src: &str) -> Result { | ^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ | | | | | | | the same lifetime is hidden here | | the same lifetime is hidden here | the lifetime is elided here | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing help: use `'_` for type paths | 461 | fn _parse_simple_whitespace(src: &str) -> Result<'_, SimpleWhitespace<'_>> { | +++ ++++ warning: hiding a lifetime that's elided elsewhere is confusing --> src/tokenizer/whitespace_parser.rs:502:28 | 502 | fn _parse_comment(src: &str) -> Result> { | ^^^^ ^^^^^^^^^^^^^^^^^^^^^^^ | | | | | | | the same lifetime is hidden here | | the same lifetime is hidden here | the lifetime is elided here | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing help: use `'_` for type paths | 502 | fn _parse_comment(src: &str) -> Result<'_, Option>> { | +++ ++++ warning: panic message contains braces --> src/lib.rs:202:32 | 202 | "Failed to parse t'{{hello}}'" | ^^ ^^ | = note: this message is not used as a format string, but will be in Rust 2021 = note: for more information, see = note: `#[warn(non_fmt_panics)]` (part of `#[warn(rust_2021_compatibility)]`) on by default help: add a "{}" format string to use the message literally | 202 | "{}", "Failed to parse t'{{hello}}'" | +++++ warning: panic message contains braces --> src/lib.rs:206:32 | 206 | "Failed to parse t'{{hello:r}}'" | ^^ ^^ | = note: this message is not used as a format string, but will be in Rust 2021 = note: for more information, see help: add a "{}" format string to use the message literally | 206 | "{}", "Failed to parse t'{{hello:r}}'" | +++++ warning: panic message contains braces --> src/lib.rs:210:40 | 210 | "Failed to parse t'line1\\n{{hello:r}}\\nline2'" | ^^ ^^ | = note: this message is not used as a format string, but will be in Rust 2021 = note: for more information, see help: add a "{}" format string to use the message literally | 210 | "{}", "Failed to parse t'line1\\n{{hello:r}}\\nline2'" | +++++ warning: `libcst` (lib test) generated 178 warnings (173 duplicates) (run `cargo fix --lib -p libcst --tests` to apply 5 suggestions) Finished `rpm` profile [optimized + debuginfo] target(s) in 2m 53s Running `/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libcst_native-bf3716f842f31e8e` running 53 tests test test::bol_offset_last_line ... ok test test::bol_offset_second_line ... ok test test::bol_offset_first_line ... ok test test::test_bare_minimum_funcdef ... ok test test::test_single_statement_with_no_newline ... 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 tokenizer::tests::test_add_dedents_for_dangling_indent ... ok test tokenizer::tests::test_can_tokenize_f_and_t_strings ... ok test tokenizer::tests::test_add_dedents_after_fake_newline ... ok test test::test_tstring_basic ... ok test tokenizer::tests::test_fake_newline_when_at_bol ... ok test tokenizer::tests::test_fraction ... ok test tokenizer::tests::test_fstring_escapes ... ok test tokenizer::tests::test_indentifier ... ok test tokenizer::tests::test_indent_dedent ... ok test tokenizer::tests::test_inconsistent_indentation_at_eof ... ok test tokenizer::tests::test_async_await ... ok test tokenizer::tests::test_integer_binary ... ok test tokenizer::tests::test_integer_decimal ... ok test tokenizer::tests::test_integer_hexadecimal ... ok test tokenizer::tests::test_integer_leading_zeros ... ok test tokenizer::tests::test_nested_f_string_specs ... ok test tokenizer::tests::test_nested_f_strings ... ok test tokenizer::tests::test_newline ... ok test tokenizer::tests::test_can_tokenize_t_string_basic ... ok test tokenizer::tests::test_no_fake_newline_for_empty_input ... ok test tokenizer::tests::test_fake_newline ... ok test tokenizer::tests::test_no_fake_newline_for_only_whitespaces ... ok test tokenizer::tests::test_operator ... ok test tokenizer::tests::test_string ... ok test tokenizer::tests::test_split_ftstring ... ok test tokenizer::tests::test_string_triple_quoted ... ok test tokenizer::tests::test_string_prefix ... ok test tokenizer::text_position::char_width::tests::test_ascii_no_newlines ... ok test tokenizer::text_position::char_width::tests::test_empty ... ok test tokenizer::text_position::char_width::tests::test_newlines ... ok test tokenizer::tests::test_integer_octal ... 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::comment_until_eof ... ok test tokenizer::whitespace_parser::tests::config_mixed_newlines ... ok test tokenizer::whitespace_parser::tests::simple_whitespace_line_continuations ... ok test tokenizer::whitespace_parser::tests::no_comment ... ok test tokenizer::whitespace_parser::tests::simple_whitespace_mixed ... ok test tokenizer::whitespace_parser::tests::single_comment ... ok test result: ok. 53 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.04s Running `/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/parse-fdcbca10f2c202bd` 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.6-build/libcst-1.8.6 --extern annotate_snippets=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libannotate_snippets-c83ae72c36bb1eec.rlib --extern difference=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libdifference-9c4b33aa3e86c4ee.rlib --extern itertools=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libitertools-7d19ca41e12c3426.rlib --extern libcst_native=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/liblibcst_native-5d31d91ffdbcd127.rlib --extern libcst_derive=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/liblibcst_derive-7b62f9686e2d2fcc.so --extern memchr=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libmemchr-eb7735759febd272.rlib --extern paste=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libpaste-ef67be6a2fe550e0.so --extern peg=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libpeg-8060f164137eb297.rlib --extern rayon=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/librayon-0efdf445a60f999f.rlib --extern regex=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libregex-8e4c91a207e2f9f7.rlib --extern thiserror=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps/libthiserror-7a8e026ecce6c013.rlib -L dependency=/builddir/build/BUILD/rust-libcst-1.8.6-build/libcst-1.8.6/target/rpm/deps -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.6-3.fc45.noarch warning: File listed twice: /usr/share/cargo/registry/libcst-1.8.6/LICENSE warning: File listed twice: /usr/share/cargo/registry/libcst-1.8.6/README.md warning: File listed twice: /usr/share/cargo/registry/libcst-1.8.6/src/tokenizer/core/LICENSE Provides: crate(libcst) = 1.8.6 purl(pkg:cargo/libcst@1.8.6) rust-libcst-devel = 1.8.6-3.fc45 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.6 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.2 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.6-3.fc45.noarch Provides: crate(libcst/default) = 1.8.6 rust-libcst+default-devel = 1.8.6-3.fc45 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.6 Processing files: rust-libcst+trace-devel-1.8.6-3.fc45.noarch Provides: crate(libcst/trace) = 1.8.6 rust-libcst+trace-devel = 1.8.6-3.fc45 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.6 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILD/rust-libcst-1.8.6-build/BUILDROOT Wrote: /builddir/build/SRPMS/rust-libcst-1.8.6-3.fc45.src.rpm Wrote: /builddir/build/RPMS/rust-libcst+default-devel-1.8.6-3.fc45.noarch.rpm Wrote: /builddir/build/RPMS/rust-libcst+trace-devel-1.8.6-3.fc45.noarch.rpm Wrote: /builddir/build/RPMS/rust-libcst-devel-1.8.6-3.fc45.noarch.rpm RPM build warnings: File listed twice: /usr/share/cargo/registry/libcst-1.8.6/LICENSE File listed twice: /usr/share/cargo/registry/libcst-1.8.6/README.md File listed twice: /usr/share/cargo/registry/libcst-1.8.6/src/tokenizer/core/LICENSE Child return code was: 0