BUG preserve_key_order still method not found

[danielzgtg]

Describe the bug
Half a year later, I still cannot cargo install qsv -....

To Reproduce
Steps to reproduce the behavior:

1. cargo install qsv --locked --features feature_capable

Expected behavior
It should produce a qsv binary.

Screenshots/Backtrace/Sample Data

   Compiling qsv v16.1.0
error[E0599]: no method named `preserve_key_order` found for struct `Json2Csv` in the current scope
   --> /home/home/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/qsv-16.1.0/src/cmd/json.rs:330:14
    |
329 | /         Json2Csv::new(flattener)
330 | |             .preserve_key_order(true)
    | |             -^^^^^^^^^^^^^^^^^^ method not found in `Json2Csv`
    | |_____________|
    |

For more information about this error, try `rustc --explain E0599`.
error: could not compile `qsv` (bin "qsv") due to 1 previous error
error: failed to compile `qsv v16.1.0`, intermediate artifacts can be found at `/tmp/cargo-installohKHyA`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

Desktop (please complete the following information):

• OS: Ubuntu 25.10
• qsv v16.1.0

Additional context

You said:

If its not merged, I may ultimately make a renamed fork and publish it on crates.io as I've done with other unmaintained crates like dynfmt, docopt, vader_sentiment_analysis, etc.

It's still not merged after so long, and that dependency is the one thing holding cargo install back. @vtselfa hasn't been active at all last year, so I don't think it will be merged. Please fork.

[jqnatividad]

@danielzgtg , I'm afraid qsv is NOT cargo installable and will probably never be.

That's because we make EXTENSIVE use of git dependencies which are not supported by cargo install beyond json-objects-to-csv.

qsv/Cargo.toml

Lines 306 to 372 in 330998e

	[patch.crates-io]
	# use our tweaked fork of csv crate
	# the csv crate underpins a lot of qsv's functionality, so every perf tweak helps
	# the main features of this csv fork is SIMD-accelerated UTF-8 validation;
	# non-allocating ByteRecord trim and StringRecord trim;
	# a faster `is_non_numeric()` helper;
	# replace byte-by-byte loop in csv-core's scan_and_copy with
	# memchr-based SIMD scanning and copy_from_slice bulk copy;
	# Add the scan_and_copy fast-path to read_field_dfa (previously only in read_record_dfa);
	# and various clippy lint suggestions applied
	csv = { git = "https://github.com/dathere/rust-csv", branch = "qsv-tuned" }
	csv-core = { git = "https://github.com/dathere/rust-csv", branch = "qsv-tuned" }
	csv-index = { git = "https://github.com/dathere/rust-csv", branch = "qsv-tuned" }
	# csv = { path = "../rust-csv" }
	# csv-core = { path = "../rust-csv/csv-core" }
	# csv-index = { path = "../rust-csv/csv-index" }
	# use fork with updated redis 1.0 dependency & client-side caching features
	cached = { git = "https://github.com/nihohit/cached", branch = "client-side-caching" }
	# use our patched fork to bump dependencies until our PR is merged
	csvlens = { git = "https://github.com/jqnatividad/csvlens", branch = "bump-deps-202602" }
	# use our patched fork of csvs_convert to bump dependencies until our PR is merged
	csvs_convert = { git = "https://github.com/jqnatividad/csvs_convert", branch = "bump-deps-202602", optional = true }
	# use latest geosuggest upstream
	geosuggest-core = { git = "https://github.com/estin/geosuggest", rev = "0430e92" }
	geosuggest-utils = { git = "https://github.com/estin/geosuggest", rev = "0430e92" }
	# use our patched fork of json-objects-to-csv to bump deps and to preserve order until our PR is merged
	json-objects-to-csv = { git = "https://github.com/jqnatividad/json-objects-to-csv", branch = "preserve_order_issue_10" }
	# use latest upstream now that our PR has been merged while awaiting a new release
	kiddo = { git = "https://github.com/sdd/kiddo.git", rev = "2056051"}
	# use upstream of mimalloc with unreleased fixes
	mimalloc = { git = "https://github.com/purpleprotocol/mimalloc_rust", rev = "7daf67f", optional = true }
	# use our patched fork of self_update with bumped dependencies at older revision
	# the latest upstream has replaced reqwest which breaks our build
	self_update = { git = "https://github.com/jaemk/self_update", rev = "62b93c6", optional = true }
	# use our patched fork of sled to get rid of unmaintained instant
	sled = { git = "https://github.com/dathere/sled", branch = "v0.34.7-bumped-parking_lot_to_0.12" }
	# Polars has a much higher release tempo for its Python bindings compared
	# to its underlying Rust library. See https://github.com/pola-rs/polars/releases
	# It's qsv's policy to use the latest upstream of polars/py-polars
	# to take advantage of Polars' latest unreleased fixes and features.
	# Based on what's available at the time of qsv's release, we may need to pin polars to a py-polars tag
	# or a specific commit if more revisions have been made since the latest polars/py-polars release.
	# BUILD NOTE: Be sure to set QSV_POLARS_REV below to the latest commit short hash or tag
	# of polars/py-polars before building qsv. This allows us to show the polars rev/tag in --version.
	# The convention to use for QSV_POLARS_REV is:
	# - if we are using a release version of Rust Polars, leave QSV_POLARS_REV empty
	# - if we are using a release version of Python Polars, use the Python tag
	# (e.g. py-1.19.0)
	# - if we are using a commit hash, separate the tag and commit hash with a colon, in the order of
	# - Python Polars tag
	# - short commit hash
	# (e.g. py-1.19.0:52ea381 to indicate that we are Python Polars 1.19.0,
	# and the commit hash 52ea381)
	# ================================
	# QSV_POLARS_REV=54c9168
	# polars = { git = "https://github.com/pola-rs/polars", tag = "py-1.38.1", optional = true }
	polars = { git = "https://github.com/pola-rs/polars", rev = "54c9168", optional = true }

If you'd rather not install the prebuilt binaries on the release page, you can alway:

• use a package manager that distributes qsv
• compile from source

[jqnatividad]

Closing this @danielzgtg as this is by design.

[jqnatividad]

Reopening this again to confirm that I'll be creating a renamed fork of json-objects-to-csv.

[danielzgtg]

I'm afraid qsv is NOT cargo installable and will probably never be

qsv 1.0.0 was cargo installable with rustc version 1.85.0-nightly (4363f9b6f 2025-01-02)

compile from source

I just discovered cargo install --path . --force --features=feature_capable exists. I will change my system update script to use it.

[jqnatividad]

That's awesome!

Does it require nightly? Does it work with stable? On 1.93?

I set MSRV to the latest stable and use the latest language features when possible so I'd b be surprised if it works on 1.85.0 nightly...

[danielzgtg]

qsv version 1.0.0, released 2 December 2024, has MSRV 1.83.0. I am waiting for the fork and a new crates.io release before I can reattempt cargo install qsv --locked --features=feature_capable.

The cargo install --path . must be executed inside a Git-cloned folder, so it's just cargo build plus a move, not the usual cargo install. I used stable rustc 1.93.1 (01f6ddf75 2026-02-11) today.