MyFavMirrors
/
moonfire-nvr
mirror of https://github.com/scottlamb/moonfire-nvr.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
moonfire-nvr/server/Cargo.lock

2774 lines
66 KiB
Plaintext
Raw Normal View History

redact URLs within stream.rs; fixes #13
2019-02-14 01:34:19 -05:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
upgrade to retina 0.0.3 The new version is more efficient.
2021-06-28 17:25:02 -04:00
version = 3
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
[[package]]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
name = "addr2line"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.16.0"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "3e61f2b7f93d2c7d2b08263acaa4a363b3e276806c68af6134c44f523bf1aacd"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
dependencies = [
"gimli",
]
[[package]]
name = "adler"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "1.0.2"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "f26201604c87b1e01bd3d98f8d5d9a8fcbb815e8cedb41ffccbeb4bf593a35fe"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
upgrade rusqlite, linked-hash-map/hashlink With Rust 1.48.0, I was getting panics like "attempted to leave type `linked_hash_map::Node<std::string::String, raw_statement::RawStatement>` uninitialized, which is invalid". Looks like this is due to a bug in linked-hash-map 0.5.2, fixed with 0.5.3. Along the way, I see that rusqlite no longer uses this crate; it switched to hashlink. Upgrade rusqlite and match that change for my own use (video index LRU cache). I'm still pulling in linked-hash-map via serde_yaml. I didn't even realize I was using serde_yaml, but libpasta wants it. Seems a little silly to me but that's something I might explore another day.
2020-11-22 20:37:55 -05:00
[[package]]
name = "ahash"
upgrade some other deps
2021-01-27 15:11:36 -05:00
version = "0.6.3"
upgrade rusqlite, linked-hash-map/hashlink With Rust 1.48.0, I was getting panics like "attempted to leave type `linked_hash_map::Node<std::string::String, raw_statement::RawStatement>` uninitialized, which is invalid". Looks like this is due to a bug in linked-hash-map 0.5.2, fixed with 0.5.3. Along the way, I see that rusqlite no longer uses this crate; it switched to hashlink. Upgrade rusqlite and match that change for my own use (video index LRU cache). I'm still pulling in linked-hash-map via serde_yaml. I didn't even realize I was using serde_yaml, but libpasta wants it. Seems a little silly to me but that's something I might explore another day.
2020-11-22 20:37:55 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some other deps
2021-01-27 15:11:36 -05:00
checksum = "796540673305a66d127804eef19ad696f1f204b8c1025aaca4958c17eab32877"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
dependencies = [
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
"getrandom 0.2.3",
upgrade some other deps
2021-01-27 15:11:36 -05:00
"once_cell",
"version_check",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
]
upgrade rusqlite, linked-hash-map/hashlink With Rust 1.48.0, I was getting panics like "attempted to leave type `linked_hash_map::Node<std::string::String, raw_statement::RawStatement>` uninitialized, which is invalid". Looks like this is due to a bug in linked-hash-map 0.5.2, fixed with 0.5.3. Along the way, I see that rusqlite no longer uses this crate; it switched to hashlink. Upgrade rusqlite and match that change for my own use (video index LRU cache). I'm still pulling in linked-hash-map via serde_yaml. I didn't even realize I was using serde_yaml, but libpasta wants it. Seems a little silly to me but that's something I might explore another day.
2020-11-22 20:37:55 -05:00
update rusqlite The big difference here is query_named and execute_named have gone away. Fair number of lines changes but straightforward.
2021-05-17 13:50:12 -04:00
[[package]]
name = "ahash"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.7.4"
update rusqlite The big difference here is query_named and execute_named have gone away. Fair number of lines changes but straightforward.
2021-05-17 13:50:12 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "43bb833f0bf979d8475d38fbf09ed3b8a55e1885fe93ad3f93239fc6a4f17b98"
update rusqlite The big difference here is query_named and execute_named have gone away. Fair number of lines changes but straightforward.
2021-05-17 13:50:12 -04:00
dependencies = [
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
"getrandom 0.2.3",
update rusqlite The big difference here is query_named and execute_named have gone away. Fair number of lines changes but straightforward.
2021-05-17 13:50:12 -04:00
"once_cell",
"version_check",
]
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
[[package]]
name = "ansi_term"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "ee49baf6cb617b853aa8d93bf420db2383fab46d314482ca2803b40d5fde979b"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
dependencies = [
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
]
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "argon2rs"
version = "0.2.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "3f67b0b6a86dae6e67ff4ca2b6201396074996379fba2b92ff649126f37cb392"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"blake2-rfc",
"scoped_threadpool",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
]
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
name = "array-macro"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "1.0.5"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "06e97b4e522f9e55523001238ac59d13a8603af57f69980de5d8de4bbbe8ada6"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "arrayref"
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
version = "0.3.6"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
checksum = "a4c527152e37cf757a3f78aae5a06fbeefdb07ccc535c980a3208ee3060dd544"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
[[package]]
name = "arrayvec"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
version = "0.4.12"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "cd9fd44efafa8690358b7408d253adf110036b88f55672a933f01d616ad9b1b9"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"nodrop",
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
]
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "arrayvec"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.5.2"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "23b62fc65de8e4e7f52534fb52b0f3ed04746ae267519eef2a83941e8085068b"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
[[package]]
name = "arrayvec"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "be4dc07131ffa69b8072d35f5007352af944213cde02545e2103680baed38fcd"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
[[package]]
name = "atty"
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
version = "0.2.14"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
dependencies = [
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
"hermit-abi",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"libc",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
]
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
[[package]]
name = "autocfg"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "1.0.1"
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "cdb031dd78e28731d87d56cc8ffef4a8f36ca26c38fe2de700543e627f8a464a"
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
[[package]]
name = "backtrace"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.3.61"
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "e7a905d892734eea339e896738c14b9afce22b5318f64b951e70bf3844419b01"
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
dependencies = [
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"addr2line",
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
"cc",
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"libc",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"miniz_oxide",
"object",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"rustc-demangle",
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "base64"
version = "0.13.0"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "904dfeac50f3cdaba28fc6f57fdcddb75f49ed61346676a78c4ffe55877802fd"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
update libpasta deps
2021-05-17 16:02:26 -04:00
[[package]]
name = "base64ct"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "1.1.0"
update libpasta deps
2021-05-17 16:02:26 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "40a96587c05c810ddbb79e2674d519cff1379517e7b91d166dff7a7cc0e9af6e"
update libpasta deps
2021-05-17 16:02:26 -04:00
[[package]]
name = "bcrypt"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a4d0faafe9e089674fc3efdb311ff5253d445c79d85d1d28bd3ace76d45e7164"
dependencies = [
"base64",
"blowfish",
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
"getrandom 0.2.3",
update libpasta deps
2021-05-17 16:02:26 -04:00
]
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
name = "bitflags"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "1.3.2"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "bef38d45163c2f1dde094a7dfd33ccf595c92905c8f8f4fdc18d06fb1037718a"
update dependencies
2017-11-17 02:01:09 -05:00
schema version 6 with pixel aspect ratio This makes anamorphic sub streams display correctly, even ones from old Hikvision cameras that don't properly set the aspect ratio at the H.264 layer.
2020-03-20 00:35:42 -04:00
[[package]]
name = "bitreader"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.3.4"
schema version 6 with pixel aspect ratio This makes anamorphic sub streams display correctly, even ones from old Hikvision cameras that don't properly set the aspect ratio at the H.264 layer.
2020-03-20 00:35:42 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "9178181a7d44239c6c8eaafa8688558a2ab5fa04b8855381f2681e9591fb941b"
schema version 6 with pixel aspect ratio This makes anamorphic sub streams display correctly, even ones from old Hikvision cameras that don't properly set the aspect ratio at the H.264 layer.
2020-03-20 00:35:42 -04:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
]
[[package]]
name = "bitvec"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "0.19.5"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "8942c8d352ae1838c9dda0b0ca2ab657696ef2232a20147cf1b30ae1a9cb4321"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
dependencies = [
"funty",
"radium",
"tap",
"wyz",
schema version 6 with pixel aspect ratio This makes anamorphic sub streams display correctly, even ones from old Hikvision cameras that don't properly set the aspect ratio at the H.264 layer.
2020-03-20 00:35:42 -04:00
]
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "blake2-rfc"
version = "0.2.18"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "5d6d530bdd2d52966a6d03b7a964add7ae1a288d25214066fd4b600f0f796400"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"arrayvec 0.4.12",
"constant_time_eq",
]
[[package]]
name = "blake2b_simd"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.5.11"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "afa748e348ad3be8263be728124b24a24f268266f6f5d58af9d75f6a40b5c587"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
"arrayref",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"arrayvec 0.5.2",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"constant_time_eq",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
]
use Blake3 instead of SHA-1 or Blake2b Benefits: * Blake3 is faster. This is most noticeable for the hashing of the sample file data. * we no longer need OpenSSL, which helps with shrinking the binary size (#70). sha1 basically forced OpenSSL usage; ring deliberately doesn't support this old algorithm, and the pure-Rust sha1 crate is painfully slow. OpenSSL might still be a better choice than ring/rustls for TLS but it's nice to have the option. For the video sample entries, I decided we don't need to hash at all. I think the id number is sufficiently stable, and it's okay---perhaps even desirable---if an existing init segment changes for fixes like e5b83c2.
2020-03-20 23:52:30 -04:00
[[package]]
name = "blake3"
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
version = "1.0.0"
use Blake3 instead of SHA-1 or Blake2b Benefits: * Blake3 is faster. This is most noticeable for the hashing of the sample file data. * we no longer need OpenSSL, which helps with shrinking the binary size (#70). sha1 basically forced OpenSSL usage; ring deliberately doesn't support this old algorithm, and the pure-Rust sha1 crate is painfully slow. OpenSSL might still be a better choice than ring/rustls for TLS but it's nice to have the option. For the video sample entries, I decided we don't need to hash at all. I think the id number is sufficiently stable, and it's okay---perhaps even desirable---if an existing init segment changes for fixes like e5b83c2.
2020-03-20 23:52:30 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
checksum = "dcd555c66291d5f836dbb6883b48660ece810fe25a31f3bdfb911945dff2691f"
use Blake3 instead of SHA-1 or Blake2b Benefits: * Blake3 is faster. This is most noticeable for the hashing of the sample file data. * we no longer need OpenSSL, which helps with shrinking the binary size (#70). sha1 basically forced OpenSSL usage; ring deliberately doesn't support this old algorithm, and the pure-Rust sha1 crate is painfully slow. OpenSSL might still be a better choice than ring/rustls for TLS but it's nice to have the option. For the video sample entries, I decided we don't need to hash at all. I think the id number is sufficiently stable, and it's okay---perhaps even desirable---if an existing init segment changes for fixes like e5b83c2.
2020-03-20 23:52:30 -04:00
dependencies = [
"arrayref",
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"arrayvec 0.7.1",
use Blake3 instead of SHA-1 or Blake2b Benefits: * Blake3 is faster. This is most noticeable for the hashing of the sample file data. * we no longer need OpenSSL, which helps with shrinking the binary size (#70). sha1 basically forced OpenSSL usage; ring deliberately doesn't support this old algorithm, and the pure-Rust sha1 crate is painfully slow. OpenSSL might still be a better choice than ring/rustls for TLS but it's nice to have the option. For the video sample entries, I decided we don't need to hash at all. I think the id number is sufficiently stable, and it's okay---perhaps even desirable---if an existing init segment changes for fixes like e5b83c2.
2020-03-20 23:52:30 -04:00
"cc",
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
use Blake3 instead of SHA-1 or Blake2b Benefits: * Blake3 is faster. This is most noticeable for the hashing of the sample file data. * we no longer need OpenSSL, which helps with shrinking the binary size (#70). sha1 basically forced OpenSSL usage; ring deliberately doesn't support this old algorithm, and the pure-Rust sha1 crate is painfully slow. OpenSSL might still be a better choice than ring/rustls for TLS but it's nice to have the option. For the video sample entries, I decided we don't need to hash at all. I think the id number is sufficiently stable, and it's okay---perhaps even desirable---if an existing init segment changes for fixes like e5b83c2.
2020-03-20 23:52:30 -04:00
"constant_time_eq",
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
"digest",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
]
[[package]]
name = "block-buffer"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4152116fd6e9dadb291ae18fc1ec3575ed6d84c29642d97890f4b4a3417297e4"
dependencies = [
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
"generic-array",
update deps
2019-02-14 01:43:30 -05:00
]
update libpasta deps
2021-05-17 16:02:26 -04:00
[[package]]
name = "blowfish"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "32fa6a061124e37baba002e496d203e23ba3d7b73750be82dbfbc92913048a5b"
dependencies = [
"byteorder",
"cipher 0.2.5",
"opaque-debug",
]
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
[[package]]
name = "bstr"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.2.17"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "ba3569f383e8f1598449f1a423e72e99569137b47740b1da11ef19af3d5c3223"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"lazy_static",
"memchr",
"regex-automata",
"serde",
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
]
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
[[package]]
name = "bumpalo"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "3.7.1"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "d9df67f7bf9ef8498769f994239c45613ef0c5899415fb58e9add412d2c1a538"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "byteorder"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "1.4.3"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "14c189c53d098945499cdfa7ecc63567cf3886b3332b312a5b4585d8d3a6a610"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "bytes"
cargo update
2021-08-31 15:59:39 -04:00
version = "1.1.0"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "c4872d67bab6358e59559027aa3b9157c53d9358c51423c17554809a8858e0f8"
update deps The immediate motivation is that Cargo.lock referred to a commit version in a PR branch of my nix fork that no longer exists. (I didn't know, but it makes sense, that "git push -f" not only forcibly updates the branch to refer to a new commit but also gets rid of orphaned commits.) Use a moonfire branch that I'll keep stable until I'm ready to move on. I also updated parking_lot and rusqlite to new major versions (nothing in the interface that I care about has changed) and did a full cargo update.
2019-07-17 17:32:09 -04:00
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
[[package]]
name = "cc"
cargo update
2021-08-31 15:59:39 -04:00
version = "1.0.70"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "d26a6ce4b6a484fa3edb70f7efa6fc430fd2b87285fe8b84304fd0936faa0dc0"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "cfg-if"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
[[package]]
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
name = "chrono"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.4.19"
upgrade a few deps
2018-08-25 01:06:14 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "670ad68c9088c2a963aaa298cb369688cf3f9465ce5e2d4ca10e6e0098a1ce73"
upgrade a few deps
2018-08-25 01:06:14 -04:00
dependencies = [
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"libc",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"num-integer",
"num-traits",
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
"time",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
upgrade a few deps
2018-08-25 01:06:14 -04:00
]
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
[[package]]
name = "cipher"
version = "0.2.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "12f8e7987cbd042a63249497f41aed09f8e65add917ea6566effbc56578d6801"
dependencies = [
"generic-array",
]
update libpasta deps
2021-05-17 16:02:26 -04:00
[[package]]
name = "cipher"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7ee52072ec15386f770805afd189a01c8841be8696bed250fa2f13c4c0d6dfb7"
dependencies = [
"generic-array",
]
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
[[package]]
name = "clap"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "2.33.3"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "37e58ac78573c40708d45522f0d80fa2f01cc4f9b4e2bf749807255454312002"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
dependencies = [
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"ansi_term",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"atty",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"bitflags",
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
"term_size",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"textwrap",
"unicode-width",
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
]
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "constant_time_eq"
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
version = "0.1.5"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
checksum = "245097e9a4535ee1e3e3931fcfcd55a796a44c643e8596ff6566d68f09b87bbc"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
[[package]]
name = "cookie-factory"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "396de984970346b0d9e93d1415082923c679e5ae5c3ee3dcbd104f5610af126b"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
name = "cpufeatures"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.2.1"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "95059428f66df56b63431fdb4e1947ed2190586af5c5a8a8b71122bdf5a7f469"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
dependencies = [
"libc",
]
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
name = "crc32fast"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "1.2.1"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "81156fece84ab6a9f2afdb109ce3ae577e42b1228441eded99bd77f627953b1a"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
]
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
update deps
2019-02-14 01:43:30 -05:00
name = "crossbeam-channel"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "0.5.1"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "06ed27e177f16d65f0f0c22a213e17c696ace5dd64b14258b52f9417ccb52db4"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
"crossbeam-utils",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
]
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
[[package]]
name = "crossbeam-utils"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.8.5"
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "d82cfc11ce7f2c3faef78d8a684447b40d503d9681acebed6cb728d45940c4db"
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
"lazy_static",
]
use cstr crate rather than unsafe This removes a few uses of unsafe, and it verifies statically that there are no interior NUL bytes.
2019-07-04 17:51:38 -04:00
[[package]]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
name = "crypto-mac"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.11.1"
use cstr crate rather than unsafe This removes a few uses of unsafe, and it verifies statically that there are no interior NUL bytes.
2019-07-04 17:51:38 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "b1d1a86f49236c215f271d40892d5fc950490551400b02ef360692c29815c714"
use cstr crate rather than unsafe This removes a few uses of unsafe, and it verifies statically that there are no interior NUL bytes.
2019-07-04 17:51:38 -04:00
dependencies = [
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
"generic-array",
"subtle",
use cstr crate rather than unsafe This removes a few uses of unsafe, and it verifies statically that there are no interior NUL bytes.
2019-07-04 17:51:38 -04:00
]
[[package]]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
name = "cstr"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.2.9"
use cstr crate rather than unsafe This removes a few uses of unsafe, and it verifies statically that there are no interior NUL bytes.
2019-07-04 17:51:38 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "f2846d3636dcaff720d311ea8983f5fa7a8288632b2f95145dd4b5819c397fd8"
use cstr crate rather than unsafe This removes a few uses of unsafe, and it verifies statically that there are no interior NUL bytes.
2019-07-04 17:51:38 -04:00
dependencies = [
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
use cstr crate rather than unsafe This removes a few uses of unsafe, and it verifies statically that there are no interior NUL bytes.
2019-07-04 17:51:38 -04:00
]
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
[[package]]
name = "csv"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "1.1.6"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "22813a6dc45b335f9bade10bf7271dc477e81113e89eb251a0bc2a8a81c536e1"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"bstr",
"csv-core",
"itoa",
"ryu",
"serde",
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
]
[[package]]
name = "csv-core"
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
version = "0.1.10"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
checksum = "2b2466559f260f48ad25fe6317b3c8dac77b5bdb5763ac7d9d6103530663bc90"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"memchr",
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
]
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
[[package]]
name = "cursive"
upgrade some other deps
2021-01-27 15:11:36 -05:00
version = "0.16.3"
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some other deps
2021-01-27 15:11:36 -05:00
checksum = "6593c3409eb794bf22090bec60dda1e19d1def284478bec7e5a92da3cf977c52"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
upgrade some other deps
2021-01-27 15:11:36 -05:00
"ahash 0.6.3",
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"crossbeam-channel",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"cursive_core",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"lazy_static",
"libc",
"log",
"maplit",
"ncurses",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"signal-hook",
"term_size",
"unicode-segmentation",
"unicode-width",
upgrade some other deps
2021-01-27 15:11:36 -05:00
"wasmer_enumset",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
]
[[package]]
name = "cursive_core"
upgrade some other deps
2021-01-27 15:11:36 -05:00
version = "0.2.2"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some other deps
2021-01-27 15:11:36 -05:00
checksum = "025ac0bcd21ced752d27b70e6aa2285a3513d07b5a0c7f89e71121d20ca1429d"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
dependencies = [
upgrade some other deps
2021-01-27 15:11:36 -05:00
"ahash 0.6.3",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"chrono",
"crossbeam-channel",
"enum-map",
"lazy_static",
"libc",
"log",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"num",
"owning_ref",
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"syn",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"unicode-segmentation",
"unicode-width",
upgrade some other deps
2021-01-27 15:11:36 -05:00
"wasmer_enumset",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"xi-unicode",
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
]
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
[[package]]
name = "darling"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
version = "0.10.2"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "0d706e75d87e35569db781a9b5e2416cff1236a47ed380831f959382ccd5f858"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"darling_core",
"darling_macro",
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
]
[[package]]
name = "darling_core"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
version = "0.10.2"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "f0c960ae2da4de88a91b2d920c2a7233b400bc33cb28453a2987822d8392519b"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"fnv",
"ident_case",
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
tweak deps, eliminating strsim 0.8 dependency I also enabled the colored help option for clap, since we're paying for the color dep anyway.
2021-06-15 03:45:11 -04:00
"strsim",
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"syn",
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
]
[[package]]
name = "darling_macro"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
version = "0.10.2"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "d9b5a2f4ac4969822c62224815d069952656cadc7084fdca9751e6d959189b72"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"darling_core",
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"quote",
"syn",
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
]
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "data-encoding"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "2.3.2"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "3ee2393c4a91429dffb4bedf19f4d6abf27d8a732c8ce4980305d782e5426d57"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "digest"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d3dd60d1080a57a05ab032377049e0591415d2b31afd7028356dbf3cc6dcb066"
dependencies = [
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
"generic-array",
update deps
2019-02-14 01:43:30 -05:00
]
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
[[package]]
name = "dirs"
version = "1.0.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "3fd78930633bd1c6e35c4b42b1df7b0cbc6bc191146e512bb3bedf243fcc3901"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"libc",
"redox_users",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
]
update several dependencies I left serde alone because uuid hasn't been updated for the new version.
2017-01-27 23:58:04 -05:00
[[package]]
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
name = "dtoa"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "0.4.8"
update several dependencies I left serde alone because uuid hasn't been updated for the new version.
2017-01-27 23:58:04 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "56899898ce76aaf4a0f24d914c97ea6ed976d42fec6ad33fcbb0a1103e07b2b0"
update several dependencies I left serde alone because uuid hasn't been updated for the new version.
2017-01-27 23:58:04 -05:00
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "either"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "1.6.1"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "e78d4f1cc4ae33bbfc157ed5d5a5ef3bc29227303d595861deb238fcec4e9457"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
[[package]]
name = "encode_unicode"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
version = "0.3.6"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "a357d28ed41a50f9c765dbfe56cbc04a64e53e5fc58ba79fbc34c10ef3df831f"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
[[package]]
name = "encoding_rs"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "0.8.28"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "80df024fbc5ac80f87dfef0d9f5209a252f2a497f7f42944cff24d8253cac065"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
]
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
name = "enum-map"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.6.4"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "4187999839f4ae8be35cf185d1381aa8dc32d2f5951349cc37ae49ebc4781855"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
dependencies = [
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
"array-macro",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"enum-map-derive",
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
]
[[package]]
name = "enum-map-derive"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.4.6"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "e5c450cf304c9e18d45db562025a14fb1ca0f5c769b6f609309f81d4c31de455"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
dependencies = [
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
"syn",
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
]
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "error-chain"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "ff511d5dc435d703f4971bc399647c9bc38e20cb41452e3b9feb4765419ed3f3"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"backtrace",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
]
update deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "error-chain"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.12.4"
update deps
2019-02-14 01:43:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "2d2f06b9cac1506ece98fe3231e3cc9c4410ec3d5b1f24ae1c8946f0742cdefc"
update deps
2019-02-14 01:43:30 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"backtrace",
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
"version_check",
update deps
2019-02-14 01:43:30 -05:00
]
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
[[package]]
name = "failure"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.1.8"
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "d32e9bd16cc02eae7db7ef620b392808b89f6a5e16bb3497d159c6b92a0f4f86"
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"backtrace",
"failure_derive",
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
]
[[package]]
name = "failure_derive"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.1.8"
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "aa4da3c766cd7a0db8242e326e9e4e081edd567072893ed320008189715366a4"
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
dependencies = [
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
"syn",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"synstructure",
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
]
upgrade rusqlite, bump required Rust to 1.33 The new rusqlite requires the transpose_result feature, stabilized in this Rust version.
2019-05-31 19:19:04 -04:00
[[package]]
name = "fallible-iterator"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "4443176a9f2c162692bd3d352d745ef9413eec5782a80d8fd6f8a1ac692a07f7"
upgrade rusqlite, bump required Rust to 1.33 The new rusqlite requires the transpose_result feature, stabilized in this Rust version.
2019-05-31 19:19:04 -04:00
[[package]]
name = "fallible-streaming-iterator"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "7360491ce676a36bf9bb3c56c1aa791658183a54d2744120f27285738d90465a"
upgrade rusqlite, bump required Rust to 1.33 The new rusqlite requires the transpose_result feature, stabilized in this Rust version.
2019-05-31 19:19:04 -04:00
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
[[package]]
name = "flate2"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "1.0.22"
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "1e6988e897c1c9c485f43b47a529cef42fde0547f9d8d41a7062518f1d8fc53f"
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"crc32fast",
"libc",
"miniz_oxide",
update most deps, notably including reqwest Fixes #60 The reqwest dependency is significant because the old version required an old version of openssl, complicating compilation on newer platforms. reqwest also pulled in old/duplicate versions of hyper, tokio, etc. Nice to drop a lot of that cruft. I left rusqlite and uuid alone because they had breaking changes I didn't want to mess with at the moment. Bumped the minimum Rust version to 1.30.0, as required by the new encoding_rs crate (and perhaps other things).
2018-11-20 12:32:55 -05:00
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "fnv"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "1.0.7"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "3f9eec918d3f24069decb9af1554cad7c880e2da24a9afd88aca000531ab82c1"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "form_urlencoded"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "1.0.1"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "5fc25a87fa4fd2094bffb06925852034d90a17f0d1e05197d4956d3555752191"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
dependencies = [
"matches",
"percent-encoding",
]
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
[[package]]
name = "four-cc"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3958af68a31b1d1384d3f39b6aa33eb14b6009065b5ca305ddd9712a4237124f"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "funty"
upgrade some other deps
2021-01-27 15:11:36 -05:00
version = "1.1.0"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some other deps
2021-01-27 15:11:36 -05:00
checksum = "fed34cd105917e91daa4da6b3728c47b068749d6a62c59811f06ed2ac71d9da7"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
[[package]]
name = "futures"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.3.17"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "a12aa0eb539080d55c3f2d45a67c3b58b6b0773c1a3ca2dfec66d58c97fd66ca"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
"futures-channel",
"futures-core",
"futures-executor",
"futures-io",
"futures-sink",
"futures-task",
"futures-util",
]
[[package]]
name = "futures-channel"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.3.17"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "5da6ba8c3bb3c165d3c7319fc1cc8304facf1fb8db99c5de877183c08a273888"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
"futures-core",
"futures-sink",
]
[[package]]
name = "futures-core"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.3.17"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "88d1c26957f23603395cd326b0ffe64124b818f4449552f960d815cfba83a53d"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "futures-executor"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.3.17"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "45025be030969d763025784f7f355043dc6bc74093e4ecc5000ca4dc50d8745c"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
"futures-core",
"futures-task",
"futures-util",
]
[[package]]
name = "futures-io"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.3.17"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "522de2a0fe3e380f1bc577ba0474108faf3f6b18321dbf60b3b9c39a75073377"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "futures-macro"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.3.17"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "18e4a4b95cea4b4ccbcf1c5675ca7c4ee4e9e75eb79944d07defde18068f79bb"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
dependencies = [
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
"autocfg",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"proc-macro-hack",
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
"syn",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
]
[[package]]
name = "futures-sink"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.3.17"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "36ea153c13024fe480590b3e3d4cad89a0cfacecc24577b68f86c6ced9c2bc11"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "futures-task"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.3.17"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "1d3d00f4eddb73e498a54394f228cd55853bdf059259e8e7bc6e69d408892e99"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "futures-util"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.3.17"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "36568465210a3a6ee45e1f165136d68671471a501e632e9a98d96872222b5481"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
"autocfg",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"futures-channel",
"futures-core",
"futures-io",
"futures-macro",
"futures-sink",
"futures-task",
"memchr",
upgrade some other deps
2021-01-27 15:11:36 -05:00
"pin-project-lite",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"pin-utils",
"proc-macro-hack",
"proc-macro-nested",
"slab",
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "generic-array"
version = "0.14.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "501466ecc8a30d1d3b7fc9229b122b2ce8ed6e9d9223f1138d4babb253e51817"
dependencies = [
"typenum",
"version_check",
]
update deps The immediate motivation is that Cargo.lock referred to a commit version in a PR branch of my nix fork that no longer exists. (I didn't know, but it makes sense, that "git push -f" not only forcibly updates the branch to refer to a new commit but also gets rid of orphaned commits.) Use a moonfire branch that I'll keep stable until I'm ready to move on. I also updated parking_lot and rusqlite to new major versions (nothing in the interface that I care about has changed) and did a full cargo update.
2019-07-17 17:32:09 -04:00
[[package]]
name = "getrandom"
upgrade some other deps
2021-01-27 15:11:36 -05:00
version = "0.1.16"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some other deps
2021-01-27 15:11:36 -05:00
checksum = "8fc3cb4d91f53b50155bdcfd23f6a4c39ae1969c2ae85982b135750cccaf5fce"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"libc",
"wasi 0.9.0+wasi-snapshot-preview1",
]
[[package]]
name = "getrandom"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.2.3"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "7fcd999463524c52659517fe2cea98493cfe485d10565e7b0fb07dbba7ad2753"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"libc",
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
"wasi 0.10.0+wasi-snapshot-preview1",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "gimli"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.25.0"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "f0a01e0497841a3b2db4f8afa483cce65f7e96a3498bd6c541734792aeac8fe7"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
[[package]]
name = "h2"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.3.4"
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "d7f3675cfef6a30c8031cf9e6493ebdc3bb3272a3fea3923c4210d1830e6a472"
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
dependencies = [
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"bytes",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"fnv",
"futures-core",
"futures-sink",
"futures-util",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"http",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"indexmap",
"slab",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"tokio",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"tokio-util",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"tracing",
update deps
2019-02-14 01:43:30 -05:00
]
schema version 6 with pixel aspect ratio This makes anamorphic sub streams display correctly, even ones from old Hikvision cameras that don't properly set the aspect ratio at the H.264 layer.
2020-03-20 00:35:42 -04:00
[[package]]
name = "h264-reader"
use released versions of a few deps
2021-06-09 17:36:14 -04:00
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c8d87669bdeca3d51902f1bf1f2c71c8f514a8f3011d9b81e63719b374091da1"
schema version 6 with pixel aspect ratio This makes anamorphic sub streams display correctly, even ones from old Hikvision cameras that don't properly set the aspect ratio at the H.264 layer.
2020-03-20 00:35:42 -04:00
dependencies = [
"bitreader",
use released versions of a few deps
2021-06-09 17:36:14 -04:00
"log",
schema version 6 with pixel aspect ratio This makes anamorphic sub streams display correctly, even ones from old Hikvision cameras that don't properly set the aspect ratio at the H.264 layer.
2020-03-20 00:35:42 -04:00
"memchr",
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
"rfc6381-codec",
schema version 6 with pixel aspect ratio This makes anamorphic sub streams display correctly, even ones from old Hikvision cameras that don't properly set the aspect ratio at the H.264 layer.
2020-03-20 00:35:42 -04:00
]
update rusqlite The big difference here is query_named and execute_named have gone away. Fair number of lines changes but straightforward.
2021-05-17 13:50:12 -04:00
[[package]]
name = "hashbrown"
version = "0.11.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ab5ef0d4909ef3724cc8cce6ccc8572c5c817592e9285f5464f8e86f8bd3726e"
dependencies = [
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
"ahash 0.7.4",
update rusqlite The big difference here is query_named and execute_named have gone away. Fair number of lines changes but straightforward.
2021-05-17 13:50:12 -04:00
]
[[package]]
name = "hashlink"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7249a3129cbc1ffccd74857f81464a323a152173cdb134e0fd81bc803b29facf"
dependencies = [
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
"hashbrown",
upgrade rusqlite, linked-hash-map/hashlink With Rust 1.48.0, I was getting panics like "attempted to leave type `linked_hash_map::Node<std::string::String, raw_statement::RawStatement>` uninitialized, which is invalid". Looks like this is due to a bug in linked-hash-map 0.5.2, fixed with 0.5.3. Along the way, I see that rusqlite no longer uses this crate; it switched to hashlink. Upgrade rusqlite and match that change for my own use (video index LRU cache). I'm still pulling in linked-hash-map via serde_yaml. I didn't even realize I was using serde_yaml, but libpasta wants it. Seems a little silly to me but that's something I might explore another day.
2020-11-22 20:37:55 -05:00
]
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
[[package]]
name = "heck"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.3.3"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "6d621efb26863f0e9924c6ac577e8275e5e6b77455db64ffa6c65c904e9e132c"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
"unicode-segmentation",
]
[[package]]
name = "hermit-abi"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.1.19"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "62b467343b94ba476dcb2500d242dadbb39557df889310ac77c5d99100aaac33"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"libc",
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
]
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
[[package]]
name = "hex"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7f24254aa9a54b5c858eaee2f5bccdb46aaf0e486a595ed5fd8f86ba55232a70"
update deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "hmac"
update libpasta deps
2021-05-17 16:02:26 -04:00
version = "0.11.0"
update deps
2019-02-14 01:43:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update libpasta deps
2021-05-17 16:02:26 -04:00
checksum = "2a2a2320eb7ec0ebe8da8f744d7812d9fc4cb4d09344ac01898dbcb6a20ae69b"
update deps
2019-02-14 01:43:30 -05:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"crypto-mac",
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
"digest",
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
]
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "http"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.2.5"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "1323096b05d41827dadeaee54c9981958c0f94e670bc94ed80037d1a7b8b186b"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"bytes",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"fnv",
"itoa",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
]
prepare v0.6.7 w/ Retina v0.3.3 This improves authentication over RTSP.
2021-10-20 17:59:33 -04:00
[[package]]
name = "http-auth"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "805afa6c41edf02ff4643e6672810974a83c2d866be06e0c377e1789084f6a7e"
dependencies = [
"base64",
"digest",
"hex",
"md-5",
"memchr",
"rand",
"sha2",
]
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "http-body"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.4.3"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "399c583b2979440c60be0821a6199eca73bc3c8dcd9d070d75ac726e2c6186e5"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"bytes",
"http",
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
"pin-project-lite",
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
]
replace resource.rs with new http-entity crate This crate is a slightly-more-polished and MIT-licensed version of resource.rs. So far it has one advantage: running the tests doesn't require RUST_TEST_THREADS=1.
2016-12-20 21:29:45 -05:00
[[package]]
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
name = "http-serve"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.3.4"
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "e3e5b6e37897dec068bfacce1a70ed7ed10582e83be73d5304b2ad7a18befb1e"
add a basic Javascript UI The Javascript is pretty amateurish I'm sure but at least it's something to iterate from. It's already much more pleasant for browsing through videos in several ways: * more responsive to load only a day at a time rather than 90+ days * much easier to see the same time segment on several cameras * more pleasant to have the videos load as a popup rather than a link that blows away your position in an enormous list * exposes the fancier .mp4 generation options: splitting at lengths other than the default, trimming to an arbitrary start and end time, including a subtitle track with timestamps. There's a slight regression in functionality: I didn't match the former top-level page which showed how much camera used of its disk allocation and the total duration of video. This is exposed in the JSON API, so it shouldn't be too hard to add back.
2017-10-22 00:54:27 -04:00
dependencies = [
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"bytes",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"flate2",
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
"futures-channel",
"futures-core",
"futures-util",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"http",
"http-body",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"httpdate",
overhaul HTTP serving and caching * use content-hashed paths for static resources (except the top-level request), with immutable Cache-Control headers. This should improve cache behavior in both directions: avoid preventable HTTP requests and cause immediate refresh when needed. I had some staleness when browsing with my phone. * set up the favicons properly while I'm at it (closes #50). I used the convenient favicons-webpack-plugin to build everything from a .svg. I've hit an error similar to lovell/sharp#1593 at least once though so I might change my mind about that part if it continues to be problematic. * use http-serve's new directory traversal code for static file serving. This removes the odd behavior where files that weren't present at server startup couldn't be served. (I wasn't comfortable switching to the content-hashed paths before doing this.) It also means the static files can be served compressed. JSON API responses were already served compressed, so this closes #25. * for a given API URL, decide if we want it to be cached or not server-side. Stop using jQuery's kludgy cache-defeating _=<timestamp> URL parameter. I might start setting etags on some of these things and could serve 304 Not Modified responses if it's genuinely unmodified.
2020-05-30 00:20:14 -04:00
"libc",
"memchr",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"mime",
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
"pin-project",
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
"smallvec",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"tokio",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
add a basic Javascript UI The Javascript is pretty amateurish I'm sure but at least it's something to iterate from. It's already much more pleasant for browsing through videos in several ways: * more responsive to load only a day at a time rather than 90+ days * much easier to see the same time segment on several cameras * more pleasant to have the videos load as a popup rather than a link that blows away your position in an enormous list * exposes the fancier .mp4 generation options: splitting at lengths other than the default, trimming to an arbitrary start and end time, including a subtitle track with timestamps. There's a slight regression in functionality: I didn't match the former top-level page which showed how much camera used of its disk allocation and the total duration of video. This is exposed in the JSON API, so it shouldn't be too hard to add back.
2017-10-22 00:54:27 -04:00
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "httparse"
cargo update
2021-08-31 15:59:39 -04:00
version = "1.5.1"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "acd94fdbe1d4ff688b67b04eee2e17bd50995534a61539e45adfefb45e5e5503"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
[[package]]
name = "httpdate"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "1.0.1"
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "6456b8a6c8f33fee7d958fcd1b60d55b11940a79e63ae87013e6d22e26034440"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "hyper"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.14.13"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "15d1cfb9e4f68655fa04c01f59edb405b6074a0f7118ea881e5026e4a1cd8593"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"bytes",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"futures-channel",
"futures-core",
"futures-util",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"h2",
"http",
"http-body",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"httparse",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"httpdate",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"itoa",
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
"pin-project-lite",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"socket2",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"tokio",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"tower-service",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"tracing",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"want",
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
]
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
[[package]]
name = "ident_case"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "b9e0384b61958566e926dc50660321d12159025e767c18e043daf26b70104c39"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "idna"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "0.2.3"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "418a0a6fab821475f634efe3ccc45c013f742efe03d853e8d3355d5cb850ecf8"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
"matches",
"unicode-bidi",
"unicode-normalization",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
]
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
[[package]]
name = "indexmap"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "1.7.0"
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "bc633605454125dec4b66843673f01c7df2b89479b32e0ed634e43a91cff62a5"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
"autocfg",
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
"hashbrown",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
]
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "instant"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.1.11"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "716d3d89f35ac6a34fd0eed635395f4c3b76fa889338a4632e5231a8684216bd"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
]
[[package]]
name = "ipnet"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "2.3.1"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "68f2d64f2edebec4ce84ad108148e67e1064789bee435edc5b60ad398714a3a9"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
fix #64 (extraneous flushes) Now each syncer has a binary heap of the times it plans to do a flush. When one of those times arrives, it rechecks if there's something to do. Seems more straightforward than rechecking each stream's first uncommitted recording, especially with the logic to retry failed flushes every minute. Also improved the info! log for each flush to see the actual recordings being flushed for better debuggability. No new tests right now. :-( They're tricky to write. One problem is that it's hard to get the timing right: a different flush has to happen after Syncer::save's database operations and before Syncer::run calls SimulatedClocks::recv_timeout with an empty channel[*], advancing the time. I've thought of a few ways of doing this: * adding a new SyncerCommand to run something, but it's messy (have to add it from the mock of one of the actions done by the save), and Box<dyn FnOnce() + 'static> not working (see rust-lang/rust#28796) makes it especially annoying. * replacing SimulatedClocks with something more like MockClocks. Lots of boilerplate. Maybe I need to find a good general-purpose Rust mock library. (mockers sounds good but I want something that works on stable Rust.) * bypassing the Syncer::run loop, instead manually running iterations from the test. Maybe the last way is the best for now. I'm likely to try it soon. [*] actually, it's calling Receiver::recv_timeout directly; Clocks::recv_timeout is dead code now? oops.
2019-01-04 14:56:15 -05:00
[[package]]
name = "itertools"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.10.1"
fix #64 (extraneous flushes) Now each syncer has a binary heap of the times it plans to do a flush. When one of those times arrives, it rechecks if there's something to do. Seems more straightforward than rechecking each stream's first uncommitted recording, especially with the logic to retry failed flushes every minute. Also improved the info! log for each flush to see the actual recordings being flushed for better debuggability. No new tests right now. :-( They're tricky to write. One problem is that it's hard to get the timing right: a different flush has to happen after Syncer::save's database operations and before Syncer::run calls SimulatedClocks::recv_timeout with an empty channel[*], advancing the time. I've thought of a few ways of doing this: * adding a new SyncerCommand to run something, but it's messy (have to add it from the mock of one of the actions done by the save), and Box<dyn FnOnce() + 'static> not working (see rust-lang/rust#28796) makes it especially annoying. * replacing SimulatedClocks with something more like MockClocks. Lots of boilerplate. Maybe I need to find a good general-purpose Rust mock library. (mockers sounds good but I want something that works on stable Rust.) * bypassing the Syncer::run loop, instead manually running iterations from the test. Maybe the last way is the best for now. I'm likely to try it soon. [*] actually, it's calling Receiver::recv_timeout directly; Clocks::recv_timeout is dead code now? oops.
2019-01-04 14:56:15 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "69ddb889f9d0d08a67338271fa9b62996bc788c7796a5c18cf057420aaed5eaf"
fix #64 (extraneous flushes) Now each syncer has a binary heap of the times it plans to do a flush. When one of those times arrives, it rechecks if there's something to do. Seems more straightforward than rechecking each stream's first uncommitted recording, especially with the logic to retry failed flushes every minute. Also improved the info! log for each flush to see the actual recordings being flushed for better debuggability. No new tests right now. :-( They're tricky to write. One problem is that it's hard to get the timing right: a different flush has to happen after Syncer::save's database operations and before Syncer::run calls SimulatedClocks::recv_timeout with an empty channel[*], advancing the time. I've thought of a few ways of doing this: * adding a new SyncerCommand to run something, but it's messy (have to add it from the mock of one of the actions done by the save), and Box<dyn FnOnce() + 'static> not working (see rust-lang/rust#28796) makes it especially annoying. * replacing SimulatedClocks with something more like MockClocks. Lots of boilerplate. Maybe I need to find a good general-purpose Rust mock library. (mockers sounds good but I want something that works on stable Rust.) * bypassing the Syncer::run loop, instead manually running iterations from the test. Maybe the last way is the best for now. I'm likely to try it soon. [*] actually, it's calling Receiver::recv_timeout directly; Clocks::recv_timeout is dead code now? oops.
2019-01-04 14:56:15 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"either",
fix #64 (extraneous flushes) Now each syncer has a binary heap of the times it plans to do a flush. When one of those times arrives, it rechecks if there's something to do. Seems more straightforward than rechecking each stream's first uncommitted recording, especially with the logic to retry failed flushes every minute. Also improved the info! log for each flush to see the actual recordings being flushed for better debuggability. No new tests right now. :-( They're tricky to write. One problem is that it's hard to get the timing right: a different flush has to happen after Syncer::save's database operations and before Syncer::run calls SimulatedClocks::recv_timeout with an empty channel[*], advancing the time. I've thought of a few ways of doing this: * adding a new SyncerCommand to run something, but it's messy (have to add it from the mock of one of the actions done by the save), and Box<dyn FnOnce() + 'static> not working (see rust-lang/rust#28796) makes it especially annoying. * replacing SimulatedClocks with something more like MockClocks. Lots of boilerplate. Maybe I need to find a good general-purpose Rust mock library. (mockers sounds good but I want something that works on stable Rust.) * bypassing the Syncer::run loop, instead manually running iterations from the test. Maybe the last way is the best for now. I'm likely to try it soon. [*] actually, it's calling Receiver::recv_timeout directly; Clocks::recv_timeout is dead code now? oops.
2019-01-04 14:56:15 -05:00
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "itoa"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.4.8"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "b71991ff56294aa922b450139ee08b3bfc70982c6b2c7562771375cf73542dd4"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
[[package]]
name = "js-sys"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.3.55"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "7cc9ffccd38c451a86bf13657df244e9c3f37493cce8e5e21e940963777acc84"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
dependencies = [
"wasm-bindgen",
]
upgrade deps, including http-serve bugfix This was including the wrong Content-Encoding: header on gzipped json responses, so Chrome wouldn't understand them at all.
2018-01-30 19:51:32 -05:00
[[package]]
name = "lazy_static"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
version = "1.4.0"
shrink mp4::Segment 128 -> 112 bytes (on 64-bit) * don't store sizes of mp4-format sample indexes; recalculate them. * keep SampleIndexIterator position as a u32 rather than a usize. This is 960 bytes for a 60-minute mp4; another small cache usage improvement.
2017-02-26 03:02:49 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
shrink mp4::Segment 128 -> 112 bytes (on 64-bit) * don't store sizes of mp4-format sample indexes; recalculate them. * keep SampleIndexIterator position as a u32 rather than a usize. This is 960 bytes for a 60-minute mp4; another small cache usage improvement.
2017-02-26 03:02:49 -05:00
replace regex use with nom This reduces the binary size noticeably on my macOS machine (#70): unstripped stripped 1 before switching to clap 11.1 MiB 6.7 MiB 2 after switching to clap 11.4 MiB 6.9 MiB 3 without regex 10.1 MiB 5.9 MiB
2020-04-18 02:02:02 -04:00
[[package]]
name = "lexical-core"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "0.7.6"
replace regex use with nom This reduces the binary size noticeably on my macOS machine (#70): unstripped stripped 1 before switching to clap 11.1 MiB 6.7 MiB 2 after switching to clap 11.4 MiB 6.9 MiB 3 without regex 10.1 MiB 5.9 MiB
2020-04-18 02:02:02 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "6607c62aa161d23d17a9072cc5da0be67cdfc89d3afb1e8d9c842bebc2525ffe"
replace regex use with nom This reduces the binary size noticeably on my macOS machine (#70): unstripped stripped 1 before switching to clap 11.1 MiB 6.7 MiB 2 after switching to clap 11.4 MiB 6.9 MiB 3 without regex 10.1 MiB 5.9 MiB
2020-04-18 02:02:02 -04:00
dependencies = [
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"arrayvec 0.5.2",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"bitflags",
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
replace regex use with nom This reduces the binary size noticeably on my macOS machine (#70): unstripped stripped 1 before switching to clap 11.1 MiB 6.7 MiB 2 after switching to clap 11.4 MiB 6.9 MiB 3 without regex 10.1 MiB 5.9 MiB
2020-04-18 02:02:02 -04:00
"ryu",
"static_assertions",
]
use nix to remove many uses of unsafe
2019-07-12 00:59:01 -04:00
[[package]]
name = "libc"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.2.103"
update deps The immediate motivation is that Cargo.lock referred to a commit version in a PR branch of my nix fork that no longer exists. (I didn't know, but it makes sense, that "git push -f" not only forcibly updates the branch to refer to a new commit but also gets rid of orphaned commits.) Use a moonfire branch that I'll keep stable until I'm ready to move on. I also updated parking_lot and rusqlite to new major versions (nothing in the interface that I care about has changed) and did a full cargo update.
2019-07-17 17:32:09 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "dd8f7255a17a627354f321ef0055d63b898c6fb27eff628af4d1b66b7331edf6"
use nix to remove many uses of unsafe
2019-07-12 00:59:01 -04:00
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "libpasta"
use released versions of a few deps
2021-06-09 17:36:14 -04:00
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cafc9e4bd8d9be7c73e85751c09d8ada2d973473d0af7423ee037bd82efebc2e"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"argon2rs",
update libpasta deps
2021-05-17 16:02:26 -04:00
"bcrypt",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"data-encoding",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"error-chain 0.12.4",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"lazy_static",
"log",
"num-traits",
"ring",
"rpassword",
"scrypt",
"serde",
"serde_mcf",
"serde_yaml",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "libsqlite3-sys"
update rusqlite The big difference here is query_named and execute_named have gone away. Fair number of lines changes but straightforward.
2021-05-17 13:50:12 -04:00
version = "0.22.2"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update rusqlite The big difference here is query_named and execute_named have gone away. Fair number of lines changes but straightforward.
2021-05-17 13:50:12 -04:00
checksum = "290b64917f8b0cb885d9de0f9959fe1f775d7fa12f1da2db9001c1c8ab60f89d"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"cc",
"pkg-config",
"vcpkg",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
]
[[package]]
name = "linked-hash-map"
upgrade some other deps
2021-01-27 15:11:36 -05:00
version = "0.5.4"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some other deps
2021-01-27 15:11:36 -05:00
checksum = "7fb9b38af92608140b86b693604b9ffcc5824240a484d1ecd4795bacb2fe88f3"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "lock_api"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.4.5"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "712a4d093c9976e24e7dbca41db895dabcbac38eb5f4045393d17a95bdfb1109"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
dependencies = [
"scopeguard",
]
upgrade deps, including http-serve bugfix This was including the wrong Content-Encoding: header on gzipped json responses, so Chrome wouldn't understand them at all.
2018-01-30 19:51:32 -05:00
[[package]]
name = "log"
upgrade some other deps
2021-01-27 15:11:36 -05:00
version = "0.4.14"
upgrade deps, including http-serve bugfix This was including the wrong Content-Encoding: header on gzipped json responses, so Chrome wouldn't understand them at all.
2018-01-30 19:51:32 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some other deps
2021-01-27 15:11:36 -05:00
checksum = "51b9bbe6c47d51fc3e1a9b945965946b4c44142ab8792c50835a980d362c2710"
upgrade deps, including http-serve bugfix This was including the wrong Content-Encoding: header on gzipped json responses, so Chrome wouldn't understand them at all.
2018-01-30 19:51:32 -05:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
upgrade deps, including http-serve bugfix This was including the wrong Content-Encoding: header on gzipped json responses, so Chrome wouldn't understand them at all.
2018-01-30 19:51:32 -05:00
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
upgrade deps, including http-serve bugfix This was including the wrong Content-Encoding: header on gzipped json responses, so Chrome wouldn't understand them at all.
2018-01-30 19:51:32 -05:00
[[package]]
name = "maplit"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
version = "1.0.2"
upgrade deps, including http-serve bugfix This was including the wrong Content-Encoding: header on gzipped json responses, so Chrome wouldn't understand them at all.
2018-01-30 19:51:32 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "3e2e65a1a2e43cfcb47a895c4c8b10d1f4a61097f9f254f183aee60cad9c651d"
upgrade deps, including http-serve bugfix This was including the wrong Content-Encoding: header on gzipped json responses, so Chrome wouldn't understand them at all.
2018-01-30 19:51:32 -05:00
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "matches"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.1.9"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "a3e378b66a060d48947b590737b30a1be76706c8dd7b8ba0f2fe3989c68a853f"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
[[package]]
name = "md-5"
version = "0.9.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7b5a279bb9607f9f53c22d496eade00d138d1bdcccd07d74650387cf94942a15"
dependencies = [
"block-buffer",
"digest",
"opaque-debug",
]
add matching time parsing and formatting routines * add a --ts subcommand to convert between numeric and human-readable representations. This is handy when directly inspecting the SQLite database or API output. * also take the human-readable form in the web interface's camera view. * to reduce confusion, when using trim=true on the web interface's camera view, trim the displayed starting and ending times as well as the actual .mp4 file links.
2017-01-13 02:09:02 -05:00
[[package]]
name = "memchr"
cargo update
2021-08-31 15:59:39 -04:00
version = "2.4.1"
add matching time parsing and formatting routines * add a --ts subcommand to convert between numeric and human-readable representations. This is handy when directly inspecting the SQLite database or API output. * also take the human-readable form in the web interface's camera view. * to reduce confusion, when using trim=true on the web interface's camera view, trim the displayed starting and ending times as well as the actual .mp4 file links.
2017-01-13 02:09:02 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "308cc39be01b73d0d18f82a0e7b2a3df85245f84af96fdddc5d202d27e47b86a"
add matching time parsing and formatting routines * add a --ts subcommand to convert between numeric and human-readable representations. This is handy when directly inspecting the SQLite database or API output. * also take the human-readable form in the web interface's camera view. * to reduce confusion, when using trim=true on the web interface's camera view, trim the displayed starting and ending times as well as the actual .mp4 file links.
2017-01-13 02:09:02 -05:00
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
[[package]]
name = "memoffset"
version = "0.6.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "59accc507f1338036a0477ef61afdae33cde60840f4dfe481319ce3ad116ddf9"
dependencies = [
"autocfg",
]
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
name = "mime"
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
version = "0.3.16"
update dependencies * The mylog update fixes a couple bad bugs. * Otherwise, just keep up with the Rust ecosystem.
2017-06-11 15:57:55 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
checksum = "2a60c7ce501c71e03a9c9c0d35b861413ae925bd979cc7a4e30d060069aaac8d"
update several dependencies I left serde alone because uuid hasn't been updated for the new version.
2017-01-27 23:58:04 -05:00
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
[[package]]
name = "minimal-lexical"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.1.3"
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "0c835948974f68e0bd58636fc6c5b1fbff7b297e3046f11b3b3c18bbac012c6d"
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
update most deps, notably including reqwest Fixes #60 The reqwest dependency is significant because the old version required an old version of openssl, complicating compilation on newer platforms. reqwest also pulled in old/duplicate versions of hyper, tokio, etc. Nice to drop a lot of that cruft. I left rusqlite and uuid alone because they had breaking changes I didn't want to mess with at the moment. Bumped the minimum Rust version to 1.30.0, as required by the new encoding_rs crate (and perhaps other things).
2018-11-20 12:32:55 -05:00
[[package]]
name = "miniz_oxide"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "0.4.4"
update most deps, notably including reqwest Fixes #60 The reqwest dependency is significant because the old version required an old version of openssl, complicating compilation on newer platforms. reqwest also pulled in old/duplicate versions of hyper, tokio, etc. Nice to drop a lot of that cruft. I left rusqlite and uuid alone because they had breaking changes I didn't want to mess with at the moment. Bumped the minimum Rust version to 1.30.0, as required by the new encoding_rs crate (and perhaps other things).
2018-11-20 12:32:55 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "a92518e98c078586bc6c934028adcca4c92a53d6a958196de835170a01d84e4b"
update most deps, notably including reqwest Fixes #60 The reqwest dependency is significant because the old version required an old version of openssl, complicating compilation on newer platforms. reqwest also pulled in old/duplicate versions of hyper, tokio, etc. Nice to drop a lot of that cruft. I left rusqlite and uuid alone because they had breaking changes I didn't want to mess with at the moment. Bumped the minimum Rust version to 1.30.0, as required by the new encoding_rs crate (and perhaps other things).
2018-11-20 12:32:55 -05:00
dependencies = [
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"adler",
"autocfg",
update most deps, notably including reqwest Fixes #60 The reqwest dependency is significant because the old version required an old version of openssl, complicating compilation on newer platforms. reqwest also pulled in old/duplicate versions of hyper, tokio, etc. Nice to drop a lot of that cruft. I left rusqlite and uuid alone because they had breaking changes I didn't want to mess with at the moment. Bumped the minimum Rust version to 1.30.0, as required by the new encoding_rs crate (and perhaps other things).
2018-11-20 12:32:55 -05:00
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
name = "mio"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.7.13"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "8c2bdb6314ec10835cd3293dd268473a835c02b7b352e788be788b3c6ca6bb16"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"libc",
"log",
"miow",
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
"ntapi",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
]
[[package]]
name = "miow"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "0.3.7"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "b9f1c5b025cda876f66ef43a113f91ebc9f4ccef34843000e0adf6ebbab84e21"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
dependencies = [
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
]
tests and fixes for Writer and Syncer * separate these out into a new file, writer.rs, as dir.rs was getting unwieldy. * extract traits for the parts of SampleFileDir and std::fs::File they needed; set up mock implementations. * move clock.rs to a new base crate to be accessible from the db crate. * add tests that exercise all the retry paths. * bugfix: account for the new recording's bytes when calculating how much to delete. * bugfix: when retrying an unlink failure in collect_garbage, we shouldn't warn about all the recordings no longer existing. Do this by retrying each step rather than the whole procedure again. * avoid double-panic scenarios, which I hit while tweaking the mocks. These are quite annoying to debug as Rust doesn't print information about either panic. I ended up using lldb to get a backtrace. Better to be cautious about what we're doing when already panicking. * give more context on raw::insert_recording errors, which I hit as well while tweaking the new tests.
2018-03-04 15:24:24 -05:00
[[package]]
name = "moonfire-base"
version = "0.0.1"
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"failure",
shutdown better After a frustrating search for a suitable channel to use for shutdown (tokio::sync::watch::Receiver and futures::future::Shared<tokio::sync::oneshot::Receiver> didn't look quite right) in which I rethought my life decisions, I finally just made my own (server/base/shutdown.rs). We can easily poll it or wait for it in async or sync contexts. Most importantly, it's convenient; not that it really matters here, but it's also efficient. We now do a slightly better job of propagating a "graceful" shutdown signal, and this channel will give us tools to improve it over time. * Shut down even when writer or syncer operations are stuck. Fixes #117 * Not done yet: streamers should instantly shut down without waiting for a connection attempt or frame or something. I'll probably implement that when removing --rtsp-library=ffmpeg. The code should be cleaner then. * Not done yet: fix a couple places that sleep for up to a second when they could shut down immediately. I just need to do the plumbing for mock clocks to work. I also implemented an immediate shutdown mode, activated by a second signal. I think this will mitigate the streamer wait situation.
2021-09-23 18:55:53 -04:00
"futures",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"lazy_static",
"libc",
"log",
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"nom 7.0.0",
upgrade some deps including parking_lot Now there's a single parking_lot version, yay.
2020-11-24 01:46:05 -05:00
"parking_lot",
refine timestamps in json signals api * API change: in update signals, allow setting a start time relative to now. This is an accuracy improvement in the case where the client has been retrying an initial request for a while. Kind of an obscure corner case but easy enough to address. And use a more convenient enum representation. * in update signals, choose `now` before acquiring the database lock. If lock acquisition takes a long time, this more accurately reflects the time the caller intended. * in general, make Time and Duration (de)serializable and use them in json types. This makes the types more self-describing, with better debug printing on both the server side and on the client library (in moonfire-playground). To make this work, base has to import serde which initially seemed like poor layering to me, but serde seems to be imported in some pretty foundational Rust crates for this reason. I'll go with it.
2021-04-21 13:44:01 -04:00
"serde",
"serde_json",
shutdown better After a frustrating search for a suitable channel to use for shutdown (tokio::sync::watch::Receiver and futures::future::Shared<tokio::sync::oneshot::Receiver> didn't look quite right) in which I rethought my life decisions, I finally just made my own (server/base/shutdown.rs). We can easily poll it or wait for it in async or sync contexts. Most importantly, it's convenient; not that it really matters here, but it's also efficient. We now do a slightly better job of propagating a "graceful" shutdown signal, and this channel will give us tools to improve it over time. * Shut down even when writer or syncer operations are stuck. Fixes #117 * Not done yet: streamers should instantly shut down without waiting for a connection attempt or frame or something. I'll probably implement that when removing --rtsp-library=ffmpeg. The code should be cleaner then. * Not done yet: fix a couple places that sleep for up to a second when they could shut down immediately. I just need to do the plumbing for mock clocks to work. I also implemented an immediate shutdown mode, activated by a second signal. I think this will mitigate the streamer wait situation.
2021-09-23 18:55:53 -04:00
"slab",
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
"time",
tests and fixes for Writer and Syncer * separate these out into a new file, writer.rs, as dir.rs was getting unwieldy. * extract traits for the parts of SampleFileDir and std::fs::File they needed; set up mock implementations. * move clock.rs to a new base crate to be accessible from the db crate. * add tests that exercise all the retry paths. * bugfix: account for the new recording's bytes when calculating how much to delete. * bugfix: when retrying an unlink failure in collect_garbage, we shouldn't warn about all the recordings no longer existing. Do this by retrying each step rather than the whole procedure again. * avoid double-panic scenarios, which I hit while tweaking the mocks. These are quite annoying to debug as Rust doesn't print information about either panic. I ended up using lldb to get a backtrace. Better to be cautious about what we're doing when already panicking. * give more context on raw::insert_recording errors, which I hit as well while tweaking the new tests.
2018-03-04 15:24:24 -05:00
]
initial split of database to a separate crate It should reduce compile time / memory usage to put quite a bit of the code into a separate crate. I also intend to limit visibility of some things to only within the db crate, but that's for a future change. This is the smallest move that will compile.
2018-02-21 02:15:39 -05:00
[[package]]
name = "moonfire-db"
prepare v0.6.7 w/ Retina v0.3.3 This improves authentication over RTSP.
2021-10-20 17:59:33 -04:00
version = "0.6.7"
initial split of database to a separate crate It should reduce compile time / memory usage to put quite a bit of the code into a separate crate. I also intend to limit visibility of some things to only within the db crate, but that's for a future change. This is the smallest move that will compile.
2018-02-21 02:15:39 -05:00
dependencies = [
upgrade some other deps
2021-01-27 15:11:36 -05:00
"base64",
use Blake3 instead of SHA-1 or Blake2b Benefits: * Blake3 is faster. This is most noticeable for the hashing of the sample file data. * we no longer need OpenSSL, which helps with shrinking the binary size (#70). sha1 basically forced OpenSSL usage; ring deliberately doesn't support this old algorithm, and the pure-Rust sha1 crate is painfully slow. OpenSSL might still be a better choice than ring/rustls for TLS but it's nice to have the option. For the video sample entries, I decided we don't need to hash at all. I think the id number is sufficiently stable, and it's okay---perhaps even desirable---if an existing init segment changes for fixes like e5b83c2.
2020-03-20 23:52:30 -04:00
"blake3",
schema version 6 with pixel aspect ratio This makes anamorphic sub streams display correctly, even ones from old Hikvision cameras that don't properly set the aspect ratio at the H.264 layer.
2020-03-20 00:35:42 -04:00
"byteorder",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"cstr",
"failure",
"fnv",
read sample files from dedicated threads Reading from the mmap()ed region in the tokio threads could cause them to stall: * That could affect UI serving when there were concurrent UI requests (i.e., not just requests that needed the reads in question anyway). * If there's a faulty disk, it could cause the UI to totally hang. Better to not mix disks between threads. * Soon, I want to handle RTSP from the tokio threads (#37). Similarly, we don't want RTSP streaming to block on operations from unrelated disks. I went with just one thread per disk which I think is sufficient. But it'd be possible to do a fixed-size pool instead which might improve latency when some pages are already cached. I also dropped the memmap dependency. I had to compute the page alignment anyway to get mremap to work, and Moonfire NVR already is Unix-specific, so there wasn't much value from the memmap or memmap2 crates. Fixes #88
2021-06-04 22:17:32 -04:00
"futures",
schema version 6 with pixel aspect ratio This makes anamorphic sub streams display correctly, even ones from old Hikvision cameras that don't properly set the aspect ratio at the H.264 layer.
2020-03-20 00:35:42 -04:00
"h264-reader",
update various other deps
2021-05-17 14:05:54 -04:00
"hashlink",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"itertools",
"lazy_static",
"libc",
"libpasta",
"log",
"moonfire-base",
"mylog",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"nix",
UI: improve aspect ratio handling As written in the changelog: Live streams formerly worked around a Firefox pixel aspect ratio bug by forcing all videos to 16:9, which dramatically distorted 9:16 camera views. Playback didn't, so anamorphic videos looked correct on Chrome but slightly stretched on Firefox. Now both live streams and playback are fully correct on all browsers.
2021-08-12 16:32:01 -04:00
"num-rational 0.4.0",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"odds",
upgrade some deps including parking_lot Now there's a single parking_lot version, yay.
2020-11-24 01:46:05 -05:00
"parking_lot",
better debugging when unable to insert VSE I saw this error once: Apr 27 21:01:33 nuc moonfire-nvr[188570]: s-reolink-sub moonfire_nvr::streamer] reolink-sub: sleeping for Duration { secs: 1, nanos: 0 } after error: CHECK constraint failed: video_sample_entry and would like to understand it better.
2021-04-28 01:51:30 -04:00
"pretty-hex",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"prettydiff",
"protobuf",
"protobuf-codegen-pure",
use Blake3 instead of SHA-1 or Blake2b Benefits: * Blake3 is faster. This is most noticeable for the hashing of the sample file data. * we no longer need OpenSSL, which helps with shrinking the binary size (#70). sha1 basically forced OpenSSL usage; ring deliberately doesn't support this old algorithm, and the pure-Rust sha1 crate is painfully slow. OpenSSL might still be a better choice than ring/rustls for TLS but it's nice to have the option. For the video sample entries, I decided we don't need to hash at all. I think the id number is sufficiently stable, and it's okay---perhaps even desirable---if an existing init segment changes for fixes like e5b83c2.
2020-03-20 23:52:30 -04:00
"ring",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"rusqlite",
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
"smallvec",
stop using old tempdir crate
2021-05-17 16:08:01 -04:00
"tempfile",
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
"time",
read sample files from dedicated threads Reading from the mmap()ed region in the tokio threads could cause them to stall: * That could affect UI serving when there were concurrent UI requests (i.e., not just requests that needed the reads in question anyway). * If there's a faulty disk, it could cause the UI to totally hang. Better to not mix disks between threads. * Soon, I want to handle RTSP from the tokio threads (#37). Similarly, we don't want RTSP streaming to block on operations from unrelated disks. I went with just one thread per disk which I think is sufficient. But it'd be possible to do a fixed-size pool instead which might improve latency when some pages are already cached. I also dropped the memmap dependency. I had to compute the page alignment anyway to get mremap to work, and Moonfire NVR already is Unix-specific, so there wasn't much value from the memmap or memmap2 crates. Fixes #88
2021-06-04 22:17:32 -04:00
"tokio",
config: validate more in cameras dialog box Fixes #152 This won't win any awards for best UI or cleanest UI code, but it's an improvement. Long-term I want the web config UI instead.
2021-08-23 18:55:47 -04:00
"url",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"uuid",
initial split of database to a separate crate It should reduce compile time / memory usage to put quite a bit of the code into a separate crate. I also intend to limit visibility of some things to only within the db crate, but that's for a future change. This is the smallest move that will compile.
2018-02-21 02:15:39 -05:00
]
use my own ffmpeg crate This significantly improves safety of the ffmpeg interface. The complex ABIs aren't accessed directly from Rust. Instead, I have a small C wrapper which uses the ffmpeg C API and the C headers at compile-time to determine the proper ABI in the same way any C program using ffmpeg would, so that the ABI doesn't have to be duplicated in Rust code. I've tested with ffmpeg 2.x and ffmpeg 3.x; it seems to work properly with both where before ffmpeg 3.x caused segfaults. It still depends on ABI compatibility between the compiled and running versions. C programs need this, too, and normal shared library versioning practices provide this guarantee. But log both versions on startup for diagnosing problems with this. Fixes #7
2017-09-21 00:06:06 -04:00
[[package]]
name = "moonfire-ffmpeg"
version = "0.0.1"
update various other deps
2021-05-17 14:05:54 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bcea35804beaed77b7b565730bcec888f5687a08408cd0986d89b94403a1cefa"
use my own ffmpeg crate This significantly improves safety of the ffmpeg interface. The complex ABIs aren't accessed directly from Rust. Instead, I have a small C wrapper which uses the ffmpeg C API and the C headers at compile-time to determine the proper ABI in the same way any C program using ffmpeg would, so that the ABI doesn't have to be duplicated in Rust code. I've tested with ffmpeg 2.x and ffmpeg 3.x; it seems to work properly with both where before ffmpeg 3.x caused segfaults. It still depends on ABI compatibility between the compiled and running versions. C programs need this, too, and normal shared library versioning practices provide this guarantee. But log both versions on startup for diagnosing problems with this. Fixes #7
2017-09-21 00:06:06 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"cc",
"libc",
"log",
upgrade some deps including parking_lot Now there's a single parking_lot version, yay.
2020-11-24 01:46:05 -05:00
"parking_lot",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"pkg-config",
use my own ffmpeg crate This significantly improves safety of the ffmpeg interface. The complex ABIs aren't accessed directly from Rust. Instead, I have a small C wrapper which uses the ffmpeg C API and the C headers at compile-time to determine the proper ABI in the same way any C program using ffmpeg would, so that the ABI doesn't have to be duplicated in Rust code. I've tested with ffmpeg 2.x and ffmpeg 3.x; it seems to work properly with both where before ffmpeg 3.x caused segfaults. It still depends on ABI compatibility between the compiled and running versions. C programs need this, too, and normal shared library versioning practices provide this guarantee. But log both versions on startup for diagnosing problems with this. Fixes #7
2017-09-21 00:06:06 -04:00
]
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
name = "moonfire-nvr"
prepare v0.6.7 w/ Retina v0.3.3 This improves authentication over RTSP.
2021-10-20 17:59:33 -04:00
version = "0.6.7"
update dependencies
2017-11-17 02:01:09 -05:00
dependencies = [
upgrade some other deps
2021-01-27 15:11:36 -05:00
"base64",
use Blake3 instead of SHA-1 or Blake2b Benefits: * Blake3 is faster. This is most noticeable for the hashing of the sample file data. * we no longer need OpenSSL, which helps with shrinking the binary size (#70). sha1 basically forced OpenSSL usage; ring deliberately doesn't support this old algorithm, and the pure-Rust sha1 crate is painfully slow. OpenSSL might still be a better choice than ring/rustls for TLS but it's nice to have the option. For the video sample entries, I decided we don't need to hash at all. I think the id number is sufficiently stable, and it's okay---perhaps even desirable---if an existing init segment changes for fixes like e5b83c2.
2020-03-20 23:52:30 -04:00
"blake3",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"byteorder",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"bytes",
tweak deps, eliminating strsim 0.8 dependency I also enabled the colored help option for clap, since we're paying for the color dep anyway.
2021-06-15 03:45:11 -04:00
"clap",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"cstr",
"cursive",
"failure",
"fnv",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"futures",
schema version 6 with pixel aspect ratio This makes anamorphic sub streams display correctly, even ones from old Hikvision cameras that don't properly set the aspect ratio at the H.264 layer.
2020-03-20 00:35:42 -04:00
"h264-reader",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"http",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"http-serve",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"hyper",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"lazy_static",
"libc",
"log",
"memchr",
"moonfire-base",
"moonfire-db",
"moonfire-ffmpeg",
"mylog",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"nix",
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"nom 7.0.0",
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
"num-rational 0.4.0",
upgrade some deps including parking_lot Now there's a single parking_lot version, yay.
2020-11-24 01:46:05 -05:00
"parking_lot",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"protobuf",
"reffers",
"reqwest",
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
"retina",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"ring",
"rusqlite",
"serde",
"serde_json",
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
"smallvec",
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"structopt",
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
"sync_wrapper",
stop using old tempdir crate
2021-05-17 16:08:01 -04:00
"tempfile",
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
"time",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"tokio",
send keepalives on live.m4s Chrome appears to time out at 60 seconds of inactivity otherwise. I think it's better to keep the stream open, even if the camera is broken. The implementation looks awkward, but that might be the state of Rust async right now.
2021-03-26 02:01:38 -04:00
"tokio-stream",
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
"tokio-tungstenite",
logging improvements * allow debug/trace logging on release builds again * enable log messages from hyper. I didn't notice they went away with 0.14.0, although there's a breaking change in the log: https://github.com/hyperium/hyper/blob/master/CHANGELOG.md#v0140-2020-12-23 * downgrade some particularly spammy messages
2021-06-05 02:28:48 -04:00
"tracing",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"url",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"uuid",
update dependencies
2017-11-17 02:01:09 -05:00
]
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
[[package]]
name = "mp4ra-rust"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "be9daf03b43bf3842962947c62ba40f411e46a58774c60838038f04a67d17626"
dependencies = [
"four-cc",
]
[[package]]
name = "mpeg4-audio-const"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "96a1fe2275b68991faded2c80aa4a33dba398b77d276038b8f50701a22e55918"
use my own logging package This supports formats that I find more useful; one that mimicks the Google glog package, and one that is similar but adapted for the systemd journal.
2017-03-26 03:01:48 -04:00
[[package]]
name = "mylog"
version = "0.1.0"
tweak color env variable options As noted in mylog's 2b1085c: Looks like both the GNU tools' --color argument and cargo's CARGO_TERM_COLOR expect always/never rather than on/off. Match that. Might as well understand off/no/false and on/yes/true also.
2021-03-12 12:24:20 -05:00
source = "git+https://github.com/scottlamb/mylog#2b1085cfb3bd0b1f2afe7d8085045d81858c0050"
use my own logging package This supports formats that I find more useful; one that mimicks the Google glog package, and one that is similar but adapted for the systemd journal.
2017-03-26 03:01:48 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"chrono",
support color coding logs (#112) ffmpeg was already doing this; now do it for native logs.
2021-03-10 01:02:00 -05:00
"libc",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"log",
upgrade some deps including parking_lot Now there's a single parking_lot version, yay.
2020-11-24 01:46:05 -05:00
"parking_lot",
use my own logging package This supports formats that I find more useful; one that mimicks the Google glog package, and one that is similar but adapted for the systemd journal.
2017-03-26 03:01:48 -04:00
]
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
[[package]]
name = "ncurses"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "5.101.0"
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "5e2c5d34d72657dc4b638a1c25d40aae81e4f1c699062f72f467237920752032"
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"cc",
"libc",
"pkg-config",
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
]
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
[[package]]
name = "nix"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.23.0"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "f305c2c2e4c39a82f7bf0bf65fb557f9070ce06781d4f2454295cc34b1c43188"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
dependencies = [
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"bitflags",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"cc",
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"libc",
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
"memoffset",
use nix to remove many uses of unsafe
2019-07-12 00:59:01 -04:00
]
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
[[package]]
name = "nodrop"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
version = "0.1.14"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "72ef4a56884ca558e5ddb05a1d1e7e1bfd9a68d9ed024c21704cc98872dae1bb"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
replace regex use with nom This reduces the binary size noticeably on my macOS machine (#70): unstripped stripped 1 before switching to clap 11.1 MiB 6.7 MiB 2 after switching to clap 11.4 MiB 6.9 MiB 3 without regex 10.1 MiB 5.9 MiB
2020-04-18 02:02:02 -04:00
[[package]]
name = "nom"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "6.1.2"
replace regex use with nom This reduces the binary size noticeably on my macOS machine (#70): unstripped stripped 1 before switching to clap 11.1 MiB 6.7 MiB 2 after switching to clap 11.4 MiB 6.9 MiB 3 without regex 10.1 MiB 5.9 MiB
2020-04-18 02:02:02 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "e7413f999671bd4745a7b624bd370a569fb6bc574b23c83a3c5ed2e453f3d5e2"
replace regex use with nom This reduces the binary size noticeably on my macOS machine (#70): unstripped stripped 1 before switching to clap 11.1 MiB 6.7 MiB 2 after switching to clap 11.4 MiB 6.9 MiB 3 without regex 10.1 MiB 5.9 MiB
2020-04-18 02:02:02 -04:00
dependencies = [
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"bitvec",
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
"funty",
replace regex use with nom This reduces the binary size noticeably on my macOS machine (#70): unstripped stripped 1 before switching to clap 11.1 MiB 6.7 MiB 2 after switching to clap 11.4 MiB 6.9 MiB 3 without regex 10.1 MiB 5.9 MiB
2020-04-18 02:02:02 -04:00
"lexical-core",
"memchr",
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
"version_check",
replace regex use with nom This reduces the binary size noticeably on my macOS machine (#70): unstripped stripped 1 before switching to clap 11.1 MiB 6.7 MiB 2 after switching to clap 11.4 MiB 6.9 MiB 3 without regex 10.1 MiB 5.9 MiB
2020-04-18 02:02:02 -04:00
]
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
[[package]]
name = "nom"
version = "7.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7ffd9d26838a953b4af82cbeb9f1592c6798916983959be223a7124e992742c1"
dependencies = [
"memchr",
"minimal-lexical",
"version_check",
]
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
[[package]]
name = "ntapi"
version = "0.3.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3f6bb902e437b6d86e03cce10a7e2af662292c5dfef23b65899ea3ac9354ad44"
dependencies = [
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "num"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.3.1"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "8b7a8e9be5e039e2ff869df49155f1c06bd01ade2117ec783e56ab0932b67a8f"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"num-complex",
"num-integer",
"num-iter",
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
"num-rational 0.3.2",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"num-traits",
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
]
[[package]]
name = "num-complex"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.3.1"
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "747d632c0c558b87dbabbe6a82f3b4ae03720d0646ac5b7b4dae89394be5f2c5"
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"num-traits",
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "num-integer"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.1.44"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "d2cc698a63b549a70bc047073d2949cce27cd1c7b0a4a862d08a8031bc2801db"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
dependencies = [
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
"autocfg",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"num-traits",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
]
[[package]]
name = "num-iter"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.1.42"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "b2021c8337a54d21aca0d59a92577a029af9431cb59b909b03252b9c164fad59"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
dependencies = [
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
"autocfg",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"num-integer",
"num-traits",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
]
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
[[package]]
name = "num-rational"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.3.2"
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "12ac428b1cb17fce6f731001d307d351ec70a6d202fc2e60f7d4c5e42d8f4f07"
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
dependencies = [
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
"autocfg",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"num-integer",
"num-traits",
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
]
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
[[package]]
name = "num-rational"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d41702bd167c2df5520b384281bc111a4b5efcf7fbc4c9c222c815b07e0a6a6a"
dependencies = [
"autocfg",
"num-integer",
"num-traits",
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "num-traits"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.2.14"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "9a64b1ec5cda2586e284722486d802acf1f7dbdc623e2bfc57e65ca1cd099290"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
dependencies = [
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
"autocfg",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "num_cpus"
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
version = "1.13.0"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
checksum = "05499f3756671c15885fee9034446956fff3f243d6077b91e5767df161f766b3"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"hermit-abi",
"libc",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "object"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.26.2"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "39f37e50073ccad23b6d09bcb5b263f4e76d3bb6038e4a3c08e52162ffa8abc2"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
dependencies = [
"memchr",
]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
backend support for live stream (#59) This is so far completely untested, for use by a new UI prototype. It creates a new URL endpoint which sends one video/mp4 media segment per key frame, with the dependent frames included. This means there will be about one key frame interval of latency (typically about a second). This seems hard to avoid, as mentioned in issue #59.
2019-01-21 18:58:52 -05:00
[[package]]
name = "odds"
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
version = "0.4.0"
backend support for live stream (#59) This is so far completely untested, for use by a new UI prototype. It creates a new URL endpoint which sends one video/mp4 media segment per key frame, with the dependent frames included. This means there will be about one key frame interval of latency (typically about a second). This seems hard to avoid, as mentioned in issue #59.
2019-01-21 18:58:52 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
checksum = "bfe9f693ec5bf79b8867b34aeaa5a2500e3a90461b486b573bcad3cca42b4d9e"
backend support for live stream (#59) This is so far completely untested, for use by a new UI prototype. It creates a new URL endpoint which sends one video/mp4 media segment per key frame, with the dependent frames included. This means there will be about one key frame interval of latency (typically about a second). This seems hard to avoid, as mentioned in issue #59.
2019-01-21 18:58:52 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"rawpointer",
"rawslice",
"unchecked-index",
backend support for live stream (#59) This is so far completely untested, for use by a new UI prototype. It creates a new URL endpoint which sends one video/mp4 media segment per key frame, with the dependent frames included. This means there will be about one key frame interval of latency (typically about a second). This seems hard to avoid, as mentioned in issue #59.
2019-01-21 18:58:52 -05:00
]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "once_cell"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "1.8.0"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "692fcb63b64b1758029e0a96ee63e049ce8c5948587f2f7208df04625e5f6b56"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "opaque-debug"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "624a8340c38c1b80fd549087862da4ba43e08858af025b236e509b6649fc13d5"
update most deps, notably including reqwest Fixes #60 The reqwest dependency is significant because the old version required an old version of openssl, complicating compilation on newer platforms. reqwest also pulled in old/duplicate versions of hyper, tokio, etc. Nice to drop a lot of that cruft. I left rusqlite and uuid alone because they had breaking changes I didn't want to mess with at the moment. Bumped the minimum Rust version to 1.30.0, as required by the new encoding_rs crate (and perhaps other things).
2018-11-20 12:32:55 -05:00
[[package]]
name = "owning_ref"
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
version = "0.4.1"
update most deps, notably including reqwest Fixes #60 The reqwest dependency is significant because the old version required an old version of openssl, complicating compilation on newer platforms. reqwest also pulled in old/duplicate versions of hyper, tokio, etc. Nice to drop a lot of that cruft. I left rusqlite and uuid alone because they had breaking changes I didn't want to mess with at the moment. Bumped the minimum Rust version to 1.30.0, as required by the new encoding_rs crate (and perhaps other things).
2018-11-20 12:32:55 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
checksum = "6ff55baddef9e4ad00f88b6c743a2a8062d4c6ade126c2a528644b8e444d52ce"
update most deps, notably including reqwest Fixes #60 The reqwest dependency is significant because the old version required an old version of openssl, complicating compilation on newer platforms. reqwest also pulled in old/duplicate versions of hyper, tokio, etc. Nice to drop a lot of that cruft. I left rusqlite and uuid alone because they had breaking changes I didn't want to mess with at the moment. Bumped the minimum Rust version to 1.30.0, as required by the new encoding_rs crate (and perhaps other things).
2018-11-20 12:32:55 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"stable_deref_trait",
update all Rust deps
2018-12-01 18:20:19 -05:00
]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "parking_lot"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.11.2"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "7d17b78036a60663b797adeaee46f5c9dfebb86948d1255007a1d6be0271ff99"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
dependencies = [
"instant",
upgrade some deps including parking_lot Now there's a single parking_lot version, yay.
2020-11-24 01:46:05 -05:00
"lock_api",
"parking_lot_core",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
]
[[package]]
name = "parking_lot_core"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.8.5"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "d76e8e1493bcac0d2766c42737f34458f1c8c50c0d23bcb24ea953affb273216"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"instant",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"libc",
cargo update
2021-08-31 15:59:39 -04:00
"redox_syscall 0.2.10",
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
"smallvec",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
update all Rust deps
2018-12-01 18:20:19 -05:00
]
update libpasta deps
2021-05-17 16:02:26 -04:00
[[package]]
name = "password-hash"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.2.3"
update libpasta deps
2021-05-17 16:02:26 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "77e0b28ace46c5a396546bcf443bf422b57049617433d8854227352a4a9b24e7"
update libpasta deps
2021-05-17 16:02:26 -04:00
dependencies = [
"base64ct",
stop using old tempdir crate
2021-05-17 16:08:01 -04:00
"rand_core",
update libpasta deps
2021-05-17 16:02:26 -04:00
"subtle",
]
update all Rust deps
2018-12-01 18:20:19 -05:00
[[package]]
update deps
2019-02-14 01:43:30 -05:00
name = "pbkdf2"
update libpasta deps
2021-05-17 16:02:26 -04:00
version = "0.8.0"
update all Rust deps
2018-12-01 18:20:19 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update libpasta deps
2021-05-17 16:02:26 -04:00
checksum = "d95f5254224e617595d2cc3cc73ff0a5eaf2637519e25f03388154e9378b6ffa"
update all Rust deps
2018-12-01 18:20:19 -05:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"crypto-mac",
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
]
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
name = "percent-encoding"
version = "2.1.0"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "d4fd5641d01c8f18a23da7b6fe29298ff4b55afcccdf78973b24cf3175fee32e"
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
name = "pin-project"
cargo update
2021-08-31 15:59:39 -04:00
version = "1.0.8"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "576bc800220cc65dac09e99e97b08b358cfab6e17078de8dc5fee223bd2d0c08"
update dependencies
2017-11-17 02:01:09 -05:00
dependencies = [
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
"pin-project-internal",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
]
[[package]]
name = "pin-project-internal"
cargo update
2021-08-31 15:59:39 -04:00
version = "1.0.8"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "6e8fe8163d14ce7f0cdac2e040116f22eac817edabff0be91e8aff7e9accf389"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
dependencies = [
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
"syn",
update dependencies
2017-11-17 02:01:09 -05:00
]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "pin-project-lite"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.2.7"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "8d31d11c69a6b52a174b42bdc0c30e5e11670f90788b2c471c31c1d17d449443"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "pin-utils"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.1.0"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "8b870d8c151b6f2fb93e84a13146138f05d02ed11c7e7c54f8826aaaf7c9f184"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "pkg-config"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.3.20"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "7c9b1041b4387893b91ee6746cddfc28516aff326a3519fb2adf820932c5e6cb"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
update deps The immediate motivation is that Cargo.lock referred to a commit version in a PR branch of my nix fork that no longer exists. (I didn't know, but it makes sense, that "git push -f" not only forcibly updates the branch to refer to a new commit but also gets rid of orphaned commits.) Use a moonfire branch that I'll keep stable until I'm ready to move on. I also updated parking_lot and rusqlite to new major versions (nothing in the interface that I care about has changed) and did a full cargo update.
2019-07-17 17:32:09 -04:00
[[package]]
name = "ppv-lite86"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.2.10"
update deps The immediate motivation is that Cargo.lock referred to a commit version in a PR branch of my nix fork that no longer exists. (I didn't know, but it makes sense, that "git push -f" not only forcibly updates the branch to refer to a new commit but also gets rid of orphaned commits.) Use a moonfire branch that I'll keep stable until I'm ready to move on. I also updated parking_lot and rusqlite to new major versions (nothing in the interface that I care about has changed) and did a full cargo update.
2019-07-17 17:32:09 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "ac74c624d6b2d21f425f752262f42188365d7b8ff1aff74c82e45136510a4857"
update deps The immediate motivation is that Cargo.lock referred to a commit version in a PR branch of my nix fork that no longer exists. (I didn't know, but it makes sense, that "git push -f" not only forcibly updates the branch to refer to a new commit but also gets rid of orphaned commits.) Use a moonfire branch that I'll keep stable until I'm ready to move on. I also updated parking_lot and rusqlite to new major versions (nothing in the interface that I care about has changed) and did a full cargo update.
2019-07-17 17:32:09 -04:00
better debugging when unable to insert VSE I saw this error once: Apr 27 21:01:33 nuc moonfire-nvr[188570]: s-reolink-sub moonfire_nvr::streamer] reolink-sub: sleeping for Duration { secs: 1, nanos: 0 } after error: CHECK constraint failed: video_sample_entry and would like to understand it better.
2021-04-28 01:51:30 -04:00
[[package]]
name = "pretty-hex"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bc5c99d529f0d30937f6f4b8a86d988047327bb88d04d2c4afc356de74722131"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
[[package]]
name = "prettydiff"
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
version = "0.5.0"
tweak deps, eliminating strsim 0.8 dependency I also enabled the colored help option for clap, since we're paying for the color dep anyway.
2021-06-15 03:45:11 -04:00
source = "git+https://github.com/scottlamb/prettydiff?branch=pr-update-deps#66d484720e1f3c32dd3cb1806cf489b832ddd9d2"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
dependencies = [
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"ansi_term",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"prettytable-rs",
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"structopt",
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
]
[[package]]
name = "prettytable-rs"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "0fd04b170004fa2daccf418a7f8253aaf033c27760b5f225889024cf66d7ac2e"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"atty",
"csv",
"encode_unicode",
"lazy_static",
"term",
"unicode-width",
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
]
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
[[package]]
name = "proc-macro-error"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "1.0.4"
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "da25490ff9892aab3fcf7c36f08cfb902dd3e71ca0f9f9517bea02a73a5ce38c"
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
dependencies = [
"proc-macro-error-attr",
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
"syn",
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
"version_check",
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
]
[[package]]
name = "proc-macro-error-attr"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "1.0.4"
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "a1be40180e52ecc98ad80b184934baf3d0d29f979574e439af5a55274b35f869"
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
dependencies = [
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
"version_check",
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
]
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "proc-macro-hack"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.5.19"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "dbf0c48bc1d91375ae5c3cd81e3722dff1abcf81a30960240640d223f59fe0e5"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "proc-macro-nested"
upgrade some other deps
2021-01-27 15:11:36 -05:00
version = "0.1.7"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some other deps
2021-01-27 15:11:36 -05:00
checksum = "bc881b2c22681370c6a780e47af9840ef841837bc98118431d4e1868bd0c1086"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "proc-macro2"
cargo update
2021-08-31 15:59:39 -04:00
version = "1.0.29"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "b9f5105d4fdaab20335ca9565e106a5d9b82b6219b5ba735731124ac6711d23d"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
dependencies = [
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"unicode-xid",
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
]
new database/sample file dir interlock scheme The idea is to avoid the problems described in src/schema.proto; those possibilities have bothered me for a while. A bonus is that (in a future commit) it can replace the sample file uuid scheme in favor of using <camera_uuid>-<stream_type>/<recording_id> for several advantages: * on data integrity problems (specifically, extra sample files), more information to use to understand what happened. * no more reserving sample files prior to using them. This avoids some extra database transactions on startup (now there's an extra two total rather than an extra one per stream). It also simplifies an upcoming change I want to make in which some streams are not flushed immediately, reducing the write load significantly (maybe one per minute total rather than one per stream per minute). * get rid of eight bytes per playback cache entry in RAM (and nine bytes per recording_playback row on flash). The implementation is still pretty rough in places: * Lack of tests. * Poor ode organization. In particular, SampleFileDirectory::write_meta shouldn't be exposed beyond db. I'm thinking about moving db.rs and SampleFileDirectory to a new crate, moonfire_nvr_db. This would improve compile times as well. * No tooling for renaming a sample file directory. * Config subcommand still panics in conditions that can be reasonably expected to happen.
2018-02-15 02:10:10 -05:00
[[package]]
name = "protobuf"
add concept of user/session permissions (I also considered the names "capabilities" and "scopes", but I think "permissions" is the most widely understood.) This is increasingly necessary as the web API becomes more capable. Among other things, it allows: * non-administrator users who can view but not access camera passwords or change any state * workers that update signal state based on cameras' built-in motion detection or a security system's events but don't need to view videos * control over what can be done without authenticating Currently session permissions are just copied from user permissions, but you can also imagine admin sessions vs not, as a checkbox when signing in. This would match the standard Unix workflow of using a non-administrative session most of the time. Relevant to my current signals work (#28) and to the addition of an administrative API (#35, including #66).
2019-06-19 18:17:50 -04:00
version = "3.0.0-pre"
cargo update
2021-08-31 15:59:39 -04:00
source = "git+https://github.com/stepancheg/rust-protobuf#b3fe22932968995779e4046189becdf7be82ba1d"
add concept of user/session permissions (I also considered the names "capabilities" and "scopes", but I think "permissions" is the most widely understood.) This is increasingly necessary as the web API becomes more capable. Among other things, it allows: * non-administrator users who can view but not access camera passwords or change any state * workers that update signal state based on cameras' built-in motion detection or a security system's events but don't need to view videos * control over what can be done without authenticating Currently session permissions are just copied from user permissions, but you can also imagine admin sessions vs not, as a checkbox when signing in. This would match the standard Unix workflow of using a non-administrative session most of the time. Relevant to my current signals work (#28) and to the addition of an administrative API (#35, including #66).
2019-06-19 18:17:50 -04:00
[[package]]
name = "protobuf-codegen"
version = "3.0.0-pre"
cargo update
2021-08-31 15:59:39 -04:00
source = "git+https://github.com/stepancheg/rust-protobuf#b3fe22932968995779e4046189becdf7be82ba1d"
add concept of user/session permissions (I also considered the names "capabilities" and "scopes", but I think "permissions" is the most widely understood.) This is increasingly necessary as the web API becomes more capable. Among other things, it allows: * non-administrator users who can view but not access camera passwords or change any state * workers that update signal state based on cameras' built-in motion detection or a security system's events but don't need to view videos * control over what can be done without authenticating Currently session permissions are just copied from user permissions, but you can also imagine admin sessions vs not, as a checkbox when signing in. This would match the standard Unix workflow of using a non-administrative session most of the time. Relevant to my current signals work (#28) and to the addition of an administrative API (#35, including #66).
2019-06-19 18:17:50 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"protobuf",
add concept of user/session permissions (I also considered the names "capabilities" and "scopes", but I think "permissions" is the most widely understood.) This is increasingly necessary as the web API becomes more capable. Among other things, it allows: * non-administrator users who can view but not access camera passwords or change any state * workers that update signal state based on cameras' built-in motion detection or a security system's events but don't need to view videos * control over what can be done without authenticating Currently session permissions are just copied from user permissions, but you can also imagine admin sessions vs not, as a checkbox when signing in. This would match the standard Unix workflow of using a non-administrative session most of the time. Relevant to my current signals work (#28) and to the addition of an administrative API (#35, including #66).
2019-06-19 18:17:50 -04:00
]
[[package]]
name = "protobuf-codegen-pure"
version = "3.0.0-pre"
cargo update
2021-08-31 15:59:39 -04:00
source = "git+https://github.com/stepancheg/rust-protobuf#b3fe22932968995779e4046189becdf7be82ba1d"
add concept of user/session permissions (I also considered the names "capabilities" and "scopes", but I think "permissions" is the most widely understood.) This is increasingly necessary as the web API becomes more capable. Among other things, it allows: * non-administrator users who can view but not access camera passwords or change any state * workers that update signal state based on cameras' built-in motion detection or a security system's events but don't need to view videos * control over what can be done without authenticating Currently session permissions are just copied from user permissions, but you can also imagine admin sessions vs not, as a checkbox when signing in. This would match the standard Unix workflow of using a non-administrative session most of the time. Relevant to my current signals work (#28) and to the addition of an administrative API (#35, including #66).
2019-06-19 18:17:50 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"protobuf",
"protobuf-codegen",
add concept of user/session permissions (I also considered the names "capabilities" and "scopes", but I think "permissions" is the most widely understood.) This is increasingly necessary as the web API becomes more capable. Among other things, it allows: * non-administrator users who can view but not access camera passwords or change any state * workers that update signal state based on cameras' built-in motion detection or a security system's events but don't need to view videos * control over what can be done without authenticating Currently session permissions are just copied from user permissions, but you can also imagine admin sessions vs not, as a checkbox when signing in. This would match the standard Unix workflow of using a non-administrative session most of the time. Relevant to my current signals work (#28) and to the addition of an administrative API (#35, including #66).
2019-06-19 18:17:50 -04:00
]
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "quote"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "1.0.9"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "c3d0b9745dc2debf507c8422de05d7226cc1f0644216dfdfead988f9b1ab32a7"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
upgrade a few deps
2018-08-25 01:06:14 -04:00
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "radium"
version = "0.5.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "941ba9d78d8e2f7ce474c015eea4d9c6d25b6a3327f9832ee29a4de27f91bbb8"
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
[[package]]
name = "rand"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.8.4"
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "2e7573632e6454cf6b99d7aac4ccca54be06da05aca2ef7423d22d27d4d4bcd8"
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
dependencies = [
"libc",
update libpasta deps
2021-05-17 16:02:26 -04:00
"rand_chacha",
stop using old tempdir crate
2021-05-17 16:08:01 -04:00
"rand_core",
update libpasta deps
2021-05-17 16:02:26 -04:00
"rand_hc",
update deps The immediate motivation is that Cargo.lock referred to a commit version in a PR branch of my nix fork that no longer exists. (I didn't know, but it makes sense, that "git push -f" not only forcibly updates the branch to refer to a new commit but also gets rid of orphaned commits.) Use a moonfire branch that I'll keep stable until I'm ready to move on. I also updated parking_lot and rusqlite to new major versions (nothing in the interface that I care about has changed) and did a full cargo update.
2019-07-17 17:32:09 -04:00
]
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
[[package]]
name = "rand_chacha"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.3.1"
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "e6c10a63a0fa32252be49d21e7709d4d4baf8d231c2dbce1eaa8141b9b127d88"
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
dependencies = [
"ppv-lite86",
stop using old tempdir crate
2021-05-17 16:08:01 -04:00
"rand_core",
update most deps, notably including reqwest Fixes #60 The reqwest dependency is significant because the old version required an old version of openssl, complicating compilation on newer platforms. reqwest also pulled in old/duplicate versions of hyper, tokio, etc. Nice to drop a lot of that cruft. I left rusqlite and uuid alone because they had breaking changes I didn't want to mess with at the moment. Bumped the minimum Rust version to 1.30.0, as required by the new encoding_rs crate (and perhaps other things).
2018-11-20 12:32:55 -05:00
]
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
[[package]]
name = "rand_core"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.6.3"
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "d34f1408f55294453790c48b2f1ebbb1c5b4b7563eb1f418bcfcfdbb06ebb4e7"
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
dependencies = [
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
"getrandom 0.2.3",
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
]
[[package]]
name = "rand_hc"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.3.1"
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "d51e9f596de227fda2ea6c84607f5558e196eeaf43c986b724ba4fb8fdf497e7"
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
dependencies = [
stop using old tempdir crate
2021-05-17 16:08:01 -04:00
"rand_core",
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
]
backend support for live stream (#59) This is so far completely untested, for use by a new UI prototype. It creates a new URL endpoint which sends one video/mp4 media segment per key frame, with the dependent frames included. This means there will be about one key frame interval of latency (typically about a second). This seems hard to avoid, as mentioned in issue #59.
2019-01-21 18:58:52 -05:00
[[package]]
name = "rawpointer"
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
version = "0.2.1"
backend support for live stream (#59) This is so far completely untested, for use by a new UI prototype. It creates a new URL endpoint which sends one video/mp4 media segment per key frame, with the dependent frames included. This means there will be about one key frame interval of latency (typically about a second). This seems hard to avoid, as mentioned in issue #59.
2019-01-21 18:58:52 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
checksum = "60a357793950651c4ed0f3f52338f53b2f809f32d83a07f72909fa13e4c6c1e3"
backend support for live stream (#59) This is so far completely untested, for use by a new UI prototype. It creates a new URL endpoint which sends one video/mp4 media segment per key frame, with the dependent frames included. This means there will be about one key frame interval of latency (typically about a second). This seems hard to avoid, as mentioned in issue #59.
2019-01-21 18:58:52 -05:00
[[package]]
name = "rawslice"
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
version = "0.1.1"
backend support for live stream (#59) This is so far completely untested, for use by a new UI prototype. It creates a new URL endpoint which sends one video/mp4 media segment per key frame, with the dependent frames included. This means there will be about one key frame interval of latency (typically about a second). This seems hard to avoid, as mentioned in issue #59.
2019-01-21 18:58:52 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
checksum = "8e23c908b26a742e5e3768ea42f19225ef809d3c9e3071bfe3e01c7e9b6fd1cd"
backend support for live stream (#59) This is so far completely untested, for use by a new UI prototype. It creates a new URL endpoint which sends one video/mp4 media segment per key frame, with the dependent frames included. This means there will be about one key frame interval of latency (typically about a second). This seems hard to avoid, as mentioned in issue #59.
2019-01-21 18:58:52 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"rawpointer",
backend support for live stream (#59) This is so far completely untested, for use by a new UI prototype. It creates a new URL endpoint which sends one video/mp4 media segment per key frame, with the dependent frames included. This means there will be about one key frame interval of latency (typically about a second). This seems hard to avoid, as mentioned in issue #59.
2019-01-21 18:58:52 -05:00
]
update several dependencies I left serde alone because uuid hasn't been updated for the new version.
2017-01-27 23:58:04 -05:00
[[package]]
name = "redox_syscall"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.1.57"
update several dependencies I left serde alone because uuid hasn't been updated for the new version.
2017-01-27 23:58:04 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "41cc0f7e4d5d4544e8861606a285bb08d3e70712ccc7d2b84d7c0ccfaf4b05ce"
update several dependencies I left serde alone because uuid hasn't been updated for the new version.
2017-01-27 23:58:04 -05:00
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
[[package]]
name = "redox_syscall"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.2.10"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "8383f39639269cde97d255a32bdb68c047337295414940c68bdd30c2e13203ff"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
dependencies = [
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"bitflags",
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
]
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
[[package]]
name = "redox_users"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.3.5"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "de0737333e7a9502c789a36d7c7fa6092a49895d4faa31ca5df163857ded2e9d"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
dependencies = [
upgrade some other deps
2021-01-27 15:11:36 -05:00
"getrandom 0.1.16",
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
"redox_syscall 0.1.57",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"rust-argon2",
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
]
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
[[package]]
name = "reffers"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.6.1"
add matching time parsing and formatting routines * add a --ts subcommand to convert between numeric and human-readable representations. This is handy when directly inspecting the SQLite database or API output. * also take the human-readable form in the web interface's camera view. * to reduce confusion, when using trim=true on the web interface's camera view, trim the displayed starting and ending times as well as the actual .mp4 file links.
2017-01-13 02:09:02 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "ae9bd363e8ee03bcc91e287ec7f0f29909dde6a99775c65b2e34c66de5a6356d"
add matching time parsing and formatting routines * add a --ts subcommand to convert between numeric and human-readable representations. This is handy when directly inspecting the SQLite database or API output. * also take the human-readable form in the web interface's camera view. * to reduce confusion, when using trim=true on the web interface's camera view, trim the displayed starting and ending times as well as the actual .mp4 file links.
2017-01-13 02:09:02 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"stable_deref_trait",
add matching time parsing and formatting routines * add a --ts subcommand to convert between numeric and human-readable representations. This is handy when directly inspecting the SQLite database or API output. * also take the human-readable form in the web interface's camera view. * to reduce confusion, when using trim=true on the web interface's camera view, trim the displayed starting and ending times as well as the actual .mp4 file links.
2017-01-13 02:09:02 -05:00
]
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
[[package]]
name = "regex-automata"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.1.10"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "6c230d73fb8d8c1b9c0b3135c5142a8acee3a0558fb8db5cf1cb65f8d7862132"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
upgrade deps
2018-01-31 01:05:39 -05:00
[[package]]
name = "remove_dir_all"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.5.3"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "3acd125665422973a33ac9d3dd2df85edad0f4ae9b00dafb1a05e43a9f5ef8e7"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
dependencies = [
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
]
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
[[package]]
name = "reqwest"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.11.4"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "246e9f61b9bb77df069a947682be06e31ac43ea37862e244a69f177694ea6d22"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
upgrade some other deps
2021-01-27 15:11:36 -05:00
"base64",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"bytes",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"encoding_rs",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"futures-core",
"futures-util",
"http",
"http-body",
"hyper",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"ipnet",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"js-sys",
"lazy_static",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"log",
"mime",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"percent-encoding",
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
"pin-project-lite",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"serde",
"serde_json",
"serde_urlencoded",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"tokio",
"url",
"wasm-bindgen",
"wasm-bindgen-futures",
"web-sys",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"winreg",
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
]
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
[[package]]
name = "retina"
prepare v0.6.7 w/ Retina v0.3.3 This improves authentication over RTSP.
2021-10-20 17:59:33 -04:00
version = "0.3.3"
use retina v0.2.0
2021-08-20 19:52:58 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
prepare v0.6.7 w/ Retina v0.3.3 This improves authentication over RTSP.
2021-10-20 17:59:33 -04:00
checksum = "99806071cb433bda0abe688798940f64ea8412482c4049e27b924e4d78675c9a"
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
dependencies = [
"base64",
"bitreader",
"bytes",
"futures",
"h264-reader",
"hex",
prepare v0.6.7 w/ Retina v0.3.3 This improves authentication over RTSP.
2021-10-20 17:59:33 -04:00
"http-auth",
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
"log",
"once_cell",
"pin-project",
"pretty-hex",
support udp with retina or ffmpeg
2021-08-31 11:10:50 -04:00
"rand",
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
"rtp-rs",
"rtsp-types",
handle stale RTSP sessions * upgrade to Retina 0.3.1 which automatically tears down sessions * wait out stale sessions before reconnecting * wait for teardown to complete before shutting down This adds some pressure on #117: it will keep waiting for the stale session to expire even if the user has requested shutdown. I'll try to address that next.
2021-09-10 00:14:01 -04:00
"sdp-types",
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
"smallvec",
upgrade to retina v0.0.5 While I'm here, return a clean error if a non-initial video frame includes a parameter change, rather than doing something crazy (#42). It's still broken under ffmpeg, it's untested, and it's not as clean as seamlessly starting a new recording with the new parameters, but it's better than nothing.
2021-07-08 19:06:30 -04:00
"thiserror",
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
"time",
"tokio",
"tokio-util",
"url",
]
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
[[package]]
name = "rfc6381-codec"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4395f46a67f0d57c57f6a5361f3a9a0c0183a19cab3998892ecdc003de6d8037"
dependencies = [
"four-cc",
"mp4ra-rust",
"mpeg4-audio-const",
]
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "ring"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "0.16.20"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "3053cf52e236a3ed746dfc745aa9cacf1b791d846bdaf412f60a8d7d6e17c8fc"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"cc",
"libc",
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
"once_cell",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"spin",
"untrusted",
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
"web-sys",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
]
[[package]]
name = "rpassword"
upgrade some other deps
2021-01-27 15:11:36 -05:00
version = "5.0.1"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some other deps
2021-01-27 15:11:36 -05:00
checksum = "ffc936cf8a7ea60c58f030fd36a612a48f440610214dc54bc36431f9ea0c3efb"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"libc",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
]
[[package]]
name = "rtp-rs"
upgrade to retina 0.0.3 The new version is more efficient.
2021-06-28 17:25:02 -04:00
version = "0.6.0"
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to retina 0.0.3 The new version is more efficient.
2021-06-28 17:25:02 -04:00
checksum = "d4ed274a5b3d36c4434cff6a4de1b42f43e64ae326b1cfa72d13d9037a314355"
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
[[package]]
name = "rtsp-types"
version = "0.0.2"
use released versions of a few deps
2021-06-09 17:36:14 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "90e677628cb208d61181b19f9b0b01efd7fce158bfba1bcb6e57e00fda291d6d"
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
dependencies = [
"cookie-factory",
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"nom 6.1.2",
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
"tinyvec",
"url",
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "rusqlite"
update rusqlite The big difference here is query_named and execute_named have gone away. Fair number of lines changes but straightforward.
2021-05-17 13:50:12 -04:00
version = "0.25.3"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update rusqlite The big difference here is query_named and execute_named have gone away. Fair number of lines changes but straightforward.
2021-05-17 13:50:12 -04:00
checksum = "57adcf67c8faaf96f3248c2a7b419a0dbc52ebe36ba83dd57fe83827c1ea4eb3"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"bitflags",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"fallible-iterator",
"fallible-streaming-iterator",
update various other deps
2021-05-17 14:05:54 -04:00
"hashlink",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"libsqlite3-sys",
"memchr",
upgrade rusqlite, linked-hash-map/hashlink With Rust 1.48.0, I was getting panics like "attempted to leave type `linked_hash_map::Node<std::string::String, raw_statement::RawStatement>` uninitialized, which is invalid". Looks like this is due to a bug in linked-hash-map 0.5.2, fixed with 0.5.3. Along the way, I see that rusqlite no longer uses this crate; it switched to hashlink. Upgrade rusqlite and match that change for my own use (video index LRU cache). I'm still pulling in linked-hash-map via serde_yaml. I didn't even realize I was using serde_yaml, but libpasta wants it. Seems a little silly to me but that's something I might explore another day.
2020-11-22 20:37:55 -05:00
"smallvec",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
]
[[package]]
name = "rust-argon2"
upgrade some other deps
2021-01-27 15:11:36 -05:00
version = "0.8.3"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some other deps
2021-01-27 15:11:36 -05:00
checksum = "4b18820d944b33caa75a71378964ac46f58517c92b6ae5f762636247c09e78fb"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
dependencies = [
upgrade some other deps
2021-01-27 15:11:36 -05:00
"base64",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"blake2b_simd",
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
"constant_time_eq",
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
"crossbeam-utils",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
]
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
[[package]]
name = "rustc-demangle"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.1.21"
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "7ef03e0a2b150c7a90d01faf6254c9c48a41e95fb2a8c2ac1c6f0d2b9aefc342"
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
[[package]]
name = "ryu"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "1.0.5"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "71d301d4193d031abdd79ff7e3dd721168a9572ef3fe51a1517aba235bd8f86e"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
[[package]]
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
name = "salsa20"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.8.1"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "ecbd2eb639fd7cab5804a0837fe373cc2172d15437e804c054a9fb885cb923b0"
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
dependencies = [
update libpasta deps
2021-05-17 16:02:26 -04:00
"cipher 0.3.0",
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
]
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "scoped_threadpool"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "1d51f5df5af43ab3f1360b429fa5e0152ac5ce8c0bd6485cae490332e96846a8"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
[[package]]
name = "scopeguard"
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
version = "1.1.0"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade deps Both a "cargo update" and a bump of major versions of a few deps. I left a few alone: * base64 because some of the deps depend on 0.11 (and 0.9), so I don't want to pull in a third version (0.12). * ring because libpasta depends on this version and I don't want to pull in two of them. * time because it's not trivial. Last I checked, time 0.2 couldn't even do what I wanted at all. I also made tokio use parking_lot, since I pull it in anyway.
2020-04-18 18:44:35 -04:00
checksum = "d29ab0c6d3fc0ee92fe66e2d99f700eab17a8d57d1c1d3b748380fb20baa78cd"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
update deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "scrypt"
update libpasta deps
2021-05-17 16:02:26 -04:00
version = "0.7.0"
update deps
2019-02-14 01:43:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update libpasta deps
2021-05-17 16:02:26 -04:00
checksum = "879588d8f90906e73302547e20fffefdd240eb3e0e744e142321f5d49dea0518"
update deps
2019-02-14 01:43:30 -05:00
dependencies = [
update libpasta deps
2021-05-17 16:02:26 -04:00
"base64ct",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"hmac",
update libpasta deps
2021-05-17 16:02:26 -04:00
"password-hash",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"pbkdf2",
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
"salsa20",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"sha2",
update deps
2019-02-14 01:43:30 -05:00
]
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
[[package]]
handle stale RTSP sessions * upgrade to Retina 0.3.1 which automatically tears down sessions * wait out stale sessions before reconnecting * wait for teardown to complete before shutting down This adds some pressure on #117: it will keep waiting for the stale session to expire even if the user has requested shutdown. I'll try to address that next.
2021-09-10 00:14:01 -04:00
name = "sdp-types"
version = "0.1.3"
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
handle stale RTSP sessions * upgrade to Retina 0.3.1 which automatically tears down sessions * wait out stale sessions before reconnecting * wait for teardown to complete before shutting down This adds some pressure on #117: it will keep waiting for the stale session to expire even if the user has requested shutdown. I'll try to address that next.
2021-09-10 00:14:01 -04:00
checksum = "ae499f6886cff026ebd8355c8f67a1881cd15f23ce89de4aab13588cf52142dd"
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
dependencies = [
handle stale RTSP sessions * upgrade to Retina 0.3.1 which automatically tears down sessions * wait out stale sessions before reconnecting * wait for teardown to complete before shutting down This adds some pressure on #117: it will keep waiting for the stale session to expire even if the user has requested shutdown. I'll try to address that next.
2021-09-10 00:14:01 -04:00
"bstr",
"fallible-iterator",
support --rtsp-library=retina (#37) This isn't well-tested and doesn't yet support an initial connection timeout. But in a quick test, it successfully returns video! I'd like to do some more aggressive code restructuring for zero-copy and to have only one writer thread per sample file directory (rather than the syncer thread + one writer thread per RTSP stream). But I'll likely wait until I drop support for ffmpeg entirely.
2021-06-07 17:36:53 -04:00
]
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
[[package]]
name = "serde"
cargo update
2021-08-31 15:59:39 -04:00
version = "1.0.130"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "f12d06de37cf59146fbdecab66aa99f9fe4f78722e3607577a5375d66bd0c913"
lose "extern crate" everywhere (Rust 2018 edition)
2018-12-28 22:53:29 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"serde_derive",
lose "extern crate" everywhere (Rust 2018 edition)
2018-12-28 22:53:29 -05:00
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "serde_bytes"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.10.5"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "defbb8a83d7f34cc8380751eeb892b825944222888aff18996ea7901f24aec88"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"serde",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
upgrade dependencies Rust 1.15+ now supports serde codegen on stable without the build.rs. Update to serde 0.9 and uuid crate 0.4 to match.
2017-02-05 23:13:51 -05:00
name = "serde_derive"
cargo update
2021-08-31 15:59:39 -04:00
version = "1.0.130"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "d7bc1a1ab1961464eae040d96713baa5a724a8152c1222492465b54322ec508b"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
dependencies = [
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
"syn",
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
]
[[package]]
name = "serde_json"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "1.0.68"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "0f690853975602e1bfe1ccbf50504d67174e3bcf340f23b5ea9992e0587a52d8"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"indexmap",
"itoa",
"ryu",
"serde",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
]
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "serde_mcf"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "6a8e71f1e2ddef2fb0451a9fcf2d975d05aac7fb6e452de01da13bff1b4c46cd"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"data-encoding",
"error-chain 0.11.0",
"lazy_static",
"serde",
"serde_bytes",
"serde_derive",
"serde_json",
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
"toml",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
]
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
[[package]]
name = "serde_urlencoded"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.7.0"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "edfa57a7f8d9c1d260a549e7224100f6c43d43f9103e06dd8b4095a9b2b43ce9"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
dependencies = [
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"form_urlencoded",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"itoa",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"ryu",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"serde",
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
]
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "serde_yaml"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.8.21"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "d8c608a35705a5d3cdc9fbe403147647ff34b921f8e833e49306df898f9b20af"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"dtoa",
cargo update
2021-08-31 15:59:39 -04:00
"indexmap",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"serde",
"yaml-rust",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
]
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
[[package]]
name = "sha-1"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.9.8"
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "99cd6713db3cf16b6c84e06321e049a9b9f699826e16096d23bbcc44d15d51a6"
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
dependencies = [
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
"block-buffer",
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
"cpufeatures",
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
"digest",
"opaque-debug",
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
]
update deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "sha2"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.9.8"
update deps
2019-02-14 01:43:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "b69f9a4c9740d74c5baa3fd2e547f9525fa8088a8a958e0ca2409a514e33f5fa"
update deps
2019-02-14 01:43:30 -05:00
dependencies = [
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
"block-buffer",
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
"cpufeatures",
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
"digest",
"opaque-debug",
update deps
2019-02-14 01:43:30 -05:00
]
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
name = "signal-hook"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.3.10"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "9c98891d737e271a2954825ef19e46bd16bdb98e2746f2eec4f7a4ef7946efd1"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"libc",
"signal-hook-registry",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
]
[[package]]
name = "signal-hook-registry"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "1.4.0"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "e51e73328dc4ac0c7ccbda3a494dfa03df1de2f46018127f60c693f2648455b0"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"libc",
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
]
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
name = "slab"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.4.4"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "c307a32c1c5c437f38c7fd45d753050587732ba8628319fbdf12a7e289ccc590"
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
name = "smallvec"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "1.7.0"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "1ecab6c735a6bb4139c0caafd0cc3635748bbb3acf4550e8138122099251f309"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "socket2"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.4.2"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "5dc90fe6c7be1a323296982db1836d1ea9e47b6839496dde9a541bc496df3516"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
dependencies = [
"libc",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
]
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
update deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "spin"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
version = "0.5.2"
update deps
2019-02-14 01:43:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "6e63cff320ae2c57904679ba7cb63280a3dc4613885beafb148ee7bf9aa9042d"
update deps
2019-02-14 01:43:30 -05:00
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
update dependencies * The mylog update fixes a couple bad bugs. * Otherwise, just keep up with the Rust ecosystem.
2017-06-11 15:57:55 -04:00
name = "stable_deref_trait"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "1.2.0"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "a8f112729512f8e442d81f95a8a7ddf2b7c6b8a1a6f509a95864142b30cab2d3"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
replace regex use with nom This reduces the binary size noticeably on my macOS machine (#70): unstripped stripped 1 before switching to clap 11.1 MiB 6.7 MiB 2 after switching to clap 11.4 MiB 6.9 MiB 3 without regex 10.1 MiB 5.9 MiB
2020-04-18 02:02:02 -04:00
[[package]]
name = "static_assertions"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "1.1.0"
replace regex use with nom This reduces the binary size noticeably on my macOS machine (#70): unstripped stripped 1 before switching to clap 11.1 MiB 6.7 MiB 2 after switching to clap 11.4 MiB 6.9 MiB 3 without regex 10.1 MiB 5.9 MiB
2020-04-18 02:02:02 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "a2eb9349b6444b326872e140eb1cf5e7c522154d69e7a0ffb0fb81c06b37543f"
replace regex use with nom This reduces the binary size noticeably on my macOS machine (#70): unstripped stripped 1 before switching to clap 11.1 MiB 6.7 MiB 2 after switching to clap 11.4 MiB 6.9 MiB 3 without regex 10.1 MiB 5.9 MiB
2020-04-18 02:02:02 -04:00
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "strsim"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
version = "0.9.3"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "6446ced80d6c486436db5c078dde11a9f73d42b57fb273121e160b84f63d894c"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
[[package]]
name = "structopt"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.3.23"
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "bf9d950ef167e25e0bdb073cf1d68e9ad2795ac826f2f3f59647817cf23c0bfa"
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
dependencies = [
"clap",
"lazy_static",
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"structopt-derive",
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
]
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
[[package]]
name = "structopt-derive"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.4.16"
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "134d838a2c9943ac3125cf6df165eda53493451b719f3255b2a26b85f772d0ba"
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
dependencies = [
"heck",
"proc-macro-error",
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
"syn",
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "subtle"
cargo update
2021-08-31 15:59:39 -04:00
version = "2.4.1"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "6bdef32e8150c2a081110b42772ffe7d7c9032b606bc226c8260fd97e0976601"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
update most deps, notably including reqwest Fixes #60 The reqwest dependency is significant because the old version required an old version of openssl, complicating compilation on newer platforms. reqwest also pulled in old/duplicate versions of hyper, tokio, etc. Nice to drop a lot of that cruft. I left rusqlite and uuid alone because they had breaking changes I didn't want to mess with at the moment. Bumped the minimum Rust version to 1.30.0, as required by the new encoding_rs crate (and perhaps other things).
2018-11-20 12:32:55 -05:00
[[package]]
name = "syn"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "1.0.77"
update most deps, notably including reqwest Fixes #60 The reqwest dependency is significant because the old version required an old version of openssl, complicating compilation on newer platforms. reqwest also pulled in old/duplicate versions of hyper, tokio, etc. Nice to drop a lot of that cruft. I left rusqlite and uuid alone because they had breaking changes I didn't want to mess with at the moment. Bumped the minimum Rust version to 1.30.0, as required by the new encoding_rs crate (and perhaps other things).
2018-11-20 12:32:55 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "5239bc68e0fef57495900cfea4e8dc75596d9a319d7e16b1e0a440d24e6fe0a0"
update most deps, notably including reqwest Fixes #60 The reqwest dependency is significant because the old version required an old version of openssl, complicating compilation on newer platforms. reqwest also pulled in old/duplicate versions of hyper, tokio, etc. Nice to drop a lot of that cruft. I left rusqlite and uuid alone because they had breaking changes I didn't want to mess with at the moment. Bumped the minimum Rust version to 1.30.0, as required by the new encoding_rs crate (and perhaps other things).
2018-11-20 12:32:55 -05:00
dependencies = [
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
"unicode-xid",
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
]
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
[[package]]
name = "sync_wrapper"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.1.1"
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "20518fe4a4c9acf048008599e464deb21beeae3d3578418951a189c235a7a9a8"
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
[[package]]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
name = "synstructure"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.12.5"
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "474aaa926faa1603c40b7885a9eaea29b444d1cb2850cb7c0e37bb1a4182f4fa"
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
dependencies = [
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
"syn",
"unicode-xid",
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
]
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
[[package]]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
name = "tap"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "1.0.1"
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "55937e1799185b12863d447f42597ed69d9928686b8d88a1df17376a097d8369"
replace homegrown Error with failure crate This reduces boilerplate, making it a bit easier for me to split the db stuff out into its own crate.
2018-02-21 01:46:14 -05:00
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
stop using old tempdir crate
2021-05-17 16:08:01 -04:00
name = "tempfile"
version = "3.2.0"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
stop using old tempdir crate
2021-05-17 16:08:01 -04:00
checksum = "dac1c663cfc93810f88aed9b8941d48cabf856a1b111c29a40439018d870eb22"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
stop using old tempdir crate
2021-05-17 16:08:01 -04:00
"libc",
"rand",
cargo update
2021-08-31 15:59:39 -04:00
"redox_syscall 0.2.10",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"remove_dir_all",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
add matching time parsing and formatting routines * add a --ts subcommand to convert between numeric and human-readable representations. This is handy when directly inspecting the SQLite database or API output. * also take the human-readable form in the web interface's camera view. * to reduce confusion, when using trim=true on the web interface's camera view, trim the displayed starting and ending times as well as the actual .mp4 file links.
2017-01-13 02:09:02 -05:00
]
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
[[package]]
name = "term"
version = "0.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "edd106a334b7657c10b7c540a0106114feadeb4dc314513e97df481d5d966f42"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"byteorder",
"dirs",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
]
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
name = "term_size"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.3.2"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "1e4129646ca0ed8f45d09b929036bafad5377103edd06e50bf574b353d2b08d9"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"libc",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
]
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
[[package]]
name = "textwrap"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "d326610f408c7a4eb6f51c37c330e496b08506c9457c9d34287ecc38809fb060"
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
dependencies = [
switch from docopt to structopt A couple reasons for this: * the docopt crate is "unlikely to see significant future evolution", and the wider docopt project is "mostly unmaintained at this point". clap/structopt is more full-featured, has more natural subcommand support, etc. * it may allow me to shrink the binary (#70). This change alone seems to be a slight regression, but it's a step toward getting rid of regex, which is pretty large. And I feel less ridiculous now that I don't have two parsing crates anyway; prettydiff was pulling in structopt. There are some behavior changes here: * misc --help output changes and such as you'd expect from switching argument-parsing libraries * I properly used PathBuf and OsString for stuff that theoretically could be non-UTF-8. I haven't tested that it actually made any difference. I'm also still storing the sample file dirname as "text" in the database to avoid causing a diff when not doing a schema change.
2020-04-18 01:41:55 -04:00
"term_size",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"unicode-width",
schema comparison in new upgrade tests, "moonfire-nvr check" The .sql files here are copied from earlier revisions: v0.sql fee4141:src/schema.sql v1.sql 0d69f4f:src/schema.sql v3.sql 422cd2a:db/schema.sql
2019-07-11 11:07:40 -04:00
]
update various other deps
2021-05-17 14:05:54 -04:00
[[package]]
name = "thiserror"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "1.0.29"
update various other deps
2021-05-17 14:05:54 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "602eca064b2d83369e2b2f34b09c70b605402801927c65c11071ac911d299b88"
update various other deps
2021-05-17 14:05:54 -04:00
dependencies = [
"thiserror-impl",
]
[[package]]
name = "thiserror-impl"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "1.0.29"
update various other deps
2021-05-17 14:05:54 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "bad553cc2c78e8de258400763a647e80e6d1b31ee237275d756f6836d204494c"
update various other deps
2021-05-17 14:05:54 -04:00
dependencies = [
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
"syn",
update various other deps
2021-05-17 14:05:54 -04:00
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "time"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.1.44"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "6db9e6914ab8b1ae1c260a4ae7a49b6c5611b40328a735b21862567685e73255"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"libc",
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
"wasi 0.10.0+wasi-snapshot-preview1",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
]
[[package]]
name = "tinyvec"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "1.5.0"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "f83b2a3d4d9091d0abd7eba4dc2710b1718583bd4d8992e2190720ea38f391f7"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
dependencies = [
"tinyvec_macros",
]
[[package]]
name = "tinyvec_macros"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cda74da7e1a664f795bb1f8a87ec406fb89a02522cf6e50620d016add6dbbf5c"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
[[package]]
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
name = "tokio"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "1.12.0"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "c2c2416fdedca8443ae44b4527de1ea633af61d8f7169ffa6e72c5b53d24efcc"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
dependencies = [
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
"autocfg",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"bytes",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"libc",
"memchr",
"mio",
"num_cpus",
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
"once_cell",
upgrade some deps including parking_lot Now there's a single parking_lot version, yay.
2020-11-24 01:46:05 -05:00
"parking_lot",
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
"pin-project-lite",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"signal-hook-registry",
"tokio-macros",
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
]
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
[[package]]
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
name = "tokio-macros"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "1.3.0"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "54473be61f4ebe4efd09cec9bd5d16fa51d70ea0192213d754d2d500457db110"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
dependencies = [
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
"syn",
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
]
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
[[package]]
name = "tokio-stream"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.1.7"
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "7b2f3f698253f03119ac0102beaa64f67a67e08074d03a22d18784104543727f"
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
dependencies = [
"futures-core",
"pin-project-lite",
"tokio",
]
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
[[package]]
name = "tokio-tungstenite"
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
version = "0.15.0"
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
checksum = "511de3f85caf1c98983545490c3d09685fa8eb634e57eec22bb4db271f46cbd8"
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
dependencies = [
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"futures-util",
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
"log",
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
"pin-project",
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
"tokio",
"tungstenite",
]
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
[[package]]
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
name = "tokio-util"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.6.8"
upgrade a few deps
2018-08-25 01:06:14 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "08d3725d3efa29485e87311c5b699de63cde14b00ed4d256b8318aa30ca452cd"
upgrade a few deps
2018-08-25 01:06:14 -04:00
dependencies = [
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"bytes",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"futures-core",
"futures-sink",
"log",
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
"pin-project-lite",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"tokio",
upgrade a few deps
2018-08-25 01:06:14 -04:00
]
[[package]]
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
name = "toml"
version = "0.4.10"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "758664fc71a3a69038656bee8b6be6477d2a6c315a6b81f7081f591bffa4111f"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"serde",
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
]
update several dependencies I left serde alone because uuid hasn't been updated for the new version.
2017-01-27 23:58:04 -05:00
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
[[package]]
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
name = "tower-service"
upgrade some other deps
2021-01-27 15:11:36 -05:00
version = "0.3.1"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some other deps
2021-01-27 15:11:36 -05:00
checksum = "360dfd1d6d30e05fda32ace2c8c70e9c0a9da713275777f5a4dbb8a1893930c6"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "tracing"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.1.28"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "84f96e095c0c82419687c20ddf5cb3eadb61f4e1405923c9dc8e53a1adacbda8"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
logging improvements * allow debug/trace logging on release builds again * enable log messages from hyper. I didn't notice they went away with 0.14.0, although there's a breaking change in the log: https://github.com/hyperium/hyper/blob/master/CHANGELOG.md#v0140-2020-12-23 * downgrade some particularly spammy messages
2021-06-05 02:28:48 -04:00
"log",
upgrade tokio, bytes, hyper, reqwest, http-serve This was mostly straightforward. The most confusing part waas the Sync bound change on body streams. I copied what hyper did and it seemed to work. /shruggie
2021-01-27 14:47:52 -05:00
"pin-project-lite",
logging improvements * allow debug/trace logging on release builds again * enable log messages from hyper. I didn't notice they went away with 0.14.0, although there's a breaking change in the log: https://github.com/hyperium/hyper/blob/master/CHANGELOG.md#v0140-2020-12-23 * downgrade some particularly spammy messages
2021-06-05 02:28:48 -04:00
"tracing-attributes",
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"tracing-core",
]
logging improvements * allow debug/trace logging on release builds again * enable log messages from hyper. I didn't notice they went away with 0.14.0, although there's a breaking change in the log: https://github.com/hyperium/hyper/blob/master/CHANGELOG.md#v0140-2020-12-23 * downgrade some particularly spammy messages
2021-06-05 02:28:48 -04:00
[[package]]
name = "tracing-attributes"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.1.16"
logging improvements * allow debug/trace logging on release builds again * enable log messages from hyper. I didn't notice they went away with 0.14.0, although there's a breaking change in the log: https://github.com/hyperium/hyper/blob/master/CHANGELOG.md#v0140-2020-12-23 * downgrade some particularly spammy messages
2021-06-05 02:28:48 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "98863d0dd09fa59a1b79c6750ad80dbda6b75f4e71c437a6a1a8cb91a8bcbd77"
logging improvements * allow debug/trace logging on release builds again * enable log messages from hyper. I didn't notice they went away with 0.14.0, although there's a breaking change in the log: https://github.com/hyperium/hyper/blob/master/CHANGELOG.md#v0140-2020-12-23 * downgrade some particularly spammy messages
2021-06-05 02:28:48 -04:00
dependencies = [
"proc-macro2",
"quote",
"syn",
]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "tracing-core"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.1.20"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "46125608c26121c81b0c6d693eab5a420e416da7e43c426d2e8f7df8da8a3acf"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
dependencies = [
"lazy_static",
]
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
[[package]]
name = "try-lock"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.2.3"
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "59547bce71d9c38b83d9c0e92b6066c4253371f15005def0c30d9657f50c7642"
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
[[package]]
name = "tungstenite"
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
version = "0.14.0"
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
checksum = "a0b2d8558abd2e276b0a8df5c05a2ec762609344191e5fd23e292c910e9165b5"
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
dependencies = [
upgrade some other deps
2021-01-27 15:11:36 -05:00
"base64",
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
"byteorder",
"bytes",
"http",
"httparse",
"log",
stop using old tempdir crate
2021-05-17 16:08:01 -04:00
"rand",
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
"sha-1",
update various other deps
2021-05-17 14:05:54 -04:00
"thiserror",
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
"url",
"utf-8",
]
update deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "typenum"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "1.14.0"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "b63708a265f51345575b27fe43f9500ad611579e764c79edbc2037b1121959ec"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
backend support for live stream (#59) This is so far completely untested, for use by a new UI prototype. It creates a new URL endpoint which sends one video/mp4 media segment per key frame, with the dependent frames included. This means there will be about one key frame interval of latency (typically about a second). This seems hard to avoid, as mentioned in issue #59.
2019-01-21 18:58:52 -05:00
[[package]]
name = "unchecked-index"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "eeba86d422ce181a719445e51872fa30f1f7413b62becb52e95ec91aa262d85c"
backend support for live stream (#59) This is so far completely untested, for use by a new UI prototype. It creates a new URL endpoint which sends one video/mp4 media segment per key frame, with the dependent frames included. This means there will be about one key frame interval of latency (typically about a second). This seems hard to avoid, as mentioned in issue #59.
2019-01-21 18:58:52 -05:00
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "unicode-bidi"
cargo update
2021-08-31 15:59:39 -04:00
version = "0.3.6"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-31 15:59:39 -04:00
checksum = "246f4c42e67e7a4e3c6106ff716a5d067d4132a642840b242e357e468a2a0085"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "unicode-normalization"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.1.19"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "d54590932941a9e9266f0832deed84ebe1bf2e4c9e4a3554d393d18f5e854bf9"
update deps
2019-02-14 01:43:30 -05:00
dependencies = [
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"tinyvec",
update deps
2019-02-14 01:43:30 -05:00
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
[[package]]
name = "unicode-segmentation"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "1.8.0"
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "8895849a949e7845e06bd6dc1aa51731a103c42707010a5b591c0038fb73385b"
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
[[package]]
name = "unicode-width"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.1.9"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "3ed742d4ea2bd1176e236172c8429aaf54486e7ac098db29ffe6529e0ce50973"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "unicode-xid"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "0.2.2"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "8ccb82d61f80a663efe1f787a51b16b5a51e3314d6ac365b08639f52387b33f3"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "untrusted"
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
version = "0.7.1"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update libpasta/ring This uses my (hopefully short-lived) libpasta fork.
2020-11-24 00:47:02 -05:00
checksum = "a156c684c91ea7d62626509bce3cb4e1d9ed5c4d978f7b4352658f96a4c26b4a"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "url"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "2.2.2"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "a507c383b2d33b5fc35d1861e77e6b383d158b2da5e14fe51b83dfedf6fd578c"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
dependencies = [
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
"form_urlencoded",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"idna",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"matches",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"percent-encoding",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
]
add matching time parsing and formatting routines * add a --ts subcommand to convert between numeric and human-readable representations. This is handy when directly inspecting the SQLite database or API output. * also take the human-readable form in the web interface's camera view. * to reduce confusion, when using trim=true on the web interface's camera view, trim the displayed starting and ending times as well as the actual .mp4 file links.
2017-01-13 02:09:02 -05:00
update most deps, notably including reqwest Fixes #60 The reqwest dependency is significant because the old version required an old version of openssl, complicating compilation on newer platforms. reqwest also pulled in old/duplicate versions of hyper, tokio, etc. Nice to drop a lot of that cruft. I left rusqlite and uuid alone because they had breaking changes I didn't want to mess with at the moment. Bumped the minimum Rust version to 1.30.0, as required by the new encoding_rs crate (and perhaps other things).
2018-11-20 12:32:55 -05:00
[[package]]
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
name = "utf-8"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "0.7.6"
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "09cc8ee72d2a9becf2f2febe0205bbed8fc6615b7cb429ad062dc7b7ddd036a9"
switch to websocket for live stream (#59) The multipart stream / hanging GET approach worked in a prototype for a single stream, but Chrome has a per-host limit of six connections. If I try streaming all my cameras at once, I hit that limit. I can't open all the streams, much less additional connections to load init segments and such. Websockets apparently has a much higher limit of 256.
2020-02-29 00:41:31 -05:00
[[package]]
update most deps, notably including reqwest Fixes #60 The reqwest dependency is significant because the old version required an old version of openssl, complicating compilation on newer platforms. reqwest also pulled in old/duplicate versions of hyper, tokio, etc. Nice to drop a lot of that cruft. I left rusqlite and uuid alone because they had breaking changes I didn't want to mess with at the moment. Bumped the minimum Rust version to 1.30.0, as required by the new encoding_rs crate (and perhaps other things).
2018-11-20 12:32:55 -05:00
name = "uuid"
upgrade some other deps
2021-01-27 15:11:36 -05:00
version = "0.8.2"
update most deps, notably including reqwest Fixes #60 The reqwest dependency is significant because the old version required an old version of openssl, complicating compilation on newer platforms. reqwest also pulled in old/duplicate versions of hyper, tokio, etc. Nice to drop a lot of that cruft. I left rusqlite and uuid alone because they had breaking changes I didn't want to mess with at the moment. Bumped the minimum Rust version to 1.30.0, as required by the new encoding_rs crate (and perhaps other things).
2018-11-20 12:32:55 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some other deps
2021-01-27 15:11:36 -05:00
checksum = "bc5cf98d8186244414c848017f0e2676b3fcb46807f6668a97dfe67359a3c4b7"
update most deps, notably including reqwest Fixes #60 The reqwest dependency is significant because the old version required an old version of openssl, complicating compilation on newer platforms. reqwest also pulled in old/duplicate versions of hyper, tokio, etc. Nice to drop a lot of that cruft. I left rusqlite and uuid alone because they had breaking changes I didn't want to mess with at the moment. Bumped the minimum Rust version to 1.30.0, as required by the new encoding_rs crate (and perhaps other things).
2018-11-20 12:32:55 -05:00
dependencies = [
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
"getrandom 0.2.3",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"serde",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
]
update dependencies * The mylog update fixes a couple bad bugs. * Otherwise, just keep up with the Rust ecosystem.
2017-06-11 15:57:55 -04:00
[[package]]
name = "vcpkg"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.2.15"
update dependencies * The mylog update fixes a couple bad bugs. * Otherwise, just keep up with the Rust ecosystem.
2017-06-11 15:57:55 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "accd4ea62f7bb7a82fe23066fb0957d48ef677f6eeb8215f372f52e48bb32426"
update dependencies * The mylog update fixes a couple bad bugs. * Otherwise, just keep up with the Rust ecosystem.
2017-06-11 15:57:55 -04:00
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
name = "version_check"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
version = "0.9.3"
use nix to remove many uses of unsafe
2019-07-12 00:59:01 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update The immediate motivation is to address these CI failures with nightly: https://github.com/scottlamb/moonfire-nvr/runs/2593322801?check_suite_focus=true ``` Compiling lock_api v0.4.2 error[E0557]: feature has been removed --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.2/src/lib.rs:91:42 | 91 | #![cfg_attr(feature = "nightly", feature(const_fn))] | ^^^^^^^^ feature has been removed | = note: split into finer-grained feature gates ``` Strangely, they don't occur locally with "rustc 1.54.0-nightly (fe72845f7 2021-05-16)" but do on CI with the exact same version?!? I don't get it, but lock-api 0.4.4 is advertised as being updated for latest nightly, so I expect this will address the problem anyway.
2021-05-17 13:31:06 -04:00
checksum = "5fecdca9a5291cc2b8dcf7dc02453fee791a280f3743cb0905f8822ae463b3fe"
use nix to remove many uses of unsafe
2019-07-12 00:59:01 -04:00
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
[[package]]
name = "want"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
version = "0.3.0"
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
checksum = "1ce8a968cb1cd110d136ff8b819a556d6fb6d919363c61534f6860c7eb172ba0"
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"log",
"try-lock",
upgrade to hyper 0.12.x Just one (intentional) functional change---now the streamers start shutting down while the webserver shuts down gracefully.
2018-08-30 01:26:19 -04:00
]
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
[[package]]
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
name = "wasi"
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
version = "0.9.0+wasi-snapshot-preview1"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
checksum = "cccddf32554fecc6acb585f82a32a72e28b48f8c4c1883ddfeeeaa96f7d8e519"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
[[package]]
name = "wasi"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
version = "0.10.0+wasi-snapshot-preview1"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some server deps I avoided rtcp 0.2.2->0.2.3 because of an accidental semver break.
2021-07-09 18:01:15 -04:00
checksum = "1a143597ca7c7793eff794def352d41792a93c481eb1042423ff7ff72ba2c31f"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
[[package]]
name = "wasm-bindgen"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.2.78"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "632f73e236b219150ea279196e54e610f5dbafa5d61786303d4da54f84e47fce"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"serde",
"serde_json",
"wasm-bindgen-macro",
]
[[package]]
name = "wasm-bindgen-backend"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.2.78"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "a317bf8f9fba2476b4b2c85ef4c4af8ff39c3c7f0cdfeed4f82c34a880aa837b"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"bumpalo",
"lazy_static",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"log",
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
"syn",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"wasm-bindgen-shared",
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
]
[[package]]
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
name = "wasm-bindgen-futures"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.4.28"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "8e8d7523cb1f2a4c96c1317ca690031b714a51cc14e05f712446691f413f5d39"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
dependencies = [
bump versions of blake3, nom, tokio-tungstenite
2021-08-31 16:04:26 -04:00
"cfg-if",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"js-sys",
"wasm-bindgen",
"web-sys",
]
[[package]]
name = "wasm-bindgen-macro"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.2.78"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "d56146e7c495528bf6587663bea13a8eb588d39b36b679d83972e1a2dbbdacf9"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
dependencies = [
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"quote",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"wasm-bindgen-macro-support",
]
[[package]]
name = "wasm-bindgen-macro-support"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.2.78"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "7803e0eea25835f8abdc585cd3021b3deb11543c6fe226dcd30b228857c5c5ab"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
dependencies = [
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
"syn",
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
"wasm-bindgen-backend",
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-shared"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.2.78"
upgrade some other deps
2021-01-27 15:11:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "0237232789cf037d5480773fe568aac745bfe2afbc11a863e97901780a6b47cc"
upgrade some other deps
2021-01-27 15:11:36 -05:00
[[package]]
name = "wasmer_enumset"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cf088cc1f7d247fd96dff0df46fb1bbb747d8a69ae1ecd71aed55c55e354b2d8"
dependencies = [
"num-traits",
"wasmer_enumset_derive",
]
[[package]]
name = "wasmer_enumset_derive"
version = "0.5.0"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some other deps
2021-01-27 15:11:36 -05:00
checksum = "a8d1b32d98e11194200baf6d3f85eb2d6cfe56f6d9af0dd617f90ca48f958a88"
dependencies = [
"darling",
de-dupe prettydiff deps via a fork
2021-05-17 15:17:18 -04:00
"proc-macro2",
"quote",
"syn",
upgrade some other deps
2021-01-27 15:11:36 -05:00
]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
[[package]]
name = "web-sys"
update various Rust deps
2021-09-29 14:44:29 -04:00
version = "0.3.55"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various Rust deps
2021-09-29 14:44:29 -04:00
checksum = "38eb105f1c59d9eaa6b5cdc92b859d85b926e82cb2e0945cd0c9259faa6fe9fb"
upgrade some deps, including reqwest The reqwest one is particularly notable because it means not having two versions of hyper/http/tokio/futures/bytes. It also drops a number of transitive deps; with some work I think I could stop depending on regex now.
2020-01-09 23:06:30 -05:00
dependencies = [
"js-sys",
"wasm-bindgen",
]
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
upgrade deps, including http-serve bugfix This was including the wrong Content-Encoding: header on gzipped json responses, so Chrome wouldn't understand them at all.
2018-01-30 19:51:32 -05:00
[[package]]
name = "winapi"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.3.9"
upgrade deps, including http-serve bugfix This was including the wrong Content-Encoding: header on gzipped json responses, so Chrome wouldn't understand them at all.
2018-01-30 19:51:32 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
upgrade deps, including http-serve bugfix This was including the wrong Content-Encoding: header on gzipped json responses, so Chrome wouldn't understand them at all.
2018-01-30 19:51:32 -05:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
upgrade deps, including http-serve bugfix This was including the wrong Content-Encoding: header on gzipped json responses, so Chrome wouldn't understand them at all.
2018-01-30 19:51:32 -05:00
]
[[package]]
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
upgrade deps, including http-serve bugfix This was including the wrong Content-Encoding: header on gzipped json responses, so Chrome wouldn't understand them at all.
2018-01-30 19:51:32 -05:00
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
[[package]]
name = "winreg"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
version = "0.7.0"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "0120db82e8a1e0b9fb3345a539c478767c0048d842860994d96113d5b667bd69"
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
dependencies = [
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
"winapi",
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
]
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
name = "wyz"
update some deps, including cursive cursive renamed a few methods, so keep up with that. No functional changes.
2020-01-20 11:56:57 -05:00
version = "0.2.0"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
checksum = "85e60b0d1b5f99db2556934e21937020776a5d31520bf169e851ac44e6420214"
[[package]]
name = "xi-unicode"
upgrade some other deps
2021-01-27 15:11:36 -05:00
version = "0.3.0"
update various deps This brings most things reasonably up-to-date. libpasta's deps are dragging a bit, keeping us on an older ring to avoid duplication, and causing us to use three versions of base64. And I need to update a few of my companion crates' parking_lot dep to match tokio.
2020-11-23 03:23:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some other deps
2021-01-27 15:11:36 -05:00
checksum = "a67300977d3dc3f8034dae89778f502b6ba20b269527b3223ba59c0cf393bb8a"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "yaml-rust"
upgrade some other deps
2021-01-27 15:11:36 -05:00
version = "0.4.5"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade some other deps
2021-01-27 15:11:36 -05:00
checksum = "56c1936c4cc7a1c9ab21a1ebb602eb942ba868cbd44a99cb7cdc5892335e1c85"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
dependencies = [
upgrade to hyper 0.13 ecosystem This doesn't take much advantage of async fns so far. For example, the with_{form,json}_body functions are still designed to be used with future combinators when it'd be more natural to call them from async fns now. But it's a start. Similarly, this still uses the old version of reqwest. Small steps. Requires Rust 1.40 now. (1.39 is a requirement of async, and 1.40 is a requirement of http-serve 0.2.0.)
2020-01-09 02:04:36 -05:00
"linked-hash-map",
]