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/Cargo.lock

2900 lines
134 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.
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
[[package]]
name = "adler32"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "1.0.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"
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 = "aho-corasick"
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
version = "0.7.4"
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"
dependencies = [
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
"memchr 2.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "ansi_term"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
]
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
name = "arc-swap"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.3.11"
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"
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"
dependencies = [
"blake2-rfc 0.2.18 (registry+https://github.com/rust-lang/crates.io-index)",
"scoped_threadpool 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
]
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
name = "array-macro"
update deps
2019-02-14 01:43:30 -05:00
version = "1.0.3"
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 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"
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
version = "0.4.11"
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"
dependencies = [
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
"nodrop 0.1.13 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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 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
version = "0.2.13"
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"
dependencies = [
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
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
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
]
update deps
2018-12-28 11:13:03 -05:00
[[package]]
name = "autocfg"
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
version = "0.1.5"
update deps
2018-12-28 11:13:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
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
version = "0.3.33"
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"
dependencies = [
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
"backtrace-sys 0.1.31 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cfg-if 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"rustc-demangle 0.1.15 (registry+https://github.com/rust-lang/crates.io-index)",
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-sys"
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
version = "0.1.31"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cc 1.0.37 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
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]]
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 = "base64"
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
version = "0.9.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"
dependencies = [
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
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"safemem 0.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
2018-12-28 11:13:03 -05:00
[[package]]
name = "base64"
update deps
2019-02-14 01:43:30 -05:00
version = "0.10.1"
update deps
2018-12-28 11:13:03 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2018-12-28 11:13:03 -05:00
]
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
name = "bitflags"
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
version = "1.1.0"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
dependencies = [
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
"arrayvec 0.4.11 (registry+https://github.com/rust-lang/crates.io-index)",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
"constant_time_eq 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
]
update deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "block-buffer"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.7.3"
update deps
2019-02-14 01:43:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"block-padding 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"byte-tools 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
"generic-array 0.12.3 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
]
[[package]]
name = "block-padding"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.1.4"
update deps
2019-02-14 01:43:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"byte-tools 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 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
version = "0.2.2"
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"
dependencies = [
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"memchr 2.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"regex-automata 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
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
"serde 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
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
2019-02-14 01:43:30 -05:00
[[package]]
name = "byte-tools"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
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
version = "1.3.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"
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]]
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 = "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.4.12"
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 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
dependencies = [
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
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"either 1.5.2 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
"iovec 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
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 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 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 = "c2-chacha"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
"ppv-lite86 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
]
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
[[package]]
name = "cc"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "1.0.37"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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 = "cfg-if"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -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"
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 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
version = "0.4.7"
upgrade a few deps
2018-08-25 01:06:14 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"num-integer 0.1.41 (registry+https://github.com/rust-lang/crates.io-index)",
"num-traits 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"time 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -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 = "clap"
version = "2.33.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"ansi_term 0.11.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"atty 0.2.13 (registry+https://github.com/rust-lang/crates.io-index)",
"bitflags 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"strsim 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
"textwrap 0.11.0 (registry+https://github.com/rust-lang/crates.io-index)",
"unicode-width 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"vec_map 0.8.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
upgrade a few deps
2018-08-25 01:06:14 -04:00
[[package]]
name = "cloudabi"
version = "0.0.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"
dependencies = [
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
"bitflags 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "constant_time_eq"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -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 = "cookie"
version = "0.12.0"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"time 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)",
"url 1.7.2 (registry+https://github.com/rust-lang/crates.io-index)",
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]]
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
name = "cookie_store"
version = "0.7.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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cookie 0.12.0 (registry+https://github.com/rust-lang/crates.io-index)",
"failure 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"idna 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
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
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"publicsuffix 1.5.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"serde 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_json 1.0.40 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"time 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)",
"try_from 0.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
"url 1.7.2 (registry+https://github.com/rust-lang/crates.io-index)",
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 a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
name = "core-foundation"
version = "0.6.4"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"core-foundation-sys 0.6.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
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 all Rust deps
2018-12-01 18:20:19 -05: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 = "core-foundation-sys"
version = "0.6.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
version = "1.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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cfg-if 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
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"
version = "0.3.8"
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"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"crossbeam-utils 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
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
"smallvec 0.6.10 (registry+https://github.com/rust-lang/crates.io-index)",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -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 = "crossbeam-deque"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.7.1"
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"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"crossbeam-epoch 0.7.1 (registry+https://github.com/rust-lang/crates.io-index)",
"crossbeam-utils 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "crossbeam-epoch"
update deps
2019-02-14 01:43:30 -05:00
version = "0.7.1"
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"
dependencies = [
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
"arrayvec 0.4.11 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cfg-if 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"crossbeam-utils 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"memoffset 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
"scopeguard 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
]
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
[[package]]
name = "crossbeam-queue"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"crossbeam-utils 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
]
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "crossbeam-utils"
update deps
2019-02-14 01:43:30 -05:00
version = "0.6.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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cfg-if 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -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]]
update deps
2019-02-14 01:43:30 -05:00
name = "crypto-mac"
version = "0.7.0"
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"
dependencies = [
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
"generic-array 0.12.3 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"subtle 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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]]
name = "cstr"
version = "0.1.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"cstr-macros 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"procedural-masquerade 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "cstr-macros"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"procedural-masquerade 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
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
"syn 0.15.39 (registry+https://github.com/rust-lang/crates.io-index)",
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"
version = "1.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"bstr 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"csv-core 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
"itoa 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
"ryu 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"serde 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
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"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"memchr 2.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
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 cursive to latest major version
2019-05-31 19:35:07 -04:00
version = "0.12.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"
dependencies = [
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
"cfg-if 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
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
"chrono 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"crossbeam-channel 0.3.8 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
"enum-map 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)",
"enumset 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
"hashbrown 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
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
"maplit 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"ncurses 5.99.0 (registry+https://github.com/rust-lang/crates.io-index)",
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"num 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"owning_ref 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"signal-hook 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"term_size 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
"toml 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"unicode-segmentation 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"unicode-width 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"xi-unicode 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
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"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"darling_core 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
"darling_macro 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "darling_core"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"fnv 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)",
"ident_case 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
"proc-macro2 0.4.30 (registry+https://github.com/rust-lang/crates.io-index)",
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
"quote 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
"strsim 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"syn 0.15.39 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
]
[[package]]
name = "darling_macro"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"darling_core 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"quote 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 0.15.39 (registry+https://github.com/rust-lang/crates.io-index)",
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"
update deps
2019-02-14 01:43:30 -05:00
version = "2.1.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"
update deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "digest"
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
version = "0.8.1"
update deps
2019-02-14 01:43:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"generic-array 0.12.3 (registry+https://github.com/rust-lang/crates.io-index)",
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"
dependencies = [
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
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
"redox_users 0.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "docopt"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "1.1.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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"regex 1.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
"serde 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"strsim 0.9.2 (registry+https://github.com/rust-lang/crates.io-index)",
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 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"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.4.4"
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"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "either"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "1.5.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"
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"
version = "0.3.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.8.17"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cfg-if 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
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"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
version = "0.5.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"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"enum-map-derive 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"enum-map-internals 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
]
[[package]]
name = "enum-map-derive"
update deps
2019-02-14 01:43:30 -05:00
version = "0.4.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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"proc-macro2 0.4.30 (registry+https://github.com/rust-lang/crates.io-index)",
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
"quote 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)",
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"syn 0.14.9 (registry+https://github.com/rust-lang/crates.io-index)",
]
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
[[package]]
name = "enum-map-internals"
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
version = "0.1.3"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"array-macro 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
]
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
name = "enumset"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
version = "0.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"
dependencies = [
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
"enumset_derive 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"num-traits 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "enumset_derive"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
version = "0.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"
dependencies = [
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
"darling 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"proc-macro2 0.4.30 (registry+https://github.com/rust-lang/crates.io-index)",
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
"quote 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 0.15.39 (registry+https://github.com/rust-lang/crates.io-index)",
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"
dependencies = [
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
"backtrace 0.3.33 (registry+https://github.com/rust-lang/crates.io-index)",
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 a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.12.1"
update deps
2019-02-14 01:43:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"backtrace 0.3.33 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"version_check 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
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 deps
2019-02-14 01:43:30 -05:00
version = "0.1.5"
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"
dependencies = [
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
"backtrace 0.3.33 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"failure_derive 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
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 deps
2019-02-14 01:43:30 -05:00
version = "0.1.5"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"proc-macro2 0.4.30 (registry+https://github.com/rust-lang/crates.io-index)",
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
"quote 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 0.15.39 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"synstructure 0.10.2 (registry+https://github.com/rust-lang/crates.io-index)",
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 deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "fake-simd"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
[[package]]
name = "fallible-streaming-iterator"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
[[package]]
name = "flate2"
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
version = "1.0.9"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"crc32fast 1.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"miniz-sys 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"miniz_oxide_c_api 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
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 dependencies
2017-11-17 02:01:09 -05:00
version = "1.0.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"
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 = "foreign-types"
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
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"foreign-types-shared 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "foreign-types-shared"
version = "0.1.1"
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 deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "fuchsia-cprng"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
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
2017-11-17 02:01:09 -05:00
name = "fuchsia-zircon"
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
version = "0.3.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"
dependencies = [
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
"bitflags 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"fuchsia-zircon-sys 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
]
[[package]]
name = "fuchsia-zircon-sys"
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
version = "0.3.3"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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 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"
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
version = "0.1.28"
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"
[[package]]
name = "futures-cpupool"
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
version = "0.1.8"
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"
dependencies = [
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
"num_cpus 1.10.1 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "gcc"
version = "0.3.55"
source = "registry+https://github.com/rust-lang/crates.io-index"
update deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "generic-array"
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
version = "0.12.3"
update deps
2019-02-14 01:43:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"typenum 1.10.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
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"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
]
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"
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
version = "0.1.25"
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"
dependencies = [
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
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"fnv 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"http 0.1.17 (registry+https://github.com/rust-lang/crates.io-index)",
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
"indexmap 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"slab 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"string 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"tokio-io 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
]
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
[[package]]
name = "hashbrown"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"unicode-segmentation 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
update deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "hmac"
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
version = "0.7.1"
update deps
2019-02-14 01:43:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"crypto-mac 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"digest 0.8.1 (registry+https://github.com/rust-lang/crates.io-index)",
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 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 = "http"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.1.17"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"fnv 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"itoa 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "http-body"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"http 0.1.17 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-buf 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
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"
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
version = "0.1.2"
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"
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 = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"flate2 1.0.9 (registry+https://github.com/rust-lang/crates.io-index)",
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures-cpupool 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"http 0.1.17 (registry+https://github.com/rust-lang/crates.io-index)",
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
"httpdate 0.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"hyper 0.12.33 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"mime 0.3.13 (registry+https://github.com/rust-lang/crates.io-index)",
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
"smallvec 0.6.10 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
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"
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
version = "1.3.4"
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 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"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
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 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
version = "0.12.33"
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"
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 a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures-cpupool 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
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
"h2 0.1.25 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"http 0.1.17 (registry+https://github.com/rust-lang/crates.io-index)",
"http-body 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"httparse 1.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
"iovec 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"itoa 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
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
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"net2 0.2.33 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"rustc_version 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"time 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tokio 0.1.22 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"tokio-buf 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tokio-executor 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"tokio-io 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-reactor 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"tokio-tcp 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tokio-threadpool 0.1.15 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"tokio-timer 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)",
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
"want 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
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 a hyper vendor branch with Nagle fix There were Nagle's algorithm delays in both the "fresh_client" and "reuse_client" versions of the .mp4 serving benchmark. Now performance is much more consistent.
2017-02-26 22:05:05 -05:00
[[package]]
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
name = "hyper-tls"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.3.2"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
"hyper 0.12.33 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"native-tls 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
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 to a hyper vendor branch with Nagle fix There were Nagle's algorithm delays in both the "fresh_client" and "reuse_client" versions of the .mp4 serving benchmark. Now performance is much more consistent.
2017-02-26 22:05:05 -05: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"
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 = "idna"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.5"
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"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"matches 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"unicode-bidi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"unicode-normalization 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
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"
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
version = "1.0.2"
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 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]]
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 = "iovec"
upgrade deps
2018-01-31 01:05:39 -05:00
version = "0.1.2"
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 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
dependencies = [
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
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
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
]
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
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"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"either 1.5.2 (registry+https://github.com/rust-lang/crates.io-index)",
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"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.4.4"
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"
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 = "kernel32-sys"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi-build 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
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"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "1.3.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"
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
dependencies = [
"spin 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
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
use the latest libc crate to build on OS X
2017-09-22 09:20:40 -04:00
[[package]]
name = "libc"
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
version = "0.2.60"
source = "git+https://github.com/rust-lang/libc#c8aa8ec72d631bc35099bcf5d634cf0a0b841be0"
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
use nix to remove many uses of unsafe
2019-07-12 00:59:01 -04:00
[[package]]
name = "libc"
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
version = "0.2.60"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
update deps
2019-02-14 01:43:30 -05:00
version = "0.1.0"
preliminary web support for auth (#26) Some caveats: * it doesn't record the peer IP yet, which makes it harder to verify sessions are valid. This is a little annoying to do in hyper now (see hyperium/hyper#1410). The direct peer might not be what we want right now anyway because there's no TLS support yet (see #27). In the meantime, the sane way to expose Moonfire NVR to the Internet is via a proxy server, and recording the proxy's IP is not useful. Maybe better to interpret a RFC 7239 Forwarded header (and/or the older X-Forwarded-{For,Proto} headers). * it doesn't ever use Secure (https-only) cookies, for a similar reason. It's not safe to use even with a tls proxy until this is fixed. * there's no "moonfire-nvr config" support for inspecting/invalidating sessions yet. * in debug builds, logging in is crazy slow. See libpasta/libpasta#9. Some notes: * I removed the Javascript "no-use-before-defined" lint, as some of the functions form a cycle. * Fixed #20 along the way. I needed to add support for properly returning non-OK HTTP statuses to signal unauthorized and such. * I removed the Access-Control-Allow-Origin header support, which was at odds with the "SameSite=lax" in the cookie header. The "yarn start" method for running a local proxy server accomplishes the same thing as the Access-Control-Allow-Origin support in a more secure manner.
2018-11-26 00:31:50 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
dependencies = [
"argon2rs 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"data-encoding 2.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"error-chain 0.12.1 (registry+https://github.com/rust-lang/crates.io-index)",
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"num-traits 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"ring 0.14.6 (registry+https://github.com/rust-lang/crates.io-index)",
Merge branch 'master' into auth
2018-12-01 18:27:54 -05:00
"rpassword 2.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
"rust-crypto 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"scrypt 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"serde 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
"serde_mcf 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"serde_yaml 0.8.9 (registry+https://github.com/rust-lang/crates.io-index)",
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 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
version = "0.15.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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cc 1.0.37 (registry+https://github.com/rust-lang/crates.io-index)",
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
"pkg-config 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
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
"vcpkg 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
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"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.5.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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
[[package]]
name = "lock_api"
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
version = "0.1.5"
upgrade a few deps
2018-08-25 01:06:14 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"owning_ref 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"scopeguard 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
]
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
[[package]]
name = "lock_api"
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
version = "0.3.1"
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"
dependencies = [
"scopeguard 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
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"
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
version = "0.4.7"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cfg-if 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "lru-cache"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.1.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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"linked-hash-map 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)",
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"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.8"
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"
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"
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
version = "2.2.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"
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 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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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
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 = "memmap"
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
version = "0.7.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"
dependencies = [
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
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 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 = "memoffset"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
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 = "mime"
update deps
2019-02-14 01:43:30 -05:00
version = "0.3.13"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"unicase 2.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
]
[[package]]
name = "mime_guess"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "2.0.0-alpha.6"
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"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"mime 0.3.13 (registry+https://github.com/rust-lang/crates.io-index)",
"phf 0.7.24 (registry+https://github.com/rust-lang/crates.io-index)",
"phf_codegen 0.7.24 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"unicase 1.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
[[package]]
name = "miniz-sys"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.1.12"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cc 1.0.37 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -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 = "miniz_oxide"
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
version = "0.2.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"
dependencies = [
"adler32 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "miniz_oxide_c_api"
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
version = "0.2.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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cc 1.0.37 (registry+https://github.com/rust-lang/crates.io-index)",
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
"crc32fast 1.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
"miniz_oxide 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
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"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.6.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"
dependencies = [
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
"fuchsia-zircon 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
"fuchsia-zircon-sys 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
"iovec 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"kernel32-sys 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
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
"miow 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"net2 0.2.33 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"slab 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "mio-uds"
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
version = "0.6.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"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"iovec 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"mio 0.6.19 (registry+https://github.com/rust-lang/crates.io-index)",
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"
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
version = "0.2.1"
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"
dependencies = [
"kernel32-sys 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"net2 0.2.33 (registry+https://github.com/rust-lang/crates.io-index)",
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
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
"ws2_32-sys 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = [
update deps
2019-02-14 01:43:30 -05:00
"failure 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
"parking_lot 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"time 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)",
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"
version = "0.0.1"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"base64 0.10.1 (registry+https://github.com/rust-lang/crates.io-index)",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
"blake2-rfc 0.2.18 (registry+https://github.com/rust-lang/crates.io-index)",
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
"cstr 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"failure 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
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
"fnv 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)",
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
"itertools 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"libpasta 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"lru-cache 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"moonfire-base 0.0.1",
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
"mylog 0.1.0 (git+https://github.com/scottlamb/mylog)",
use the nix repository again nix-rust/nix#1097 is merged so it does what we need now.
2019-07-20 19:13:12 -04:00
"nix 0.14.1 (git+https://github.com/nix-rust/nix)",
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
"odds 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"openssl 0.10.23 (registry+https://github.com/rust-lang/crates.io-index)",
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
"parking_lot 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"prettydiff 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"protobuf 3.0.0-pre (git+https://github.com/stepancheg/rust-protobuf)",
"protobuf-codegen-pure 3.0.0-pre (git+https://github.com/stepancheg/rust-protobuf)",
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
"regex 1.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
"rusqlite 0.19.0 (registry+https://github.com/rust-lang/crates.io-index)",
"smallvec 0.6.10 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tempdir 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"time 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"uuid 0.7.4 (registry+https://github.com/rust-lang/crates.io-index)",
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cc 1.0.37 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
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
"pkg-config 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
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"
version = "0.1.0"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"base64 0.10.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"cstr 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
"cursive 0.12.0 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"docopt 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"failure 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"fnv 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures-cpupool 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"http 0.1.17 (registry+https://github.com/rust-lang/crates.io-index)",
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
"http-serve 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"hyper 0.12.33 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
"memchr 2.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"memmap 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"moonfire-base 0.0.1",
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
"moonfire-db 0.0.1",
update dependencies
2017-11-17 02:01:09 -05:00
"moonfire-ffmpeg 0.0.1",
"mylog 0.1.0 (git+https://github.com/scottlamb/mylog)",
use the nix repository again nix-rust/nix#1097 is merged so it does what we need now.
2019-07-20 19:13:12 -04:00
"nix 0.14.1 (git+https://github.com/nix-rust/nix)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"openssl 0.10.23 (registry+https://github.com/rust-lang/crates.io-index)",
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
"parking_lot 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"protobuf 3.0.0-pre (git+https://github.com/stepancheg/rust-protobuf)",
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
"reffers 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"regex 1.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
"reqwest 0.9.18 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"ring 0.14.6 (registry+https://github.com/rust-lang/crates.io-index)",
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
"rusqlite 0.19.0 (registry+https://github.com/rust-lang/crates.io-index)",
"serde 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_json 1.0.40 (registry+https://github.com/rust-lang/crates.io-index)",
"smallvec 0.6.10 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tempdir 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"time 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tokio 0.1.22 (registry+https://github.com/rust-lang/crates.io-index)",
update all Rust deps
2018-12-01 18:20:19 -05:00
"tokio-signal 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
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
"url 1.7.2 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"uuid 0.7.4 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
]
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"
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 = "git+https://github.com/scottlamb/mylog#85bd324aa297de8bef4e1a4445c63acbd5f870b2"
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 = [
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
"chrono 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
"parking_lot 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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 = "native-tls"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.2.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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"openssl 0.10.23 (registry+https://github.com/rust-lang/crates.io-index)",
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
"openssl-probe 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"openssl-sys 0.9.47 (registry+https://github.com/rust-lang/crates.io-index)",
"schannel 0.1.15 (registry+https://github.com/rust-lang/crates.io-index)",
"security-framework 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
"security-framework-sys 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tempfile 3.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "ncurses"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "5.99.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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cc 1.0.37 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
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
"pkg-config 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "net2"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.2.33"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cfg-if 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
use nix to remove many uses of unsafe
2019-07-12 00:59:01 -04:00
[[package]]
name = "nix"
version = "0.14.1"
use the nix repository again nix-rust/nix#1097 is merged so it does what we need now.
2019-07-20 19:13:12 -04:00
source = "git+https://github.com/nix-rust/nix#38de0424d77c870db85a698b01a01763f343ecac"
use nix to remove many uses of unsafe
2019-07-12 00:59:01 -04:00
dependencies = [
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
"bitflags 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
use nix to remove many uses of unsafe
2019-07-12 00:59:01 -04:00
"cc 1.0.37 (registry+https://github.com/rust-lang/crates.io-index)",
"cfg-if 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (git+https://github.com/rust-lang/libc)",
use nix to remove many uses of unsafe
2019-07-12 00:59:01 -04:00
"void 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
]
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"
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
version = "0.1.13"
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"
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 cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
version = "0.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"
dependencies = [
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
"num-complex 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"num-integer 0.1.41 (registry+https://github.com/rust-lang/crates.io-index)",
"num-iter 0.1.39 (registry+https://github.com/rust-lang/crates.io-index)",
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
"num-rational 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"num-traits 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
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 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
version = "0.2.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"
dependencies = [
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
"autocfg 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"num-traits 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
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 a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.1.41"
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"
dependencies = [
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
"autocfg 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"num-traits 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
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 a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.1.39"
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"
dependencies = [
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
"autocfg 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"num-integer 0.1.41 (registry+https://github.com/rust-lang/crates.io-index)",
"num-traits 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
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 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
version = "0.2.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"
dependencies = [
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
"autocfg 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"num-integer 0.1.41 (registry+https://github.com/rust-lang/crates.io-index)",
"num-traits 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
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-traits"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.2.8"
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 a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
dependencies = [
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
"autocfg 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
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"
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
version = "1.10.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"
dependencies = [
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"rawpointer 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"rawslice 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"unchecked-index 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
]
update deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "opaque-debug"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
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 = "openssl"
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.23"
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"
dependencies = [
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
"bitflags 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cfg-if 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
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
"foreign-types 0.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"openssl-sys 0.9.47 (registry+https://github.com/rust-lang/crates.io-index)",
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
2018-01-31 01:05:39 -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 = "openssl-probe"
version = "0.1.2"
upgrade deps
2018-01-31 01:05:39 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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 = "openssl-sys"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.9.47"
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"
dependencies = [
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
"autocfg 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cc 1.0.37 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
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
"pkg-config 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)",
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
"vcpkg 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
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 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"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"stable_deref_trait 1.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
name = "parking_lot"
update deps
2019-02-14 01:43:30 -05:00
version = "0.7.1"
update all Rust deps
2018-12-01 18:20:19 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"lock_api 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"parking_lot_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
[[package]]
name = "parking_lot"
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
version = "0.9.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"
dependencies = [
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
"lock_api 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
"parking_lot_core 0.6.1 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"rustc_version 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "parking_lot_core"
update deps
2019-02-14 01:43:30 -05:00
version = "0.4.0"
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"
dependencies = [
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"rand 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
"rustc_version 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
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
"smallvec 0.6.10 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "parking_lot_core"
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
version = "0.6.1"
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"
dependencies = [
"cfg-if 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
"cloudabi 0.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
"redox_syscall 0.1.56 (registry+https://github.com/rust-lang/crates.io-index)",
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
"rustc_version 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
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
"smallvec 0.6.10 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
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"
version = "0.3.0"
update all Rust deps
2018-12-01 18:20:19 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"crypto-mac 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
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 deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
[[package]]
name = "percent-encoding"
update dependencies
2017-11-17 02:01:09 -05:00
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "phf"
update deps
2019-02-14 01:43:30 -05:00
version = "0.7.24"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"phf_shared 0.7.24 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
]
[[package]]
name = "phf_codegen"
update deps
2019-02-14 01:43:30 -05:00
version = "0.7.24"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"phf_generator 0.7.24 (registry+https://github.com/rust-lang/crates.io-index)",
"phf_shared 0.7.24 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
]
[[package]]
name = "phf_generator"
update deps
2019-02-14 01:43:30 -05:00
version = "0.7.24"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"phf_shared 0.7.24 (registry+https://github.com/rust-lang/crates.io-index)",
"rand 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
]
[[package]]
name = "phf_shared"
update deps
2019-02-14 01:43:30 -05:00
version = "0.7.24"
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 dependencies
2017-11-17 02:01:09 -05:00
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"siphasher 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"unicase 1.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 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
version = "0.3.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 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"
version = "0.2.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"ansi_term 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
"prettytable-rs 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
"structopt 0.2.18 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "prettytable-rs"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"atty 0.2.13 (registry+https://github.com/rust-lang/crates.io-index)",
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
"csv 1.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
"encode_unicode 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)",
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
"term 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)",
"unicode-width 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "proc-macro2"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.4.30"
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"
dependencies = [
"unicode-xid 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
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]]
name = "procedural-masquerade"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
improve error messages on unparseable text protos Takes advantage of stepancheg/rust-protobuf#428
2019-07-20 19:22:24 -04:00
source = "git+https://github.com/stepancheg/rust-protobuf#c28865f0ada87733b80806eecbdcbd4906d13ee3"
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"
improve error messages on unparseable text protos Takes advantage of stepancheg/rust-protobuf#428
2019-07-20 19:22:24 -04:00
source = "git+https://github.com/stepancheg/rust-protobuf#c28865f0ada87733b80806eecbdcbd4906d13ee3"
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 = [
"protobuf 3.0.0-pre (git+https://github.com/stepancheg/rust-protobuf)",
]
[[package]]
name = "protobuf-codegen-pure"
version = "3.0.0-pre"
improve error messages on unparseable text protos Takes advantage of stepancheg/rust-protobuf#428
2019-07-20 19:22:24 -04:00
source = "git+https://github.com/stepancheg/rust-protobuf#c28865f0ada87733b80806eecbdcbd4906d13ee3"
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 = [
"protobuf 3.0.0-pre (git+https://github.com/stepancheg/rust-protobuf)",
"protobuf-codegen 3.0.0-pre (git+https://github.com/stepancheg/rust-protobuf)",
]
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
[[package]]
name = "publicsuffix"
version = "1.5.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
dependencies = [
"error-chain 0.12.1 (registry+https://github.com/rust-lang/crates.io-index)",
"idna 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"regex 1.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"url 1.7.2 (registry+https://github.com/rust-lang/crates.io-index)",
]
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
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 = "quote"
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
version = "0.6.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 a few deps
2018-08-25 01:06:14 -04:00
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"proc-macro2 0.4.30 (registry+https://github.com/rust-lang/crates.io-index)",
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
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "rand"
update deps
2019-02-14 01:43:30 -05:00
version = "0.3.23"
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"
dependencies = [
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"rand 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "rand"
update deps
2019-02-14 01:43:30 -05:00
version = "0.4.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"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"fuchsia-cprng 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
"rdrand 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
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
2018-01-31 01:05:39 -05:00
[[package]]
name = "rand"
update deps
2019-02-14 01:43:30 -05:00
version = "0.5.6"
upgrade deps
2018-01-31 01:05:39 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"cloudabi 0.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"fuchsia-cprng 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
]
update all Rust deps
2018-12-01 18:20:19 -05:00
[[package]]
name = "rand"
update deps
2019-02-14 01:43:30 -05:00
version = "0.6.5"
update all Rust deps
2018-12-01 18:20:19 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"autocfg 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"rand_chacha 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
update all Rust deps
2018-12-01 18:20:19 -05:00
"rand_hc 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_isaac 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"rand_jitter 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_os 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_pcg 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"rand_xorshift 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
update all Rust deps
2018-12-01 18:20:19 -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 = "rand"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"getrandom 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_chacha 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_core 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_hc 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
update all Rust deps
2018-12-01 18:20:19 -05:00
[[package]]
name = "rand_chacha"
update deps
2019-02-14 01:43:30 -05:00
version = "0.1.1"
update all Rust deps
2018-12-01 18:20:19 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"autocfg 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
update all Rust deps
2018-12-01 18:20:19 -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 = "rand_chacha"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"autocfg 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"c2-chacha 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_core 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
upgrade a few deps
2018-08-25 01:06:14 -04:00
[[package]]
name = "rand_core"
update deps
2019-02-14 01:43:30 -05:00
version = "0.3.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"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"rand_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "rand_core"
update deps
2019-02-14 01:43:30 -05:00
version = "0.4.0"
upgrade a few deps
2018-08-25 01:06:14 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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 = "rand_core"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"getrandom 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
update all Rust deps
2018-12-01 18:20:19 -05:00
[[package]]
name = "rand_hc"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
update all Rust deps
2018-12-01 18:20:19 -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 = "rand_hc"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"rand_core 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
update all Rust deps
2018-12-01 18:20:19 -05:00
[[package]]
name = "rand_isaac"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "rand_jitter"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.1.4"
update deps
2019-02-14 01:43:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"rand_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
]
[[package]]
name = "rand_os"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.1.3"
update deps
2019-02-14 01:43:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"cloudabi 0.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
"fuchsia-cprng 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"rand_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
"rdrand 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
update all Rust deps
2018-12-01 18:20:19 -05:00
]
[[package]]
name = "rand_pcg"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.1.2"
update all Rust deps
2018-12-01 18:20:19 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"autocfg 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"rand_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
update all Rust deps
2018-12-01 18:20:19 -05:00
]
[[package]]
name = "rand_xorshift"
update deps
2019-02-14 01:43:30 -05:00
version = "0.1.1"
update all Rust deps
2018-12-01 18:20:19 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
update all Rust deps
2018-12-01 18:20:19 -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"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "rawslice"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"rawpointer 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "rdrand"
version = "0.4.0"
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"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -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]]
name = "redox_syscall"
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
version = "0.1.56"
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"
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"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"argon2rs 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
"failure 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_os 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
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
"redox_syscall 0.1.56 (registry+https://github.com/rust-lang/crates.io-index)",
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"
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
version = "0.5.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"
dependencies = [
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
"stable_deref_trait 1.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
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]]
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 = "regex"
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
version = "1.1.9"
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 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 = [
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
"aho-corasick 0.7.4 (registry+https://github.com/rust-lang/crates.io-index)",
"memchr 2.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
"regex-syntax 0.6.8 (registry+https://github.com/rust-lang/crates.io-index)",
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
"thread_local 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
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
"utf8-ranges 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
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 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
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"
version = "0.1.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
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 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 = "regex-syntax"
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
version = "0.6.8"
upgrade deps
2018-01-31 01:05:39 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"ucd-util 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
]
[[package]]
name = "remove_dir_all"
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
version = "0.5.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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
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"
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
version = "0.9.18"
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"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"base64 0.10.1 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
"cookie 0.12.0 (registry+https://github.com/rust-lang/crates.io-index)",
"cookie_store 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
"encoding_rs 0.8.17 (registry+https://github.com/rust-lang/crates.io-index)",
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
"flate2 1.0.9 (registry+https://github.com/rust-lang/crates.io-index)",
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"http 0.1.17 (registry+https://github.com/rust-lang/crates.io-index)",
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
"hyper 0.12.33 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"hyper-tls 0.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"mime 0.3.13 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"mime_guess 2.0.0-alpha.6 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"native-tls 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
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
"serde 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_json 1.0.40 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"serde_urlencoded 0.5.5 (registry+https://github.com/rust-lang/crates.io-index)",
"time 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tokio 0.1.22 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-executor 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"tokio-io 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tokio-threadpool 0.1.15 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"tokio-timer 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)",
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
"url 1.7.2 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"uuid 0.7.4 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "ring"
update deps
2019-02-14 01:43:30 -05:00
version = "0.14.6"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cc 1.0.37 (registry+https://github.com/rust-lang/crates.io-index)",
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"spin 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)",
"untrusted 0.6.2 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
]
[[package]]
name = "rpassword"
Merge branch 'master' into auth
2018-12-01 18:27:54 -05:00
version = "2.1.0"
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"
dependencies = [
"kernel32-sys 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 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
version = "0.19.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"
dependencies = [
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
"bitflags 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"fallible-iterator 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
"fallible-streaming-iterator 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libsqlite3-sys 0.15.0 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"lru-cache 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"memchr 2.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"time 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "rust-crypto"
version = "0.2.36"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"gcc 0.3.55 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"rand 0.3.23 (registry+https://github.com/rust-lang/crates.io-index)",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
"rustc-serialize 0.3.24 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"time 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -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]]
name = "rustc-demangle"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.1.15"
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"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "rustc-serialize"
version = "0.3.24"
source = "registry+https://github.com/rust-lang/crates.io-index"
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 = "rustc_version"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"semver 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
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"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
[[package]]
name = "safemem"
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
version = "0.3.0"
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 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 = "schannel"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.1.15"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "scoped_threadpool"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
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 = "scopeguard"
version = "0.3.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"
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"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
update deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "scrypt"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"base64 0.9.3 (registry+https://github.com/rust-lang/crates.io-index)",
"byte-tools 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
"hmac 0.7.1 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"pbkdf2 0.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
"rand 0.5.6 (registry+https://github.com/rust-lang/crates.io-index)",
"sha2 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
"subtle 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "security-framework"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.3.1"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"core-foundation 0.6.4 (registry+https://github.com/rust-lang/crates.io-index)",
"core-foundation-sys 0.6.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"security-framework-sys 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "security-framework-sys"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.3.1"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"core-foundation-sys 0.6.2 (registry+https://github.com/rust-lang/crates.io-index)",
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.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 = "semver"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"semver-parser 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "semver-parser"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
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
version = "1.0.96"
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"
lose "extern crate" everywhere (Rust 2018 edition)
2018-12-28 22:53:29 -05:00
dependencies = [
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
"serde_derive 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
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"
dependencies = [
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
"serde 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
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"
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
version = "1.0.96"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"proc-macro2 0.4.30 (registry+https://github.com/rust-lang/crates.io-index)",
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
"quote 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 0.15.39 (registry+https://github.com/rust-lang/crates.io-index)",
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 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
version = "1.0.40"
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"
dependencies = [
Merge branch 'master' into auth
2018-11-20 14:10:47 -05:00
"indexmap 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"itoa 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
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
"ryu 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
"serde 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
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"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"data-encoding 2.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
"error-chain 0.11.0 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"serde 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"serde_bytes 0.10.5 (registry+https://github.com/rust-lang/crates.io-index)",
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
"serde_derive 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_json 1.0.40 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2018-12-28 11:13:03 -05:00
"toml 0.4.10 (registry+https://github.com/rust-lang/crates.io-index)",
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 a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.5.5"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"dtoa 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
"itoa 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
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
"serde 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
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
"url 1.7.2 (registry+https://github.com/rust-lang/crates.io-index)",
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 a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.8.9"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"dtoa 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
"linked-hash-map 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"serde 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"yaml-rust 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "sha2"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"block-buffer 0.7.3 (registry+https://github.com/rust-lang/crates.io-index)",
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
"digest 0.8.1 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"fake-simd 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
"opaque-debug 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
]
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
name = "signal-hook"
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
version = "0.1.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"
dependencies = [
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"signal-hook-registry 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "signal-hook-registry"
version = "1.0.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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"arc-swap 0.3.11 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
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]]
name = "siphasher"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.2.3"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "slab"
update deps
2019-02-14 01:43:30 -05:00
version = "0.4.2"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
[[package]]
name = "smallvec"
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
version = "0.6.10"
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 deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "spin"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "1.1.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"
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 = "string"
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
version = "0.2.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"
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
dependencies = [
"bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "strsim"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
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 = "strsim"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.9.2"
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"
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 = "structopt"
version = "0.2.18"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"clap 2.33.0 (registry+https://github.com/rust-lang/crates.io-index)",
"structopt-derive 0.2.18 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "structopt-derive"
version = "0.2.18"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"heck 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
"proc-macro2 0.4.30 (registry+https://github.com/rust-lang/crates.io-index)",
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
"quote 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 0.15.39 (registry+https://github.com/rust-lang/crates.io-index)",
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
2019-02-14 01:43:30 -05:00
[[package]]
name = "subtle"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
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 = "syn"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.14.9"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"proc-macro2 0.4.30 (registry+https://github.com/rust-lang/crates.io-index)",
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
"quote 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)",
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
"unicode-xid 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "syn"
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
version = "0.15.39"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"proc-macro2 0.4.30 (registry+https://github.com/rust-lang/crates.io-index)",
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
"quote 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)",
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
"unicode-xid 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "synstructure"
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.2"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"proc-macro2 0.4.30 (registry+https://github.com/rust-lang/crates.io-index)",
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
"quote 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 0.15.39 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"unicode-xid 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
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]]
name = "tempdir"
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
version = "0.3.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"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"rand 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
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
"remove_dir_all 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)",
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]]
name = "tempfile"
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
version = "3.1.0"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"cfg-if 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
"rand 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
"redox_syscall 0.1.56 (registry+https://github.com/rust-lang/crates.io-index)",
"remove_dir_all 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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"
dependencies = [
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
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"dirs 1.0.5 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
]
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
name = "term_size"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"kernel32-sys 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
]
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"
dependencies = [
"unicode-width 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "thread_local"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.3.6"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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"
update deps
2019-02-14 01:43:30 -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"
dependencies = [
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
"redox_syscall 0.1.56 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
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 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 = "tokio"
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
version = "0.1.22"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"mio 0.6.19 (registry+https://github.com/rust-lang/crates.io-index)",
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
"num_cpus 1.10.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tokio-codec 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"tokio-current-thread 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tokio-executor 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"tokio-fs 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-reactor 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tokio-sync 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"tokio-tcp 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tokio-threadpool 0.1.15 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"tokio-timer 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)",
update all Rust deps
2018-12-01 18:20:19 -05:00
"tokio-udp 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"tokio-uds 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04: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 = "tokio-buf"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
"either 1.5.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
]
upgrade a few deps
2018-08-25 01:06:14 -04:00
[[package]]
name = "tokio-codec"
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
version = "0.1.1"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"tokio-io 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
]
[[package]]
name = "tokio-current-thread"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.1.6"
upgrade a few deps
2018-08-25 01:06:14 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-executor 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "tokio-executor"
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
version = "0.1.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"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"crossbeam-utils 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
]
[[package]]
name = "tokio-fs"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.1.6"
upgrade a few deps
2018-08-25 01:06:14 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"tokio-io 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tokio-threadpool 0.1.15 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "tokio-io"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.1.12"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
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 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 = "tokio-reactor"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.1.9"
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"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"crossbeam-utils 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"mio 0.6.19 (registry+https://github.com/rust-lang/crates.io-index)",
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
"num_cpus 1.10.1 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"parking_lot 0.7.1 (registry+https://github.com/rust-lang/crates.io-index)",
"slab 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tokio-executor 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"tokio-io 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tokio-sync 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "tokio-signal"
update all Rust deps
2018-12-01 18:20:19 -05:00
version = "0.2.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"
dependencies = [
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"mio 0.6.19 (registry+https://github.com/rust-lang/crates.io-index)",
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
"mio-uds 0.6.7 (registry+https://github.com/rust-lang/crates.io-index)",
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
"signal-hook 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-executor 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"tokio-io 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-reactor 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
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 deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "tokio-sync"
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
version = "0.1.6"
update deps
2019-02-14 01:43:30 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"fnv 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05: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 = "tokio-tcp"
update deps
2019-02-14 01:43:30 -05:00
version = "0.1.3"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
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
"iovec 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"mio 0.6.19 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-reactor 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "tokio-threadpool"
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
version = "0.1.15"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"crossbeam-deque 0.7.1 (registry+https://github.com/rust-lang/crates.io-index)",
"crossbeam-queue 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"crossbeam-utils 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
"num_cpus 1.10.1 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"rand 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
"slab 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tokio-executor 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "tokio-timer"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.2.11"
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"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"crossbeam-utils 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
update deps
2019-02-14 01:43:30 -05:00
"slab 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tokio-executor 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "tokio-udp"
update all Rust deps
2018-12-01 18:20:19 -05:00
version = "0.1.3"
upgrade a few deps
2018-08-25 01:06:14 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"mio 0.6.19 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tokio-codec 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"tokio-io 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-reactor 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
]
[[package]]
name = "tokio-uds"
update deps
2019-02-14 01:43:30 -05:00
version = "0.2.5"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"iovec 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"mio 0.6.19 (registry+https://github.com/rust-lang/crates.io-index)",
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
"mio-uds 0.6.7 (registry+https://github.com/rust-lang/crates.io-index)",
update all Rust deps
2018-12-01 18:20:19 -05:00
"tokio-codec 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"tokio-io 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-reactor 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
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
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 deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
name = "toml"
update deps
2018-12-28 11:13:03 -05:00
version = "0.4.10"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"serde 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
]
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
[[package]]
name = "toml"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"serde 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade cursive to latest major version
2019-05-31 19:35:07 -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 = "try-lock"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
[[package]]
name = "try_from"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"cfg-if 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
]
update deps
2019-02-14 01:43:30 -05:00
[[package]]
name = "typenum"
version = "1.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
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 = "ucd-util"
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
version = "0.1.3"
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"
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"
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
name = "unicase"
version = "1.4.2"
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"
dependencies = [
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
"version_check 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "unicase"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "2.4.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"
dependencies = [
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
"version_check 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
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"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
version = "0.3.4"
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"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"matches 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
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"
update deps
2019-02-14 01:43:30 -05:00
version = "0.1.8"
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 deps
2019-02-14 01:43:30 -05:00
dependencies = [
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
"smallvec 0.6.10 (registry+https://github.com/rust-lang/crates.io-index)",
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"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "1.3.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"
[[package]]
name = "unicode-width"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.5"
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 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 = "unicode-xid"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "untrusted"
update deps
2019-02-14 01:43:30 -05:00
version = "0.6.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"
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"
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
version = "1.7.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"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"idna 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"matches 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"percent-encoding 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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 = "utf8-ranges"
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
version = "1.0.3"
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"
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 = "uuid"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.7.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"
dependencies = [
update deps
2019-02-14 01:43:30 -05:00
"rand 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
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
"serde 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)",
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"
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
version = "0.2.7"
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"
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 = "vec_map"
version = "0.8.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
name = "version_check"
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
version = "0.1.5"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
use nix to remove many uses of unsafe
2019-07-12 00:59:01 -04:00
[[package]]
name = "void"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
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
version = "0.2.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"
dependencies = [
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
"futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
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
"try-lock 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "winapi"
version = "0.2.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
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 a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.3.7"
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"
dependencies = [
"winapi-i686-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi-x86_64-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "winapi-build"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
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 = "ws2_32-sys"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi-build 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
name = "xi-unicode"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
[[package]]
name = "yaml-rust"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
version = "0.4.3"
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"
dependencies = [
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"linked-hash-map 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
[metadata]
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum adler32 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)" = "7e522997b529f05601e05166c07ed17789691f562762c7f3b987263d2dedee5c"
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
"checksum aho-corasick 0.7.4 (registry+https://github.com/rust-lang/crates.io-index)" = "36b7aa1ccb7d7ea3f437cf025a2ab1c47cc6c1bc9fc84918ff449def12f5e282"
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
"checksum ansi_term 0.11.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ee49baf6cb617b853aa8d93bf420db2383fab46d314482ca2803b40d5fde979b"
"checksum ansi_term 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)" = "23ac7c30002a5accbf7e8987d0632fa6de155b7c3d39d0067317a391e00a2ef6"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum arc-swap 0.3.11 (registry+https://github.com/rust-lang/crates.io-index)" = "bc4662175ead9cd84451d5c35070517777949a2ed84551764129cedb88384841"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
"checksum argon2rs 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)" = "3f67b0b6a86dae6e67ff4ca2b6201396074996379fba2b92ff649126f37cb392"
update deps
2019-02-14 01:43:30 -05:00
"checksum array-macro 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)" = "7c4ff37a25fb442a1fecfd399be0dde685558bca30fb998420532889a36852d2"
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
"checksum arrayvec 0.4.11 (registry+https://github.com/rust-lang/crates.io-index)" = "b8d73f9beda665eaa98ab9e4f7442bd4e7de6652587de55b2525e52e29c1b0ba"
"checksum atty 0.2.13 (registry+https://github.com/rust-lang/crates.io-index)" = "1803c647a3ec87095e7ae7acfca019e98de5ec9a7d01343f611cf3152ed71a90"
"checksum autocfg 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "22130e92352b948e7e82a49cdb0aa94f2211761117f29e052dd397c1ac33542b"
"checksum backtrace 0.3.33 (registry+https://github.com/rust-lang/crates.io-index)" = "88fb679bc9af8fa639198790a77f52d345fe13656c08b43afa9424c206b731c6"
"checksum backtrace-sys 0.1.31 (registry+https://github.com/rust-lang/crates.io-index)" = "82a830b4ef2d1124a711c71d263c5abdc710ef8e907bd508c88be475cebc422b"
update deps
2019-02-14 01:43:30 -05:00
"checksum base64 0.10.1 (registry+https://github.com/rust-lang/crates.io-index)" = "0b25d992356d2eb0ed82172f5248873db5560c4721f564b13cb5193bda5e668e"
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
"checksum base64 0.9.3 (registry+https://github.com/rust-lang/crates.io-index)" = "489d6c0ed21b11d038c31b6ceccca973e65d73ba3bd8ecb9a2babf5546164643"
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
"checksum bitflags 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "3d155346769a6855b86399e9bc3814ab343cd3d62c7e985113d46a0ec3c281fd"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
"checksum blake2-rfc 0.2.18 (registry+https://github.com/rust-lang/crates.io-index)" = "5d6d530bdd2d52966a6d03b7a964add7ae1a288d25214066fd4b600f0f796400"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum block-buffer 0.7.3 (registry+https://github.com/rust-lang/crates.io-index)" = "c0940dc441f31689269e10ac70eb1002a3a1d3ad1390e030043662eb7fe4688b"
"checksum block-padding 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "6d4dc3af3ee2e12f3e5d224e5e1e3d73668abbeb69e566d361f7d5563a4fdf09"
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
"checksum bstr 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "fc0662252f9bba48c251a16d16a768b9fcd959593bde07544710bce6efe60b7a"
update deps
2019-02-14 01:43:30 -05:00
"checksum byte-tools 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "e3b5ca7a04898ad4bcd41c90c5285445ff5b791899bb1b0abdd2a2aa791211d7"
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
"checksum byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)" = "a7c3dd8985a7111efc5c80b44e23ecdd8c007de8ade3b96595387e812b957cf5"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum bytes 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)" = "206fdffcfa2df7cbe15601ef46c813fce0965eb3286db6b56c583b814b51c81c"
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
"checksum c2-chacha 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "7d64d04786e0f528460fc884753cf8dddcc466be308f6026f8e355c41a0e4101"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum cc 1.0.37 (registry+https://github.com/rust-lang/crates.io-index)" = "39f75544d7bbaf57560d2168f28fd649ff9c76153874db88bdbdfd839b1a7e7d"
"checksum cfg-if 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)" = "b486ce3ccf7ffd79fdeb678eac06a9e6c09fc88d33836340becb8fffe87c5e33"
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
"checksum chrono 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)" = "77d81f58b7301084de3b958691458a53c3f7e0b1d702f77e550b6a88e3a88abe"
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
"checksum clap 2.33.0 (registry+https://github.com/rust-lang/crates.io-index)" = "5067f5bb2d80ef5d68b4c87db81601f0b75bca627bc2ef76b141d7b846a3c6d9"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum cloudabi 0.0.3 (registry+https://github.com/rust-lang/crates.io-index)" = "ddfc5b9aa5d4507acaf872de71051dfd0e309860e88966e1051e462a077aac4f"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
"checksum constant_time_eq 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "8ff012e225ce166d4422e0e78419d901719760f62ae2b7969ca6b564d1b54a9e"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum cookie 0.12.0 (registry+https://github.com/rust-lang/crates.io-index)" = "888604f00b3db336d2af898ec3c1d5d0ddf5e6d462220f2ededc33a87ac4bbd5"
"checksum cookie_store 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "46750b3f362965f197996c4448e4a0935e791bf7d6631bfce9ee0af3d24c919c"
"checksum core-foundation 0.6.4 (registry+https://github.com/rust-lang/crates.io-index)" = "25b9e03f145fd4f2bf705e07b900cd41fc636598fe5dc452fd0db1441c3f496d"
"checksum core-foundation-sys 0.6.2 (registry+https://github.com/rust-lang/crates.io-index)" = "e7ca8a5221364ef15ce201e8ed2f609fc312682a8f4e0e3d4aa5879764e0fa3b"
"checksum crc32fast 1.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ba125de2af0df55319f41944744ad91c71113bf74a4646efff39afe1f6842db1"
update deps
2019-02-14 01:43:30 -05:00
"checksum crossbeam-channel 0.3.8 (registry+https://github.com/rust-lang/crates.io-index)" = "0f0ed1a4de2235cabda8558ff5840bffb97fcb64c97827f354a451307df5f72b"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum crossbeam-deque 0.7.1 (registry+https://github.com/rust-lang/crates.io-index)" = "b18cd2e169ad86297e6bc0ad9aa679aee9daa4f19e8163860faf7c164e4f5a71"
update deps
2019-02-14 01:43:30 -05:00
"checksum crossbeam-epoch 0.7.1 (registry+https://github.com/rust-lang/crates.io-index)" = "04c9e3102cc2d69cd681412141b390abd55a362afc1540965dad0ad4d34280b4"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum crossbeam-queue 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "7c979cd6cfe72335896575c6b5688da489e420d36a27a0b9eb0c73db574b4a4b"
update deps
2019-02-14 01:43:30 -05:00
"checksum crossbeam-utils 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)" = "f8306fcef4a7b563b76b7dd949ca48f52bc1141aa067d2ea09565f3e2652aa5c"
"checksum crypto-mac 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "4434400df11d95d556bac068ddfedd482915eb18fe8bea89bc80b6e4b1c179e5"
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
"checksum cstr 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)" = "19f7a08ed4ecd7e077d4cee63937473e6f7cf57b702a9114ef41751b2cbc0f60"
"checksum cstr-macros 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "0f12dd847ec773fc98d75edba5394cb87d0f35e7ee548a4c81849ca6374b3d48"
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
"checksum csv 1.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "37519ccdfd73a75821cac9319d4fce15a81b9fcf75f951df5b9988aa3a0af87d"
"checksum csv-core 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "9b5cadb6b25c77aeff80ba701712494213f4a8418fcda2ee11b6560c3ad0bf4c"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
"checksum cursive 0.12.0 (registry+https://github.com/rust-lang/crates.io-index)" = "b7ecc7282b5361471b607c26f44148205607e26d48a2fc65bd16e7619b1ebb78"
"checksum darling 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)" = "fcfbcb0c5961907597a7d1148e3af036268f2b773886b8bb3eeb1e1281d3d3d6"
"checksum darling_core 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)" = "6afc018370c3bff3eb51f89256a6bdb18b4fdcda72d577982a14954a7a0b402c"
"checksum darling_macro 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)" = "c6d8dac1c6f1d29a41c4712b4400f878cb4fcc4c7628f298dd75038e024998d1"
update deps
2019-02-14 01:43:30 -05:00
"checksum data-encoding 2.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "f4f47ca1860a761136924ddd2422ba77b2ea54fe8cc75b9040804a0d9d32ad97"
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
"checksum digest 0.8.1 (registry+https://github.com/rust-lang/crates.io-index)" = "f3d0c8c8752312f9713efd397ff63acb9f85585afbf179282e720e7704954dd5"
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
"checksum dirs 1.0.5 (registry+https://github.com/rust-lang/crates.io-index)" = "3fd78930633bd1c6e35c4b42b1df7b0cbc6bc191146e512bb3bedf243fcc3901"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum docopt 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "7f525a586d310c87df72ebcd98009e57f1cc030c8c268305287a476beb653969"
"checksum dtoa 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)" = "ea57b42383d091c85abcc2706240b94ab2a8fa1fc81c10ff23c4de06e2a90b5e"
"checksum either 1.5.2 (registry+https://github.com/rust-lang/crates.io-index)" = "5527cfe0d098f36e3f8839852688e63c8fff1c90b2b405aef730615f9a7bcf7b"
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
"checksum encode_unicode 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)" = "90b2c9496c001e8cb61827acdefad780795c42264c137744cae6f7d9e3450abd"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum encoding_rs 0.8.17 (registry+https://github.com/rust-lang/crates.io-index)" = "4155785c79f2f6701f185eb2e6b4caf0555ec03477cb4c70db67b465311620ed"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
"checksum enum-map 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ccd9b2d5e0eb5c2ff851791e2af90ab4531b1168cfc239d1c0bf467e60ba3c89"
update deps
2019-02-14 01:43:30 -05:00
"checksum enum-map-derive 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)" = "153f6e8a8b2868e2fedf921b165f30229edcccb74d6a9bb1ccf0480ef61cd07e"
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
"checksum enum-map-internals 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "d2436d68e28d1ec1646f3e54003c6b4c4e192785532a687d52a3d2ba56c346bb"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
"checksum enumset 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "cac0a22e173f6570a7d69a2ab9e3fe79cf0dcdd0fdb162bfc932b97158f2b2a7"
"checksum enumset_derive 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "01d93b926a992a4a526c2a14e2faf734fdef5bf9d0a52ba69a2ca7d4494c284b"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
"checksum error-chain 0.11.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ff511d5dc435d703f4971bc399647c9bc38e20cb41452e3b9feb4765419ed3f3"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum error-chain 0.12.1 (registry+https://github.com/rust-lang/crates.io-index)" = "3ab49e9dcb602294bc42f9a7dfc9bc6e936fca4418ea300dbfb84fe16de0b7d9"
update deps
2019-02-14 01:43:30 -05:00
"checksum failure 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "795bd83d3abeb9220f257e597aa0080a508b27533824adf336529648f6abf7e2"
"checksum failure_derive 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "ea1063915fd7ef4309e222a5a07cf9c319fb9c7836b1f89b85458672dbb127e1"
"checksum fake-simd 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "e88a8acf291dafb59c2d96e8f59828f3838bb1a70398823ade51a84de6a6deed"
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
"checksum fallible-iterator 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "4443176a9f2c162692bd3d352d745ef9413eec5782a80d8fd6f8a1ac692a07f7"
"checksum fallible-streaming-iterator 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)" = "7360491ce676a36bf9bb3c56c1aa791658183a54d2744120f27285738d90465a"
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
"checksum flate2 1.0.9 (registry+https://github.com/rust-lang/crates.io-index)" = "550934ad4808d5d39365e5d61727309bf18b3b02c6c56b729cb92e7dd84bc3d8"
update dependencies
2017-11-17 02:01:09 -05:00
"checksum fnv 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)" = "2fad85553e09a6f881f739c29f0b00b0f01357c743266d478b68951ce23285f3"
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
"checksum foreign-types 0.3.2 (registry+https://github.com/rust-lang/crates.io-index)" = "f6f339eb8adc052cd2ca78910fda869aefa38d22d5cb648e6485e4d3fc06f3b1"
"checksum foreign-types-shared 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "00b0228411908ca8685dba7fc2cdd70ec9990a6e753e89b6ac91a84c40fbaf4b"
update deps
2019-02-14 01:43:30 -05:00
"checksum fuchsia-cprng 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "a06f77d526c1a601b7c4cdd98f54b5eaabffc14d5f2f0296febdc7f357c6d3ba"
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
"checksum fuchsia-zircon 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)" = "2e9763c69ebaae630ba35f74888db465e49e259ba1bc0eda7d06f4a067615d82"
"checksum fuchsia-zircon-sys 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)" = "3dcaa9ae7725d12cdb85b3ad99a434db70b468c09ded17e012d86b5c1010f7a7"
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
"checksum futures 0.1.28 (registry+https://github.com/rust-lang/crates.io-index)" = "45dc39533a6cae6da2b56da48edae506bb767ec07370f86f70fc062e9d435869"
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
"checksum futures-cpupool 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)" = "ab90cde24b3319636588d0c35fe03b1333857621051837ed769faefb4c2162e4"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
"checksum gcc 0.3.55 (registry+https://github.com/rust-lang/crates.io-index)" = "8f5f3913fa0bfe7ee1fd8248b6b9f42a5af4b9d65ec2dd2c3c26132b950ecfc2"
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
"checksum generic-array 0.12.3 (registry+https://github.com/rust-lang/crates.io-index)" = "c68f0274ae0e023facc3c97b2e00f076be70e254bc851d972503b328db79b2ec"
"checksum getrandom 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "e65cce4e5084b14874c4e7097f38cab54f47ee554f9194673456ea379dcc4c55"
"checksum h2 0.1.25 (registry+https://github.com/rust-lang/crates.io-index)" = "a539b63339fbbb00e081e84b6e11bd1d9634a82d91da2984a18ac74a8823f392"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
"checksum hashbrown 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "29fba9abe4742d586dfd0c06ae4f7e73a1c2d86b856933509b269d82cdf06e18"
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
"checksum heck 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "20564e78d53d2bb135c343b3f47714a56af2061f1c928fdb541dc7b9fdd94205"
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
"checksum hmac 0.7.1 (registry+https://github.com/rust-lang/crates.io-index)" = "5dcb5e64cda4c23119ab41ba960d1e170a774c8e4b9d9e6a9bc18aabf5e59695"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum http 0.1.17 (registry+https://github.com/rust-lang/crates.io-index)" = "eed324f0f0daf6ec10c474f150505af2c143f251722bf9dbd1261bd1f2ee2c1a"
"checksum http-body 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "6741c859c1b2463a423a1dbce98d418e6c3c3fc720fb0d45528657320920292d"
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
"checksum http-serve 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "1ea104cf9aa840307e26a7fb952551d3f8463809a08074334a436d2c90e49510"
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
"checksum httparse 1.3.4 (registry+https://github.com/rust-lang/crates.io-index)" = "cd179ae861f0c2e53da70d892f5f3029f9594be0c41dc5269cd371691b1dc2f9"
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
"checksum httpdate 0.3.2 (registry+https://github.com/rust-lang/crates.io-index)" = "494b4d60369511e7dea41cf646832512a94e542f68bb9c49e54518e0f468eb47"
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
"checksum hyper 0.12.33 (registry+https://github.com/rust-lang/crates.io-index)" = "7cb44cbce9d8ee4fb36e4c0ad7b794ac44ebaad924b9c8291a63215bb44c2c8f"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum hyper-tls 0.3.2 (registry+https://github.com/rust-lang/crates.io-index)" = "3a800d6aa50af4b5850b2b0f659625ce9504df908e9733b635720483be26174f"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
"checksum ident_case 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)" = "b9e0384b61958566e926dc50660321d12159025e767c18e043daf26b70104c39"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum idna 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "38f09e0f0b1fb55fdee1f17470ad800da77af5186a1a76c026b679358b7e844e"
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
"checksum indexmap 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "7e81a7c05f79578dbc15793d8b619db9ba32b4577003ef3af1a91c416798c58d"
upgrade deps
2018-01-31 01:05:39 -05:00
"checksum iovec 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "dbe6e417e7d0975db6512b90796e8ce223145ac4e33c377e4a42882a0e88bb08"
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
"checksum itertools 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)" = "5b8467d9c1cebe26feb08c640139247fac215782d35371ade9a2136ed6085358"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum itoa 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)" = "501266b7edd0174f8530248f87f99c88fbe60ca4ef3dd486835b8d8d53136f7f"
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
"checksum kernel32-sys 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "7507624b29483431c0ba2d82aece8ca6cdba9382bff4ddd0f7490560c056098d"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum lazy_static 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)" = "bc5729f27f159ddd61f4df6228e827e86643d4d3e7c32183cb30a1c08f604a14"
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
"checksum libc 0.2.60 (git+https://github.com/rust-lang/libc)" = "<none>"
"checksum libc 0.2.60 (registry+https://github.com/rust-lang/crates.io-index)" = "d44e80633f007889c7eff624b709ab43c92d708caad982295768a7b13ca3b5eb"
update deps
2019-02-14 01:43:30 -05:00
"checksum libpasta 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "31a3bd8a4714af6f88d2cd850b016ad4567770f88fa3cf0571ec197591362f99"
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
"checksum libsqlite3-sys 0.15.0 (registry+https://github.com/rust-lang/crates.io-index)" = "72b1e07fcc60484f42e246f0cf1f133940c98117c81b2cefcdf71be288069680"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum linked-hash-map 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)" = "ae91b68aebc4ddb91978b11a1b02ddd8602a05ec19002801c5666000e05e0f83"
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
"checksum lock_api 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "62ebf1391f6acad60e5c8b43706dde4582df75c06698ab44511d15016bc2442c"
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
"checksum lock_api 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "f8912e782533a93a167888781b836336a6ca5da6175c05944c86cf28c31104dc"
"checksum log 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)" = "c275b6ad54070ac2d665eef9197db647b32239c9d244bfb6f041a766d00da5b3"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum lru-cache 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "31e24f1ad8321ca0e8a1e0ac13f23cb668e6f5466c2c57319f6a5cf1cc8e3b1c"
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
"checksum maplit 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)" = "08cbb6b4fef96b6d77bfc40ec491b1690c779e77b05cd9f07f787ed376fd4c43"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum matches 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)" = "7ffc5c5338469d4d3ea17d269fa8ea3512ad247247c30bd2df69e68309ed0a08"
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
"checksum memchr 2.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "88579771288728879b57485cc7d6b07d648c9f0141eb955f8ab7f9d45394468e"
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
"checksum memmap 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "6585fd95e7bb50d6cc31e20d4cf9afb4e2ba16c5846fc76793f11218da9c475b"
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
"checksum memoffset 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "0f9dc261e2b62d7a622bf416ea3c5245cdd5d9a7fcc428c0d06804dfce1775b3"
update deps
2019-02-14 01:43:30 -05:00
"checksum mime 0.3.13 (registry+https://github.com/rust-lang/crates.io-index)" = "3e27ca21f40a310bd06d9031785f4801710d566c184a6e15bad4f1d9b65f9425"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum mime_guess 2.0.0-alpha.6 (registry+https://github.com/rust-lang/crates.io-index)" = "30de2e4613efcba1ec63d8133f344076952090c122992a903359be5a4f99c3ed"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum miniz-sys 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)" = "1e9e3ae51cea1576ceba0dde3d484d30e6e5b86dee0b2d412fe3a16a15c98202"
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
"checksum miniz_oxide 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "b6c3756d66cf286314d5f7ebe74886188a9a92f5eee68b06f31ac2b4f314c99d"
"checksum miniz_oxide_c_api 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "5b78ca5446dd9fe0dab00e058731b6b08a8c1d2b9cdb8efb10876e24e9ae2494"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum mio 0.6.19 (registry+https://github.com/rust-lang/crates.io-index)" = "83f51996a3ed004ef184e16818edc51fadffe8e7ca68be67f9dee67d84d0ff23"
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
"checksum mio-uds 0.6.7 (registry+https://github.com/rust-lang/crates.io-index)" = "966257a94e196b11bb43aca423754d87429960a768de9414f3691d6957abf125"
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
"checksum miow 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "8c1f2f3b1cf331de6896aabf6e9d55dca90356cc9960cca7eaaf408a355ae919"
specify git path to mylog
2017-03-26 03:03:24 -04:00
"checksum mylog 0.1.0 (git+https://github.com/scottlamb/mylog)" = "<none>"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum native-tls 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)" = "4b2df1a4c22fd44a62147fd8f13dd0f95c9d8ca7b2610299b2a2f9cf8964274e"
"checksum ncurses 5.99.0 (registry+https://github.com/rust-lang/crates.io-index)" = "15699bee2f37e9f8828c7b35b2bc70d13846db453f2d507713b758fabe536b82"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum net2 0.2.33 (registry+https://github.com/rust-lang/crates.io-index)" = "42550d9fb7b6684a6d404d9fa7250c2eb2646df731d1c06afc06dcee9e1bcf88"
use the nix repository again nix-rust/nix#1097 is merged so it does what we need now.
2019-07-20 19:13:12 -04:00
"checksum nix 0.14.1 (git+https://github.com/nix-rust/nix)" = "<none>"
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
"checksum nodrop 0.1.13 (registry+https://github.com/rust-lang/crates.io-index)" = "2f9667ddcc6cc8a43afc9b7917599d7216aa09c463919ea32c59ed6cac8bc945"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"checksum num 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "cf4825417e1e1406b3782a8ce92f4d53f26ec055e3622e1881ca8e9f5f9e08db"
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
"checksum num-complex 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)" = "fcb0cf31fb3ff77e6d2a6ebd6800df7fdcd106f2ad89113c9130bcd07f93dffc"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum num-integer 0.1.41 (registry+https://github.com/rust-lang/crates.io-index)" = "b85e541ef8255f6cf42bbfe4ef361305c6c135d10919ecc26126c4e5ae94bc09"
"checksum num-iter 0.1.39 (registry+https://github.com/rust-lang/crates.io-index)" = "76bd5272412d173d6bf9afdf98db8612bbabc9a7a830b7bfc9c188911716132e"
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
"checksum num-rational 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "f2885278d5fe2adc2f75ced642d52d879bffaceb5a2e0b1d4309ffdfb239b454"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum num-traits 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)" = "6ba9a427cfca2be13aa6f6403b0b7e7368fe982bfa16fccc450ce74c46cd9b32"
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
"checksum num_cpus 1.10.1 (registry+https://github.com/rust-lang/crates.io-index)" = "bcef43580c035376c0705c42792c294b66974abbfd2789b511784023f71f3273"
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
"checksum odds 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "a9a18d7081eb052145753e982d7b8de495f15f74636d0d963f09116581eab665"
update deps
2019-02-14 01:43:30 -05:00
"checksum opaque-debug 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "93f5bb2e8e8dec81642920ccff6b61f1eb94fa3020c5a325c9851ff604152409"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum openssl 0.10.23 (registry+https://github.com/rust-lang/crates.io-index)" = "97c140cbb82f3b3468193dd14c1b88def39f341f68257f8a7fe8ed9ed3f628a5"
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
"checksum openssl-probe 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "77af24da69f9d9341038eba93a073b1fdaaa1b788221b00a69bce9e762cb32de"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum openssl-sys 0.9.47 (registry+https://github.com/rust-lang/crates.io-index)" = "75bdd6dbbb4958d38e47a1d2348847ad1eb4dc205dc5d37473ae504391865acc"
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
"checksum owning_ref 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "49a4b8ea2179e6a2e27411d3bca09ca6dd630821cf6894c6c7c8467a8ee7ef13"
update deps
2019-02-14 01:43:30 -05:00
"checksum parking_lot 0.7.1 (registry+https://github.com/rust-lang/crates.io-index)" = "ab41b4aed082705d1056416ae4468b6ea99d52599ecf3169b00088d43113e337"
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
"checksum parking_lot 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)" = "f842b1982eb6c2fe34036a4fbfb06dd185a3f5c8edfaacdf7d1ea10b07de6252"
update all Rust deps
2018-12-01 18:20:19 -05:00
"checksum parking_lot_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "94c8c7923936b28d546dfd14d4472eaf34c99b14e1c973a32b3e6d4eb04298c9"
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
"checksum parking_lot_core 0.6.1 (registry+https://github.com/rust-lang/crates.io-index)" = "1a7bbaa05312363e0480e1efee133fff1a09ef4a6406b65e226b9a793c223a32"
update deps
2019-02-14 01:43:30 -05:00
"checksum pbkdf2 0.3.0 (registry+https://github.com/rust-lang/crates.io-index)" = "006c038a43a45995a9670da19e67600114740e8511d4333bf97a56e66a7542d9"
update dependencies
2017-11-17 02:01:09 -05:00
"checksum percent-encoding 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)" = "31010dd2e1ac33d5b46a5b413495239882813e0369f8ed8a5e266f173602f831"
update deps
2019-02-14 01:43:30 -05:00
"checksum phf 0.7.24 (registry+https://github.com/rust-lang/crates.io-index)" = "b3da44b85f8e8dfaec21adae67f95d93244b2ecf6ad2a692320598dcc8e6dd18"
"checksum phf_codegen 0.7.24 (registry+https://github.com/rust-lang/crates.io-index)" = "b03e85129e324ad4166b06b2c7491ae27fe3ec353af72e72cd1654c7225d517e"
"checksum phf_generator 0.7.24 (registry+https://github.com/rust-lang/crates.io-index)" = "09364cc93c159b8b06b1f4dd8a4398984503483891b0c26b867cf431fb132662"
"checksum phf_shared 0.7.24 (registry+https://github.com/rust-lang/crates.io-index)" = "234f71a15de2288bcb7e3b6515828d22af7ec8598ee6d24c3b526fa0a80b67a0"
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
"checksum pkg-config 0.3.14 (registry+https://github.com/rust-lang/crates.io-index)" = "676e8eb2b1b4c9043511a9b7bea0915320d7e502b0a079fb03f9635a5252b18c"
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
"checksum ppv-lite86 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)" = "e3cbf9f658cdb5000fcf6f362b8ea2ba154b9f146a61c7a20d647034c6b6561b"
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
"checksum prettydiff 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "5240be0c9ea1bc7887819a36264cb9475eb71c58749808e5b989c8c1fdc67acf"
"checksum prettytable-rs 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)" = "0fd04b170004fa2daccf418a7f8253aaf033c27760b5f225889024cf66d7ac2e"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum proc-macro2 0.4.30 (registry+https://github.com/rust-lang/crates.io-index)" = "cf3d2011ab5c909338f7887f4fc896d35932e29146c12c8d01da6b22a80ba759"
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
"checksum procedural-masquerade 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "9a1574a51c3fd37b26d2c0032b649d08a7d51d4cca9c41bbc5bf7118fa4509d0"
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
"checksum protobuf 3.0.0-pre (git+https://github.com/stepancheg/rust-protobuf)" = "<none>"
"checksum protobuf-codegen 3.0.0-pre (git+https://github.com/stepancheg/rust-protobuf)" = "<none>"
"checksum protobuf-codegen-pure 3.0.0-pre (git+https://github.com/stepancheg/rust-protobuf)" = "<none>"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum publicsuffix 1.5.2 (registry+https://github.com/rust-lang/crates.io-index)" = "5afecba86dcf1e4fd610246f89899d1924fe12e1e89f555eb7c7f710f3c5ad1d"
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
"checksum quote 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)" = "6ce23b6b870e8f94f81fb0a363d65d86675884b34a09043c81e5562f11c1f8e1"
update deps
2019-02-14 01:43:30 -05:00
"checksum rand 0.3.23 (registry+https://github.com/rust-lang/crates.io-index)" = "64ac302d8f83c0c1974bf758f6b041c6c8ada916fbb44a609158ca8b064cc76c"
"checksum rand 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)" = "552840b97013b1a26992c11eac34bdd778e464601a4c2054b5f0bff7c6761293"
"checksum rand 0.5.6 (registry+https://github.com/rust-lang/crates.io-index)" = "c618c47cd3ebd209790115ab837de41425723956ad3ce2e6a7f09890947cacb9"
"checksum rand 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)" = "6d71dacdc3c88c1fde3885a3be3fbab9f35724e6ce99467f7d9c5026132184ca"
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
"checksum rand 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "d47eab0e83d9693d40f825f86948aa16eff6750ead4bdffc4ab95b8b3a7f052c"
update deps
2019-02-14 01:43:30 -05:00
"checksum rand_chacha 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "556d3a1ca6600bfcbab7c7c91ccb085ac7fbbcd70e008a98742e7847f4f7bcef"
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
"checksum rand_chacha 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "e193067942ef6f485a349a113329140d0ab9e2168ce92274499bb0e9a4190d9d"
update deps
2019-02-14 01:43:30 -05:00
"checksum rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "7a6fdeb83b075e8266dcc8762c22776f6877a63111121f5f8c7411e5be7eed4b"
"checksum rand_core 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "d0e7a549d590831370895ab7ba4ea0c1b6b011d106b5ff2da6eee112615e6dc0"
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
"checksum rand_core 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)" = "615e683324e75af5d43d8f7a39ffe3ee4a9dc42c5c701167a71dc59c3a493aca"
update all Rust deps
2018-12-01 18:20:19 -05:00
"checksum rand_hc 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "7b40677c7be09ae76218dc623efbf7b18e34bced3f38883af07bb75630a21bc4"
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
"checksum rand_hc 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ca3129af7b92a17112d59ad498c6f81eaf463253766b90396d39ea7a39d6613c"
update all Rust deps
2018-12-01 18:20:19 -05:00
"checksum rand_isaac 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "ded997c9d5f13925be2a6fd7e66bf1872597f759fd9dd93513dd7e92e5a5ee08"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum rand_jitter 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "1166d5c91dc97b88d1decc3285bb0a99ed84b05cfd0bc2341bdf2d43fc41e39b"
"checksum rand_os 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "7b75f676a1e053fc562eafbb47838d67c84801e38fc1ba459e8f180deabd5071"
"checksum rand_pcg 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "abf9b09b01790cfe0364f52bf32995ea3c39f4d2dd011eac241d2914146d0b44"
update deps
2019-02-14 01:43:30 -05:00
"checksum rand_xorshift 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "cbf7e9e623549b0e21f6e97cf8ecf247c1a8fd2e8a992ae265314300b2455d5c"
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
"checksum rawpointer 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ebac11a9d2e11f2af219b8b8d833b76b1ea0e054aa0e8d8e9e4cbde353bdf019"
"checksum rawslice 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "22b23b9f57ea250c6db4b21e2897b43ff08209217ca8260469fae6c0f9ad7e25"
update deps
2019-02-14 01:43:30 -05:00
"checksum rdrand 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "678054eb77286b51581ba43620cc911abf02758c91f93f479767aed0f90458b2"
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
"checksum redox_syscall 0.1.56 (registry+https://github.com/rust-lang/crates.io-index)" = "2439c63f3f6139d1b57529d16bc3b8bb855230c8efcc5d3a896c8bea7c3b1e84"
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
"checksum redox_users 0.3.0 (registry+https://github.com/rust-lang/crates.io-index)" = "3fe5204c3a17e97dde73f285d49be585df59ed84b50a872baf416e73b62c3828"
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
"checksum reffers 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "0c3b765c544398b56cb85f1c77c6e1d963930b8b5c9678b2cc93195795a6fc32"
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
"checksum regex 1.1.9 (registry+https://github.com/rust-lang/crates.io-index)" = "d9d8297cc20bbb6184f8b45ff61c8ee6a9ac56c156cec8e38c3e5084773c44ad"
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
"checksum regex-automata 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)" = "3ed09217220c272b29ef237a974ad58515bde75f194e3ffa7e6d0bf0f3b01f86"
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
"checksum regex-syntax 0.6.8 (registry+https://github.com/rust-lang/crates.io-index)" = "9b01330cce219c1c6b2e209e5ed64ccd587ae5c67bed91c0b49eecf02ae40e21"
"checksum remove_dir_all 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)" = "4a83fa3702a688b9359eccba92d153ac33fd2e8462f9e0e3fdf155239ea7792e"
"checksum reqwest 0.9.18 (registry+https://github.com/rust-lang/crates.io-index)" = "00eb63f212df0e358b427f0f40aa13aaea010b470be642ad422bcbca2feff2e4"
update deps
2019-02-14 01:43:30 -05:00
"checksum ring 0.14.6 (registry+https://github.com/rust-lang/crates.io-index)" = "426bc186e3e95cac1e4a4be125a4aca7e84c2d616ffc02244eef36e2a60a093c"
Merge branch 'master' into auth
2018-12-01 18:27:54 -05:00
"checksum rpassword 2.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "d37473170aedbe66ffa3ad3726939ba677d83c646ad4fd99e5b4bc38712f45ec"
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
"checksum rusqlite 0.19.0 (registry+https://github.com/rust-lang/crates.io-index)" = "6ebca2e7e3deb7241b7fa5929c088548c590728b1b740c479594c23f813eb8a7"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
"checksum rust-crypto 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)" = "f76d05d3993fd5f4af9434e8e436db163a12a9d40e1a58a726f27a01dfd12a2a"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum rustc-demangle 0.1.15 (registry+https://github.com/rust-lang/crates.io-index)" = "a7f4dccf6f4891ebcc0c39f9b6eb1a83b9bf5d747cb439ec6fba4f3b977038af"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
"checksum rustc-serialize 0.3.24 (registry+https://github.com/rust-lang/crates.io-index)" = "dcf128d1287d2ea9d80910b5f1120d0b8eede3fbf1abe91c40d39ea7d51e6fda"
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
"checksum rustc_version 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)" = "138e3e0acb6c9fb258b19b67cb8abd63c00679d2851805ea151465464fe9030a"
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
"checksum ryu 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "c92464b447c0ee8c4fb3824ecc8383b81717b9f1e74ba2e72540aef7b9f82997"
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
"checksum safemem 0.3.0 (registry+https://github.com/rust-lang/crates.io-index)" = "8dca453248a96cb0749e36ccdfe2b0b4e54a61bfef89fb97ec621eb8e0a93dd9"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum schannel 0.1.15 (registry+https://github.com/rust-lang/crates.io-index)" = "f2f6abf258d99c3c1c5c2131d99d064e94b7b3dd5f416483057f308fea253339"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
"checksum scoped_threadpool 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)" = "1d51f5df5af43ab3f1360b429fa5e0152ac5ce8c0bd6485cae490332e96846a8"
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
"checksum scopeguard 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)" = "94258f53601af11e6a49f722422f6e3425c52b06245a5cf9bc09908b174f5e27"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum scopeguard 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "b42e15e59b18a828bbf5c58ea01debb36b9b096346de35d941dcb89009f24a0d"
update deps
2019-02-14 01:43:30 -05:00
"checksum scrypt 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "656c79d0e90d0ab28ac86bf3c3d10bfbbac91450d3f190113b4e76d9fec3cfdd"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum security-framework 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "eee63d0f4a9ec776eeb30e220f0bc1e092c3ad744b2a379e3993070364d3adc2"
"checksum security-framework-sys 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "9636f8989cbf61385ae4824b98c1aaa54c994d7d8b41f11c601ed799f0549a56"
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
"checksum semver 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)" = "1d7eb9ef2c18661902cc47e535f9bc51b78acd254da71d375c2f6720d9a40403"
"checksum semver-parser 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "388a1df253eca08550bef6c72392cfe7c30914bf41df5269b68cbd6ff8f570a3"
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
"checksum serde 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)" = "793b5e49d3ac0e38a8f02935712854273c9c660b60f80e9d07be8f86090c5eca"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum serde_bytes 0.10.5 (registry+https://github.com/rust-lang/crates.io-index)" = "defbb8a83d7f34cc8380751eeb892b825944222888aff18996ea7901f24aec88"
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
"checksum serde_derive 1.0.96 (registry+https://github.com/rust-lang/crates.io-index)" = "fbf64bb3bd01d6ea6317a448971bcdf88ff4929708285b9adadb64a23f63e53c"
"checksum serde_json 1.0.40 (registry+https://github.com/rust-lang/crates.io-index)" = "051c49229f282f7c6f3813f8286cc1e3323e8051823fce42c7ea80fe13521704"
initial db layer work for authentication (#26)
2018-11-02 02:25:06 -04:00
"checksum serde_mcf 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "6a8e71f1e2ddef2fb0451a9fcf2d975d05aac7fb6e452de01da13bff1b4c46cd"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum serde_urlencoded 0.5.5 (registry+https://github.com/rust-lang/crates.io-index)" = "642dd69105886af2efd227f75a520ec9b44a820d65bc133a9131f7d229fd165a"
"checksum serde_yaml 0.8.9 (registry+https://github.com/rust-lang/crates.io-index)" = "38b08a9a90e5260fe01c6480ec7c811606df6d3a660415808c3c3fa8ed95b582"
update deps
2019-02-14 01:43:30 -05:00
"checksum sha2 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)" = "7b4d8bfd0e469f417657573d8451fb33d16cfe0989359b93baf3a1ffc639543d"
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
"checksum signal-hook 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)" = "4f61c4d59f3aaa9f61bba6450a9b80ba48362fd7d651689e7a10c453b1f6dc68"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum signal-hook-registry 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)" = "cded4ffa32146722ec54ab1f16320568465aa922aa9ab4708129599740da85d7"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum siphasher 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)" = "0b8de496cf83d4ed58b6be86c3a275b8602f6ffe98d3024a869e124147a9a3ac"
update deps
2019-02-14 01:43:30 -05:00
"checksum slab 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)" = "c111b5bd5695e56cffe5129854aa230b39c93a305372fdbb2668ca2394eea9f8"
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
"checksum smallvec 0.6.10 (registry+https://github.com/rust-lang/crates.io-index)" = "ab606a9c5e214920bb66c458cd7be8ef094f813f20fe77a54cc7dbfff220d4b7"
update deps
2019-02-14 01:43:30 -05:00
"checksum spin 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)" = "44363f6f51401c34e7be73db0db371c04705d35efbe9f7d6082e03a921a32c55"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum stable_deref_trait 1.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "dba1a27d3efae4351c8051072d619e3ade2820635c3958d826bfea39d59b54c8"
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
"checksum string 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "d24114bfcceb867ca7f71a0d3fe45d45619ec47a6fbfa98cb14e14250bfa5d6d"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
"checksum strsim 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "bb4f380125926a99e52bc279241539c018323fab05ad6368b56f93d9369ff550"
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
"checksum strsim 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)" = "8ea5119cdb4c55b55d432abb513a0429384878c15dde60cc77b1c99de1a95a6a"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum strsim 0.9.2 (registry+https://github.com/rust-lang/crates.io-index)" = "032c03039aae92b350aad2e3779c352e104d919cb192ba2fabbd7b831ce4f0f6"
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
"checksum structopt 0.2.18 (registry+https://github.com/rust-lang/crates.io-index)" = "16c2cdbf9cc375f15d1b4141bc48aeef444806655cd0e904207edc8d68d86ed7"
"checksum structopt-derive 0.2.18 (registry+https://github.com/rust-lang/crates.io-index)" = "53010261a84b37689f9ed7d395165029f9cc7abb9f56bbfe86bee2597ed25107"
update deps
2019-02-14 01:43:30 -05:00
"checksum subtle 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "2d67a5a62ba6e01cb2192ff309324cb4875d0c451d55fe2319433abe7a05a8ee"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum syn 0.14.9 (registry+https://github.com/rust-lang/crates.io-index)" = "261ae9ecaa397c42b960649561949d69311f08eeaea86a65696e6e46517cf741"
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
"checksum syn 0.15.39 (registry+https://github.com/rust-lang/crates.io-index)" = "b4d960b829a55e56db167e861ddb43602c003c7be0bee1d345021703fac2fb7c"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum synstructure 0.10.2 (registry+https://github.com/rust-lang/crates.io-index)" = "02353edf96d6e4dc81aea2d8490a7e9db177bf8acb0e951c24940bf866cb313f"
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
"checksum tempdir 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)" = "15f2b5fb00ccdf689e0149d1b1b3c03fead81c2b37735d812fa8bddbbf41b6d8"
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
"checksum tempfile 3.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "7a6e24d9338a0a5be79593e2fa15a648add6138caa803e2d5bc782c371732ca9"
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
"checksum term 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)" = "edd106a334b7657c10b7c540a0106114feadeb4dc314513e97df481d5d966f42"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"checksum term_size 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "9e5b9a66db815dcfd2da92db471106457082577c3c278d4138ab3e3b4e189327"
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
"checksum textwrap 0.11.0 (registry+https://github.com/rust-lang/crates.io-index)" = "d326610f408c7a4eb6f51c37c330e496b08506c9457c9d34287ecc38809fb060"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum thread_local 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)" = "c6b53e329000edc2b34dbe8545fd20e55a333362d0a321909685a19bd28c3f1b"
update deps
2019-02-14 01:43:30 -05:00
"checksum time 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)" = "db8dcfca086c1143c9270ac42a2bbd8a7ee477b78ac8e45b19abfb0cbede4b6f"
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
"checksum tokio 0.1.22 (registry+https://github.com/rust-lang/crates.io-index)" = "5a09c0b5bb588872ab2f09afa13ee6e9dac11e10a0ec9e8e3ba39a5a5d530af6"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum tokio-buf 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "8fb220f46c53859a4b7ec083e41dec9778ff0b1851c0942b211edb89e0ccdc46"
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
"checksum tokio-codec 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "5c501eceaf96f0e1793cf26beb63da3d11c738c4a943fdf3746d81d64684c39f"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum tokio-current-thread 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "d16217cad7f1b840c5a97dfb3c43b0c871fef423a6e8d2118c604e843662a443"
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
"checksum tokio-executor 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)" = "0f27ee0e6db01c5f0b2973824547ce7e637b2ed79b891a9677b0de9bd532b6ac"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum tokio-fs 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "3fe6dc22b08d6993916647d108a1a7d15b9cd29c4f4496c62b92c45b5041b7af"
"checksum tokio-io 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)" = "5090db468dad16e1a7a54c8c67280c5e4b544f3d3e018f0b913b400261f85926"
"checksum tokio-reactor 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)" = "6af16bfac7e112bea8b0442542161bfc41cbfa4466b580bdda7d18cb88b911ce"
update all Rust deps
2018-12-01 18:20:19 -05:00
"checksum tokio-signal 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)" = "dd6dc5276ea05ce379a16de90083ec80836440d5ef8a6a39545a3207373b8296"
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
"checksum tokio-sync 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "2162248ff317e2bc713b261f242b69dbb838b85248ed20bb21df56d60ea4cae7"
update deps
2019-02-14 01:43:30 -05:00
"checksum tokio-tcp 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "1d14b10654be682ac43efee27401d792507e30fd8d26389e1da3b185de2e4119"
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
"checksum tokio-threadpool 0.1.15 (registry+https://github.com/rust-lang/crates.io-index)" = "90ca01319dea1e376a001e8dc192d42ebde6dd532532a5bad988ac37db365b19"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum tokio-timer 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)" = "f2106812d500ed25a4f38235b9cae8f78a09edf43203e16e59c3b769a342a60e"
update all Rust deps
2018-12-01 18:20:19 -05:00
"checksum tokio-udp 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "66268575b80f4a4a710ef83d087fdfeeabdce9b74c797535fbac18a2cb906e92"
update deps
2019-02-14 01:43:30 -05:00
"checksum tokio-uds 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)" = "037ffc3ba0e12a0ab4aca92e5234e0dedeb48fddf6ccd260f1f150a36a9f2445"
update deps
2018-12-28 11:13:03 -05:00
"checksum toml 0.4.10 (registry+https://github.com/rust-lang/crates.io-index)" = "758664fc71a3a69038656bee8b6be6477d2a6c315a6b81f7081f591bffa4111f"
upgrade cursive to latest major version
2019-05-31 19:35:07 -04:00
"checksum toml 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "b8c96d7873fa7ef8bdeb3a9cda3ac48389b4154f32b9803b4bc26220b677b039"
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
"checksum try-lock 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "e604eb7b43c06650e854be16a2a03155743d3752dd1c943f6829e26b7a36e382"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum try_from 0.3.2 (registry+https://github.com/rust-lang/crates.io-index)" = "283d3b89e1368717881a9d51dad843cc435380d8109c9e47d38780a324698d8b"
update deps
2019-02-14 01:43:30 -05:00
"checksum typenum 1.10.0 (registry+https://github.com/rust-lang/crates.io-index)" = "612d636f949607bdf9b123b4a6f6d966dedf3ff669f7f045890d3a4a73948169"
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
"checksum ucd-util 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "535c204ee4d8434478593480b8f86ab45ec9aae0e83c568ca81abf0fd0e88f86"
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
"checksum unchecked-index 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "eeba86d422ce181a719445e51872fa30f1f7413b62becb52e95ec91aa262d85c"
update dependencies
2017-11-17 02:01:09 -05:00
"checksum unicase 1.4.2 (registry+https://github.com/rust-lang/crates.io-index)" = "7f4765f83163b74f957c797ad9253caf97f103fb064d3999aea9568d09fc8a33"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum unicase 2.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "a84e5511b2a947f3ae965dcb29b13b7b1691b6e7332cf5dbc1744138d5acb7f6"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"checksum unicode-bidi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)" = "49f2bd0c6468a8230e1db229cff8029217cf623c767ea5d60bfbd42729ea54d5"
update deps
2019-02-14 01:43:30 -05:00
"checksum unicode-normalization 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)" = "141339a08b982d942be2ca06ff8b076563cbe223d1befd5450716790d44e2426"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum unicode-segmentation 1.3.0 (registry+https://github.com/rust-lang/crates.io-index)" = "1967f4cdfc355b37fd76d2a954fb2ed3871034eb4f26d60537d88795cfc332a9"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum unicode-width 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "882386231c45df4700b275c7ff55b6f3698780a650026380e72dabe76fa46526"
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
"checksum unicode-xid 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "fc72304796d0818e357ead4e000d19c9c174ab23dc11093ac919054d20a6a7fc"
update deps
2019-02-14 01:43:30 -05:00
"checksum untrusted 0.6.2 (registry+https://github.com/rust-lang/crates.io-index)" = "55cd1f4b4e96b46aeb8d4855db4a7a9bd96eeeb5c6a1ab54593328761642ce2f"
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
"checksum url 1.7.2 (registry+https://github.com/rust-lang/crates.io-index)" = "dd4e7c0d531266369519a4aa4f399d748bd37043b00bde1e4ff1f60a120b355a"
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
"checksum utf8-ranges 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)" = "9d50aa7650df78abf942826607c62468ce18d9019673d4a2ebe1865dbb96ffde"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum uuid 0.7.4 (registry+https://github.com/rust-lang/crates.io-index)" = "90dbc611eb48397705a6b0f6e917da23ae517e4d127123d2cf7674206627d32a"
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
"checksum vcpkg 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)" = "33dd455d0f96e90a75803cfeb7f948768c08d70a6de9a8d2362461935698bf95"
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
"checksum vec_map 0.8.1 (registry+https://github.com/rust-lang/crates.io-index)" = "05c78687fb1a80548ae3250346c3db86a80a7cdd77bda190189f2d0a0987c81a"
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
"checksum version_check 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "914b1a6776c4c929a602fafd8bc742e06365d4bcbe48c30f9cca5824f70dc9dd"
use nix to remove many uses of unsafe
2019-07-12 00:59:01 -04:00
"checksum void 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "6a02e4885ed3bc0f2de90ea6dd45ebcbb66dacffe03547fadbb0eeae2770887d"
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
"checksum want 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "b6395efa4784b027708f7451087e647ec73cc74f5d9bc2e418404248d679a230"
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
"checksum winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)" = "167dc9d6949a9b857f3451275e911c3f44255842c1f7a76f33c55103a909087a"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)" = "f10e386af2b13e47c89e7236a7a14a086791a2b88ebad6df9bf42040195cf770"
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
"checksum winapi-build 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "2d315eee3b34aca4797b2da6b13ed88266e6d612562a0c46390af8299fc699bc"
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
"checksum winapi-i686-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
"checksum winapi-x86_64-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
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
"checksum ws2_32-sys 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "d59cefebd0c892fa2dd6de581e937301d8552cb44489cdff035c6187cb63fa5e"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"checksum xi-unicode 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "12ea8eda4b1eb72f02d148402e23832d56a33f55d8c1b2d5bcdde91d79d47cb1"
update a few deps cursive & rusqlite are more significant; I'll do those separately
2019-05-31 18:08:49 -04:00
"checksum yaml-rust 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)" = "65923dd1784f44da1d2c3dbbc5e822045628c590ba72123e1c73d3c230c4434d"