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

1846 lines
86 KiB
Plaintext
Raw Normal View History

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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.6.6"
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 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
"memchr 2.0.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
]
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
name = "arc-swap"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "array-macro"
version = "1.0.2"
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"
version = "0.4.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"nodrop 0.1.12 (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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.3.9"
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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"backtrace-sys 0.1.24 (registry+https://github.com/rust-lang/crates.io-index)",
"cfg-if 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"rustc-demangle 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.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 = "backtrace-sys"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.24"
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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"cc 1.0.22 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.9.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
"byteorder 1.2.4 (registry+https://github.com/rust-lang/crates.io-index)",
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"safemem 0.2.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 = "bitflags"
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.9.1"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
name = "bitflags"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "1.0.4"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "build_const"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.2.1"
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
[[package]]
name = "byteorder"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "1.2.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 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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.4.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 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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"byteorder 1.2.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 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 (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
[[package]]
name = "cc"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "1.0.22"
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"
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"
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.4.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"num-integer 0.1.39 (registry+https://github.com/rust-lang/crates.io-index)",
"num-traits 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
"time 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"bitflags 1.0.4 (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 dependencies
2017-11-17 02:01:09 -05:00
name = "core-foundation"
version = "0.2.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"
dependencies = [
update dependencies
2017-11-17 02:01:09 -05:00
"core-foundation-sys 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"libc 0.2.43 (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 dependencies
2017-11-17 02:01:09 -05:00
name = "core-foundation-sys"
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
version = "0.2.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"libc 0.2.43 (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 = "crc"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "1.8.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"build_const 0.2.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
]
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
name = "crossbeam-channel"
version = "0.2.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"crossbeam-epoch 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)",
"crossbeam-utils 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)",
"parking_lot 0.6.3 (registry+https://github.com/rust-lang/crates.io-index)",
"rand 0.5.5 (registry+https://github.com/rust-lang/crates.io-index)",
"smallvec 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
[[package]]
name = "crossbeam-deque"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.6.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"crossbeam-epoch 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)",
"crossbeam-utils 0.5.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
]
[[package]]
name = "crossbeam-epoch"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.5.2"
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 = [
"arrayvec 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"cfg-if 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"crossbeam-utils 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)",
"lazy_static 1.1.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)",
]
[[package]]
name = "crossbeam-utils"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.5.0"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
version = "0.9.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 cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"crossbeam-channel 0.2.4 (registry+https://github.com/rust-lang/crates.io-index)",
"enum-map 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
"enumset 0.3.11 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.4 (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)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"ncurses 5.94.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 dependencies
2017-11-17 02:01:09 -05:00
"owning_ref 0.3.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
"signal-hook 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
"term_size 0.3.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
"toml 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"unicode-segmentation 1.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
"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
]
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "1.0.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"lazy_static 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"regex 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
"serde 1.0.75 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_derive 1.0.75 (registry+https://github.com/rust-lang/crates.io-index)",
"strsim 0.7.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 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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.4.3"
update several dependencies I left serde alone because uuid hasn't been updated for the new version.
2017-01-27 23:58:04 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update 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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.8.6"
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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"cfg-if 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
]
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
name = "enum-map"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"array-macro 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
"enum-map-derive 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
"reexport-proc-macro 1.0.5 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "enum-map-derive"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"proc-macro2 0.4.13 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 0.6.8 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 0.14.9 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "enumset"
version = "0.3.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"num-traits 0.2.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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"backtrace 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)",
"failure_derive 0.1.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
]
[[package]]
name = "failure_derive"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"proc-macro2 0.4.13 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 0.6.8 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 0.14.9 (registry+https://github.com/rust-lang/crates.io-index)",
"synstructure 0.9.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
]
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
[[package]]
name = "flate2"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "1.0.2"
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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
"miniz-sys 0.1.10 (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 = "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"
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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"bitflags 1.0.4 (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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.23"
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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"futures 0.1.23 (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
"num_cpus 1.8.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 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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.10"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"bytes 0.4.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
"fnv 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"itoa 0.4.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
]
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"
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
version = "0.0.1"
upgrade a few deps
2018-08-25 01:06:14 -04:00
source = "git+https://github.com/scottlamb/http-serve?rev=b361ee#b361ee6dd5afc6a30eaf1d54be072310a1f04778"
add a basic Javascript UI The Javascript is pretty amateurish I'm sure but at least it's something to iterate from. It's already much more pleasant for browsing through videos in several ways: * more responsive to load only a day at a time rather than 90+ days * much easier to see the same time segment on several cameras * more pleasant to have the videos load as a popup rather than a link that blows away your position in an enormous list * exposes the fancier .mp4 generation options: splitting at lengths other than the default, trimming to an arbitrary start and end time, including a subtitle track with timestamps. There's a slight regression in functionality: I didn't match the former top-level page which showed how much camera used of its disk allocation and the total duration of video. This is exposed in the JSON API, so it shouldn't be too hard to add back.
2017-10-22 00:54:27 -04:00
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"flate2 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
"futures 0.1.23 (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)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"http 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
"hyper 0.11.27 (registry+https://github.com/rust-lang/crates.io-index)",
"mime 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)",
"smallvec 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
"time 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)",
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
"unicase 2.1.0 (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"
upgrade a few deps
2018-08-25 01:06:14 -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"
[[package]]
name = "hyper"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.11.27"
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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"base64 0.9.2 (registry+https://github.com/rust-lang/crates.io-index)",
"bytes 0.4.9 (registry+https://github.com/rust-lang/crates.io-index)",
"futures 0.1.23 (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)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"http 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
"httparse 1.3.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)",
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
"language-tags 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"log 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
"mime 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)",
"net2 0.2.33 (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)",
upgrade deps
2018-01-31 01:05:39 -05:00
"relay 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"time 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-core 0.1.17 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 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
"tokio-proto 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-service 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"unicase 2.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"want 0.0.4 (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
]
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.4"
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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
"hyper 0.11.27 (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
"native-tls 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"tokio-core 0.1.17 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 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
"tokio-service 0.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
"tokio-tls 0.1.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
]
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
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)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"unicode-normalization 0.1.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 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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"libc 0.2.43 (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
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.4.2"
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)",
]
[[package]]
name = "language-tags"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "lazy_static"
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.2.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "lazy_static"
upgrade a few deps
2018-08-25 01:06:14 -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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
dependencies = [
"version_check 0.1.4 (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
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
[[package]]
name = "lazycell"
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.6.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"
use the latest libc crate to build on OS X
2017-09-22 09:20:40 -04:00
[[package]]
name = "libc"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.2.43"
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 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 = "libflate"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.16"
update dependencies * The mylog update fixes a couple bad bugs. * Otherwise, just keep up with the Rust ecosystem.
2017-06-11 15:57:55 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"adler32 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
"byteorder 1.2.4 (registry+https://github.com/rust-lang/crates.io-index)",
"crc 1.8.1 (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
]
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"
upgrade a few deps
2018-08-25 01:06:14 -04: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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"cc 1.0.22 (registry+https://github.com/rust-lang/crates.io-index)",
"pkg-config 0.3.13 (registry+https://github.com/rust-lang/crates.io-index)",
"vcpkg 0.2.6 (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 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.4.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 a few deps
2018-08-25 01:06:14 -04:00
[[package]]
name = "lock_api"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"owning_ref 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
"scopeguard 0.3.3 (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 = "log"
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.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"
upgrade deps, including http-serve bugfix This was including the wrong Content-Encoding: header on gzipped json responses, so Chrome wouldn't understand them at all.
2018-01-30 19:51:32 -05:00
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"log 0.4.4 (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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.4.4"
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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"cfg-if 0.1.5 (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 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.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"
dependencies = [
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
"linked-hash-map 0.4.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"
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 = "2.0.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"libc 0.2.43 (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 = "memmap"
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.6.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
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.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
]
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.3.9"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"unicase 2.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"mime 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)",
"phf 0.7.22 (registry+https://github.com/rust-lang/crates.io-index)",
"phf_codegen 0.7.22 (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"
version = "0.1.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"cc 1.0.22 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
name = "mio"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.6.15"
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)",
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
"lazycell 0.6.0 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.4 (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)",
"slab 0.4.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
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "mio-uds"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.6.6"
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)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"mio 0.6.15 (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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"failure 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
"parking_lot 0.6.3 (registry+https://github.com/rust-lang/crates.io-index)",
"time 0.1.40 (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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"failure 0.1.2 (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)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"lazy_static 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.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
"lru-cache 0.1.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
"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)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"openssl 0.10.11 (registry+https://github.com/rust-lang/crates.io-index)",
"parking_lot 0.6.3 (registry+https://github.com/rust-lang/crates.io-index)",
"protobuf 2.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
"regex 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
"rusqlite 0.14.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
"tempdir 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"time 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)",
"uuid 0.6.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
]
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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"cc 1.0.22 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
"pkg-config 0.3.13 (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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"byteorder 1.2.4 (registry+https://github.com/rust-lang/crates.io-index)",
"bytes 0.4.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
"cursive 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"docopt 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
"failure 0.1.2 (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)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"futures 0.1.23 (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)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"http 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
"http-serve 0.0.1 (git+https://github.com/scottlamb/http-serve?rev=b361ee)",
"hyper 0.11.27 (registry+https://github.com/rust-lang/crates.io-index)",
"lazy_static 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.4 (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
"memmap 0.6.2 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"mime 0.3.9 (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)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"openssl 0.10.11 (registry+https://github.com/rust-lang/crates.io-index)",
"parking_lot 0.6.3 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"reffers 0.4.2 (git+https://github.com/diwic/reffers-rs)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"regex 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
"reqwest 0.8.8 (registry+https://github.com/rust-lang/crates.io-index)",
"rusqlite 0.14.0 (registry+https://github.com/rust-lang/crates.io-index)",
"serde 1.0.75 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_derive 1.0.75 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_json 1.0.26 (registry+https://github.com/rust-lang/crates.io-index)",
"smallvec 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
"tempdir 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"time 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-core 0.1.17 (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
"tokio-signal 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"url 1.7.1 (registry+https://github.com/rust-lang/crates.io-index)",
"uuid 0.6.5 (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"
upgrade deps
2018-01-31 01:05:39 -05:00
source = "git+https://github.com/scottlamb/mylog#448368771548f8843b626be5f046cdb4dd965902"
use my own logging package This supports formats that I find more useful; one that mimicks the Google glog package, and one that is similar but adapted for the systemd journal.
2017-03-26 03:01:48 -04:00
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"chrono 0.4.5 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
"parking_lot 0.5.5 (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"
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.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 = [
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
"lazy_static 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"libc 0.2.43 (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
"openssl 0.9.24 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"schannel 0.1.13 (registry+https://github.com/rust-lang/crates.io-index)",
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"security-framework 0.1.16 (registry+https://github.com/rust-lang/crates.io-index)",
"security-framework-sys 0.1.16 (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)",
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "5.94.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 a few deps
2018-08-25 01:06:14 -04:00
"cc 1.0.22 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"pkg-config 0.3.13 (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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"cfg-if 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.5 (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 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"
version = "0.1.12"
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 cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"num-complex 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"num-integer 0.1.39 (registry+https://github.com/rust-lang/crates.io-index)",
"num-iter 0.1.37 (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-rational 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"num-traits 0.2.5 (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 cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
version = "0.2.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 a few deps
2018-08-25 01:06:14 -04:00
"num-traits 0.2.5 (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"
upgrade a few deps
2018-08-25 01:06:14 -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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"num-traits 0.2.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 = "num-iter"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.37"
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
"num-integer 0.1.39 (registry+https://github.com/rust-lang/crates.io-index)",
"num-traits 0.2.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
]
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 cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
version = "0.2.1"
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"num-integer 0.1.39 (registry+https://github.com/rust-lang/crates.io-index)",
"num-traits 0.2.5 (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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.2.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"
[[package]]
name = "num_cpus"
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 = "1.8.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"libc 0.2.43 (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 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.9.24"
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 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
"bitflags 0.9.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
"foreign-types 0.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"lazy_static 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"openssl-sys 0.9.35 (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 = "openssl"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.10.11"
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
"bitflags 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
"cfg-if 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
"foreign-types 0.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"lazy_static 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"openssl-sys 0.9.35 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -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 = "openssl-sys"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.9.35"
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
"cc 1.0.22 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"pkg-config 0.3.13 (registry+https://github.com/rust-lang/crates.io-index)",
"vcpkg 0.2.6 (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 = "owning_ref"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"stable_deref_trait 1.1.1 (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
]
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
name = "parking_lot"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.5.5"
update dependencies
2017-11-17 02:01:09 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"owning_ref 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"parking_lot_core 0.2.14 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "parking_lot"
version = "0.6.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"lock_api 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
"parking_lot_core 0.2.14 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -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 = "parking_lot_core"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.2.14"
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
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"rand 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)",
"smallvec 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.5 (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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.7.22"
update dependencies
2017-11-17 02:01:09 -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
"phf_shared 0.7.22 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
]
[[package]]
name = "phf_codegen"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.7.22"
update dependencies
2017-11-17 02:01:09 -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
"phf_generator 0.7.22 (registry+https://github.com/rust-lang/crates.io-index)",
"phf_shared 0.7.22 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
]
[[package]]
name = "phf_generator"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.7.22"
update dependencies
2017-11-17 02:01:09 -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
"phf_shared 0.7.22 (registry+https://github.com/rust-lang/crates.io-index)",
"rand 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
]
[[package]]
name = "phf_shared"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.7.22"
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.3.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"
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.4.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"
dependencies = [
"unicode-xid 0.1.0 (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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "2.0.4"
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"
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.6.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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
dependencies = [
"proc-macro2 0.4.13 (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]]
upgrade a few deps
2018-08-25 01:06:14 -04:00
name = "rand"
version = "0.3.22"
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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"fuchsia-zircon 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"rand 0.4.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
]
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.4.3"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.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
]
upgrade deps
2018-01-31 01:05:39 -05:00
[[package]]
name = "rand"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.5.5"
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)",
upgrade deps
2018-01-31 01:05:39 -05:00
"fuchsia-zircon 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_core 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
]
upgrade a few deps
2018-08-25 01:06:14 -04:00
[[package]]
name = "rand_core"
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]]
name = "redox_syscall"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.40"
update several dependencies I left serde alone because uuid hasn't been updated for the new version.
2017-01-27 23:58:04 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
name = "reexport-proc-macro"
version = "1.0.5"
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 = "reffers"
version = "0.4.2"
upgrade a few deps
2018-08-25 01:06:14 -04:00
source = "git+https://github.com/diwic/reffers-rs#49a4d754b6a5dd441ce959ad6287fe3f4b295419"
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
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 = "regex"
upgrade a few deps
2018-08-25 01:06:14 -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"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"aho-corasick 0.6.6 (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
"memchr 2.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"regex-syntax 0.6.2 (registry+https://github.com/rust-lang/crates.io-index)",
"thread_local 0.3.6 (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
"utf8-ranges 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "regex-syntax"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.6.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 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 = [
"ucd-util 0.1.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
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
[[package]]
name = "relay"
upgrade deps
2018-01-31 01:05:39 -05:00
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
]
[[package]]
name = "remove_dir_all"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.5.1"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"winapi 0.3.5 (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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.8.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"bytes 0.4.9 (registry+https://github.com/rust-lang/crates.io-index)",
"encoding_rs 0.8.6 (registry+https://github.com/rust-lang/crates.io-index)",
"futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
"hyper 0.11.27 (registry+https://github.com/rust-lang/crates.io-index)",
"hyper-tls 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
"libflate 0.1.16 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
"mime_guess 2.0.0-alpha.6 (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
"native-tls 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"serde 1.0.75 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_json 1.0.26 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_urlencoded 0.5.3 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-core 0.1.17 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 0.1.8 (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
"tokio-tls 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"url 1.7.1 (registry+https://github.com/rust-lang/crates.io-index)",
"uuid 0.6.5 (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
]
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.14.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"bitflags 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
"libsqlite3-sys 0.9.3 (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
"lru-cache 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"time 0.1.40 (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
]
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.9"
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
[[package]]
name = "ryu"
version = "0.2.5"
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"
version = "0.2.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 = "schannel"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.13"
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
"lazy_static 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.5 (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 = "scoped-tls"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.2"
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"
[[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"
[[package]]
name = "security-framework"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
version = "0.1.16"
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 = [
"core-foundation 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
"core-foundation-sys 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"security-framework-sys 0.1.16 (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 deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
version = "0.1.16"
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 = [
"core-foundation-sys 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"libc 0.2.43 (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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "1.0.75"
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"
[[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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "1.0.75"
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
"proc-macro2 0.4.13 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 0.6.8 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 0.14.9 (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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "1.0.26"
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
"itoa 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
"ryu 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
"serde 1.0.75 (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 = "serde_urlencoded"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.5.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"dtoa 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)",
"itoa 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
"serde 1.0.75 (registry+https://github.com/rust-lang/crates.io-index)",
"url 1.7.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
]
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
[[package]]
name = "signal-hook"
version = "0.1.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"arc-swap 0.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
]
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"
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 = "slab"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
name = "slab"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.4.1"
update dependencies
2017-11-17 02:01:09 -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 = "smallvec"
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"
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
[[package]]
name = "smallvec"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.6.5"
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
dependencies = [
"unreachable 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
update dependencies * The mylog update fixes a couple bad bugs. * Otherwise, just keep up with the Rust ecosystem.
2017-06-11 15:57:55 -04:00
name = "stable_deref_trait"
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"
[[package]]
name = "strsim"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.7.0"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update 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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"proc-macro2 0.4.13 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 0.6.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
"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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.9.0"
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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"proc-macro2 0.4.13 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 0.6.8 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 0.14.9 (registry+https://github.com/rust-lang/crates.io-index)",
"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
]
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 = "take"
version = "0.1.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 = "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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"rand 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)",
"remove_dir_all 0.5.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
]
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)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.2.8 (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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"lazy_static 1.1.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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"redox_syscall 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.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
]
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
"mio 0.6.15 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-codec 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-current-thread 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-executor 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-fs 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-reactor 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-tcp 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-threadpool 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-timer 0.2.6 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-udp 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-uds 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "tokio-codec"
version = "0.1.0"
update deps I want to use hyper::server::Request::bytes_mut(), so an update is needed. Update everything at once. Most notably, the http-serve update starts using the http crate types for some things. (More to come.)
2018-04-06 18:54:52 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"bytes 0.4.9 (registry+https://github.com/rust-lang/crates.io-index)",
"futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 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
]
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-core"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.17"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"bytes 0.4.9 (registry+https://github.com/rust-lang/crates.io-index)",
"futures 0.1.23 (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 a few deps
2018-08-25 01:06:14 -04:00
"log 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
"mio 0.6.15 (registry+https://github.com/rust-lang/crates.io-index)",
"scoped-tls 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-executor 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-reactor 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-timer 0.2.6 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "tokio-current-thread"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-executor 0.1.4 (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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.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"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "tokio-fs"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-threadpool 0.1.6 (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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.8"
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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"bytes 0.4.9 (registry+https://github.com/rust-lang/crates.io-index)",
"futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.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
]
[[package]]
name = "tokio-proto"
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.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"futures 0.1.23 (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
"log 0.3.9 (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 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
"rand 0.3.22 (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
"slab 0.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
"smallvec 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
"take 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"tokio-core 0.1.17 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 0.1.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
"tokio-service 0.1.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
[[package]]
name = "tokio-reactor"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.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"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"crossbeam-utils 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)",
"futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
"lazy_static 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
"mio 0.6.15 (registry+https://github.com/rust-lang/crates.io-index)",
"num_cpus 1.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
"parking_lot 0.6.3 (registry+https://github.com/rust-lang/crates.io-index)",
"slab 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-executor 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 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
]
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-service"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"futures 0.1.23 (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 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.1.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"mio 0.6.15 (registry+https://github.com/rust-lang/crates.io-index)",
"mio-uds 0.6.6 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-core 0.1.17 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.5 (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-tcp"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"bytes 0.4.9 (registry+https://github.com/rust-lang/crates.io-index)",
"futures 0.1.23 (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)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"mio 0.6.15 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-reactor 0.1.4 (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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.6"
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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"crossbeam-deque 0.6.1 (registry+https://github.com/rust-lang/crates.io-index)",
"crossbeam-utils 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)",
"futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.4 (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
"num_cpus 1.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"rand 0.5.5 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-executor 0.1.4 (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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.2.6"
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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"crossbeam-utils 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)",
"futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
"slab 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-executor 0.1.4 (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 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]]
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
name = "tokio-tls"
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.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"
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
dependencies = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"futures 0.1.23 (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
"native-tls 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade a few deps
2018-08-25 01:06:14 -04:00
"tokio-core 0.1.17 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"bytes 0.4.9 (registry+https://github.com/rust-lang/crates.io-index)",
"futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
"mio 0.6.15 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-codec 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-reactor 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "tokio-uds"
version = "0.2.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"bytes 0.4.9 (registry+https://github.com/rust-lang/crates.io-index)",
"futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
"iovec 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
"mio 0.6.15 (registry+https://github.com/rust-lang/crates.io-index)",
"mio-uds 0.6.6 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-reactor 0.1.4 (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 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.4.6"
update dependencies
2017-11-17 02:01:09 -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
"serde 1.0.75 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
]
upgrade a few deps
2018-08-25 01:06:14 -04:00
[[package]]
name = "try-lock"
version = "0.1.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"
version = "0.1.1"
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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"version_check 0.1.4 (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 dependencies
2017-11-17 02:01:09 -05:00
version = "2.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 = [
upgrade a few deps
2018-08-25 01:06:14 -04:00
"version_check 0.1.4 (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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.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"
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
[[package]]
name = "unicode-segmentation"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "1.2.1"
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[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"
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 = "unreachable"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
version = "1.0.0"
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 = [
"void 1.0.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 = "url"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "1.7.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 = [
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"
version = "1.0.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 = "uuid"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.6.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
"cfg-if 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"rand 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)",
"serde 1.0.75 (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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.2.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"
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
name = "version_check"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.1.4"
update dependencies
2017-11-17 02:01:09 -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 = "void"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade a few deps
2018-08-25 01:06:14 -04:00
[[package]]
name = "want"
version = "0.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
"try-lock 0.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
[[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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
version = "0.3.5"
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"
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"
"checksum aho-corasick 0.6.6 (registry+https://github.com/rust-lang/crates.io-index)" = "c1c6d463cbe7ed28720b5b489e7c083eeb8f90d08be2a0d6bb9e1ffea9ce1afa"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"checksum arc-swap 0.3.0 (registry+https://github.com/rust-lang/crates.io-index)" = "f753d9b7c861f9f426fdb10479e35ffef7eaa4359d7c3595610645459df8849a"
"checksum array-macro 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "8b1b1a00de235e9f2cc0e650423dc249d875c116a5934188c08fdd0c02d840ef"
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 arrayvec 0.4.7 (registry+https://github.com/rust-lang/crates.io-index)" = "a1e964f9e24d588183fcb43503abda40d288c8657dfc27311516ce2f05675aef"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum backtrace 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)" = "89a47830402e9981c5c41223151efcced65a0510c13097c769cede7efb34782a"
"checksum backtrace-sys 0.1.24 (registry+https://github.com/rust-lang/crates.io-index)" = "c66d56ac8dabd07f6aacdaf633f4b8262f5b3601a810a0dcddffd5c22c69daa0"
"checksum base64 0.9.2 (registry+https://github.com/rust-lang/crates.io-index)" = "85415d2594767338a74a30c1d370b2f3262ec1b4ed2d7bba5b3faf4de40467d9"
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 bitflags 0.9.1 (registry+https://github.com/rust-lang/crates.io-index)" = "4efd02e230a02e18f92fc2735f44597385ed02ad8f831e7c1c1156ee5e1ab3a5"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum bitflags 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)" = "228047a76f468627ca71776ecdebd732a3423081fcf5125585bcd7c49886ce12"
"checksum build_const 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "39092a32794787acd8525ee150305ff051b0aa6cc2abaf193924f5ab05425f39"
"checksum byteorder 1.2.4 (registry+https://github.com/rust-lang/crates.io-index)" = "8389c509ec62b9fe8eca58c502a0acaf017737355615243496cde4994f8fa4f9"
"checksum bytes 0.4.9 (registry+https://github.com/rust-lang/crates.io-index)" = "e178b8e0e239e844b083d5a0d4a156b2654e67f9f80144d48398fcd736a24fb8"
"checksum cc 1.0.22 (registry+https://github.com/rust-lang/crates.io-index)" = "4a6007c146fdd28d4512a794b07ffe9d8e89e6bf86e2e0c4ddff2e1fb54a0007"
"checksum cfg-if 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "0c4e7bb64a8ebb0d856483e1e682ea3422f883c5f5615a90d51a2c82fe87fdd3"
"checksum chrono 0.4.5 (registry+https://github.com/rust-lang/crates.io-index)" = "e48d85528df61dc964aa43c5f6ca681a19cfa74939b2348d204bd08a981f2fb0"
"checksum cloudabi 0.0.3 (registry+https://github.com/rust-lang/crates.io-index)" = "ddfc5b9aa5d4507acaf872de71051dfd0e309860e88966e1051e462a077aac4f"
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 core-foundation 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)" = "25bfd746d203017f7d5cbd31ee5d8e17f94b6521c7af77ece6c9e4b2d4b16c67"
"checksum core-foundation-sys 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)" = "065a5d7ffdcbc8fa145d6f0746f3555025b9097a9e9cda59f7467abae670c78d"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum crc 1.8.1 (registry+https://github.com/rust-lang/crates.io-index)" = "d663548de7f5cca343f1e0a48d14dcfb0e9eb4e079ec58883b7251539fa10aeb"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"checksum crossbeam-channel 0.2.4 (registry+https://github.com/rust-lang/crates.io-index)" = "6c0a94250b0278d7fc5a894c3d276b11ea164edc8bf8feb10ca1ea517b44a649"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum crossbeam-deque 0.6.1 (registry+https://github.com/rust-lang/crates.io-index)" = "3486aefc4c0487b9cb52372c97df0a48b8c249514af1ee99703bf70d2f2ceda1"
"checksum crossbeam-epoch 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)" = "30fecfcac6abfef8771151f8be4abc9e4edc112c2bcb233314cafde2680536e9"
"checksum crossbeam-utils 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)" = "677d453a17e8bd2b913fa38e8b9cf04bcdbb5be790aa294f2389661d72036015"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"checksum cursive 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)" = "e7024f124e4645e285879af7b54ea466dabfed91d16c3d8049df7a4e4c36d8bd"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum docopt 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)" = "d60c92df70dfaaabecc14b409fd79f55ba0f247780529db1d73bfa601e1d3ac0"
"checksum dtoa 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)" = "6d301140eb411af13d3115f9a562c85cc6b541ade9dfa314132244aaee7489dd"
"checksum encoding_rs 0.8.6 (registry+https://github.com/rust-lang/crates.io-index)" = "2a91912d6f37c6a8fef8a2316a862542d036f13c923ad518b5aca7bcaac7544c"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"checksum enum-map 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)" = "caa1769f019df7ccd8f9a741d2d608309688d0f1bd8a8747c14ac993660c761c"
"checksum enum-map-derive 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "f915c8ef505ce27b6fa51515463938aa2e9135081fefc93aef786539a646a365"
"checksum enumset 0.3.11 (registry+https://github.com/rust-lang/crates.io-index)" = "81193cae36d896445dae43f89be4fd6a171aad6bd674acb7e7074d50bbce6940"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum failure 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "7efb22686e4a466b1ec1a15c2898f91fa9cb340452496dca654032de20ff95b9"
"checksum failure_derive 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "946d0e98a50d9831f5d589038d2ca7f8f455b1c21028c0db0e84116a12696426"
"checksum flate2 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "37847f133aae7acf82bb9577ccd8bda241df836787642654286e79679826a54b"
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"
"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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum futures 0.1.23 (registry+https://github.com/rust-lang/crates.io-index)" = "884dbe32a6ae4cd7da5c6db9b78114449df9953b8d490c9d7e1b51720b922c62"
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum http 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)" = "dca621d0fa606a5ff2850b6e337b57ad6137ee4d67e940449643ff45af6874c6"
"checksum http-serve 0.0.1 (git+https://github.com/scottlamb/http-serve?rev=b361ee)" = "<none>"
"checksum httparse 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)" = "7b6288d7db100340ca12873fd4d08ad1b8f206a9457798dfb17c018a33fee540"
"checksum hyper 0.11.27 (registry+https://github.com/rust-lang/crates.io-index)" = "34a590ca09d341e94cddf8e5af0bbccde205d5fbc2fa3c09dd67c7f85cea59d7"
"checksum hyper-tls 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "ffb1bd5e518d3065840ab315dbbf44e4420e5f7d80e2cb93fa6ffffc50522378"
"checksum idna 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "38f09e0f0b1fb55fdee1f17470ad800da77af5186a1a76c026b679358b7e844e"
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum itoa 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)" = "5adb58558dcd1d786b5f0bd15f3226ee23486e24b7b58304b60f64dc68e62606"
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"
"checksum language-tags 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "a91d884b6667cd606bb5a69aa0c99ba811a115fc68915e7056ec08a46e93199a"
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 lazy_static 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)" = "76f033c7ad61445c5b347c7382dd1237847eb1bce590fe50365dcb33d546be73"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum lazy_static 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ca488b89a5657b0a2ecd45b95609b3e848cf1755da332a0da46e2b2b1cb371a7"
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 lazycell 0.6.0 (registry+https://github.com/rust-lang/crates.io-index)" = "a6f08839bc70ef4a3fe1d566d5350f519c5912ea86be0df1740a7d247c7fc0ef"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum libc 0.2.43 (registry+https://github.com/rust-lang/crates.io-index)" = "76e3a3ef172f1a0b9a9ff0dd1491ae5e6c948b94479a3021819ba7d860c8645d"
"checksum libflate 0.1.16 (registry+https://github.com/rust-lang/crates.io-index)" = "7d4b4c7aff5bac19b956f693d0ea0eade8066deb092186ae954fa6ba14daab98"
"checksum libsqlite3-sys 0.9.3 (registry+https://github.com/rust-lang/crates.io-index)" = "d3711dfd91a1081d2458ad2d06ea30a8755256e74038be2ad927d94e1c955ca8"
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 linked-hash-map 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)" = "7860ec297f7008ff7a1e3382d7f7e1dcd69efc94751a2284bafc3d013c2aa939"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum lock_api 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "949826a5ccf18c1b3a7c3d57692778d21768b79e46eb9dd07bfc4c2160036c54"
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 log 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)" = "e19e8d5c34a3e0e2223db8e060f9e8264aeeb5c5fc64a4ee9965c062211c024b"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum log 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)" = "cba860f648db8e6f269df990180c2217f333472b4a6e901e97446858487971e2"
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 lru-cache 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "4d06ff7ff06f729ce5f4e227876cb88d10bc59cd4ae1e09fbb2bde15c850dc21"
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"
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 memchr 2.0.1 (registry+https://github.com/rust-lang/crates.io-index)" = "796fba70e76612589ed2ce7f45282f5af869e0fdd7cc6199fa1aa1f1d591ba9d"
"checksum memmap 0.6.2 (registry+https://github.com/rust-lang/crates.io-index)" = "e2ffa2c986de11a9df78620c01eeaaf27d94d3ff02bf81bfcca953102dd0c6ff"
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum mime 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)" = "4b082692d3f6cf41b453af73839ce3dfc212c4411cbb2441dff80a716e38bd79"
"checksum mime_guess 2.0.0-alpha.6 (registry+https://github.com/rust-lang/crates.io-index)" = "30de2e4613efcba1ec63d8133f344076952090c122992a903359be5a4f99c3ed"
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
"checksum miniz-sys 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)" = "609ce024854aeb19a0ef7567d348aaa5a746b32fb72e336df7fcc16869d7e2b4"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum mio 0.6.15 (registry+https://github.com/rust-lang/crates.io-index)" = "4fcfcb32d63961fb6f367bfd5d21e4600b92cd310f71f9dca25acae196eb1560"
"checksum mio-uds 0.6.6 (registry+https://github.com/rust-lang/crates.io-index)" = "84c7b5caa3a118a6e34dbac36504503b1e8dc5835e833306b9d6af0e05929f79"
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>"
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 native-tls 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "f74dbadc8b43df7864539cedb7bc91345e532fdd913cfdc23ad94f4d2d40fbc0"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum ncurses 5.94.0 (registry+https://github.com/rust-lang/crates.io-index)" = "4a02f0da600c09fa2e5fd6479093ba8a4b21f4ed5bed3b6ddc26583b50d31319"
"checksum net2 0.2.33 (registry+https://github.com/rust-lang/crates.io-index)" = "42550d9fb7b6684a6d404d9fa7250c2eb2646df731d1c06afc06dcee9e1bcf88"
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 nodrop 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)" = "9a2228dca57108069a5262f2ed8bd2e82496d2e074a06d1ccc7ce1687b6ae0a2"
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"
"checksum num-complex 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "68de83578789e0fbda3fa923035be83cf8bfd3b30ccfdecd5aa89bf8601f408e"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum num-integer 0.1.39 (registry+https://github.com/rust-lang/crates.io-index)" = "e83d528d2677f0518c570baf2b7abdcf0cd2d248860b68507bdcb3e91d4c0cea"
"checksum num-iter 0.1.37 (registry+https://github.com/rust-lang/crates.io-index)" = "af3fdbbc3291a5464dc57b03860ec37ca6bf915ed6ee385e7c6c052c422b2124"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"checksum num-rational 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "4e96f040177bb3da242b5b1ecf3f54b5d5af3efbbfb18608977a5d2767b22f10"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum num-traits 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)" = "630de1ef5cc79d0cdd78b7e33b81f083cbfe90de0f4b2b2f07f905867c70e9fe"
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 num_cpus 1.8.0 (registry+https://github.com/rust-lang/crates.io-index)" = "c51a3322e4bca9d212ad9a158a02abc6934d005490c054a2778df73a70aa0a30"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum openssl 0.10.11 (registry+https://github.com/rust-lang/crates.io-index)" = "6c24d3508b4fb6da175c10baac54c578b33f09c89ae90c6fe9788b3b4768efdc"
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 openssl 0.9.24 (registry+https://github.com/rust-lang/crates.io-index)" = "a3605c298474a3aa69de92d21139fb5e2a81688d308262359d85cdd0d12a7985"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum openssl-sys 0.9.35 (registry+https://github.com/rust-lang/crates.io-index)" = "912f301a749394e1025d9dcddef6106ddee9252620e6d0a0e5f8d0681de9b129"
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 owning_ref 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)" = "cdf84f41639e037b484f93433aa3897863b561ed65c6e59c7073d7c561710f37"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum parking_lot 0.5.5 (registry+https://github.com/rust-lang/crates.io-index)" = "d4d05f1349491390b1730afba60bb20d55761bef489a954546b58b4b34e1e2ac"
"checksum parking_lot 0.6.3 (registry+https://github.com/rust-lang/crates.io-index)" = "69376b761943787ebd5cc85a5bc95958651a22609c5c1c2b65de21786baec72b"
"checksum parking_lot_core 0.2.14 (registry+https://github.com/rust-lang/crates.io-index)" = "4db1a8ccf734a7bce794cc19b3df06ed87ab2f3907036b693c68f56b4d4537fa"
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum phf 0.7.22 (registry+https://github.com/rust-lang/crates.io-index)" = "7d37a244c75a9748e049225155f56dbcb98fe71b192fd25fd23cb914b5ad62f2"
"checksum phf_codegen 0.7.22 (registry+https://github.com/rust-lang/crates.io-index)" = "4e4048fe7dd7a06b8127ecd6d3803149126e9b33c7558879846da3a63f734f2b"
"checksum phf_generator 0.7.22 (registry+https://github.com/rust-lang/crates.io-index)" = "05a079dd052e7b674d21cb31cbb6c05efd56a2cd2827db7692e2f1a507ebd998"
"checksum phf_shared 0.7.22 (registry+https://github.com/rust-lang/crates.io-index)" = "c2261d544c2bb6aa3b10022b0be371b9c7c64f762ef28c6f5d4f1ef6d97b5930"
"checksum pkg-config 0.3.13 (registry+https://github.com/rust-lang/crates.io-index)" = "104630aa1c83213cbc76db0703630fcb0421dac3585063be4ce9a8a2feeaa745"
"checksum proc-macro2 0.4.13 (registry+https://github.com/rust-lang/crates.io-index)" = "ee5697238f0d893c7f0ecc59c0999f18d2af85e424de441178bcacc9f9e6cf67"
"checksum protobuf 2.0.4 (registry+https://github.com/rust-lang/crates.io-index)" = "128a4f37a2df739a567a8685b17f54aa19b9c3c4a6a5b8731e97a419b3db451c"
"checksum quote 0.6.8 (registry+https://github.com/rust-lang/crates.io-index)" = "dd636425967c33af890042c483632d33fa7a18f19ad1d7ea72e8998c6ef8dea5"
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 rand 0.3.22 (registry+https://github.com/rust-lang/crates.io-index)" = "15a732abf9d20f0ad8eeb6f909bf6868722d9a06e1e50802b6a70351f40b4eb1"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum rand 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)" = "8356f47b32624fef5b3301c1be97e5944ecdd595409cc5da11d05f211db6cfbd"
"checksum rand 0.5.5 (registry+https://github.com/rust-lang/crates.io-index)" = "e464cd887e869cddcae8792a4ee31d23c7edd516700695608f5b98c67ee0131c"
"checksum rand_core 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "edecf0f94da5551fc9b492093e30b041a891657db7940ee221f9d2f66e82eef2"
"checksum redox_syscall 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)" = "c214e91d3ecf43e9a4e41e578973adeb14b474f2bee858742d127af75a0112b1"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"checksum reexport-proc-macro 1.0.5 (registry+https://github.com/rust-lang/crates.io-index)" = "438fe63770eda15baf98e30b4d27ada49b932866307fa04fec24d9043fe63324"
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 reffers 0.4.2 (git+https://github.com/diwic/reffers-rs)" = "<none>"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum regex 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)" = "3d8c9f33201f46669484bacc312b00e7541bed6aaf296dffe2bb4e0ac6b8ce2a"
"checksum regex-syntax 0.6.2 (registry+https://github.com/rust-lang/crates.io-index)" = "747ba3b235651f6e2f67dfa8bcdcd073ddb7c243cb21c442fc12395dfcac212d"
upgrade deps
2018-01-31 01:05:39 -05:00
"checksum relay 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "1576e382688d7e9deecea24417e350d3062d97e32e45d70b1cde65994ff1489a"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum remove_dir_all 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "3488ba1b9a2084d38645c4c08276a1752dcbf2c7130d74f1569681ad5d2799c5"
"checksum reqwest 0.8.8 (registry+https://github.com/rust-lang/crates.io-index)" = "738769ec83daf6c1929dc9dae7d69ed3779b55ae5c356e989dcd3aa677d8486e"
"checksum rusqlite 0.14.0 (registry+https://github.com/rust-lang/crates.io-index)" = "c9d9118f1ce84d8d0b67f9779936432fb42bb620cef2122409d786892cce9a3c"
"checksum rustc-demangle 0.1.9 (registry+https://github.com/rust-lang/crates.io-index)" = "bcfe5b13211b4d78e5c2cadfebd7769197d95c639c35a50057eb4c05de811395"
"checksum ryu 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)" = "e7c066b8e2923f05d4718a06d2622f189ff362bc642bfade6c6629f0440f3827"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"checksum safemem 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "e27a8b19b835f7aea908818e871f5cc3a5a186550c30773be987e155e8163d8f"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum schannel 0.1.13 (registry+https://github.com/rust-lang/crates.io-index)" = "dc1fabf2a7b6483a141426e1afd09ad543520a77ac49bd03c286e7696ccfd77f"
"checksum scoped-tls 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "332ffa32bf586782a3efaeb58f127980944bbc8c4d6913a86107ac2a5ab24b28"
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 deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"checksum security-framework 0.1.16 (registry+https://github.com/rust-lang/crates.io-index)" = "dfa44ee9c54ce5eecc9de7d5acbad112ee58755239381f687e564004ba4a2332"
"checksum security-framework-sys 0.1.16 (registry+https://github.com/rust-lang/crates.io-index)" = "5421621e836278a0b139268f36eee0dc7e389b784dc3f79d8f11aabadf41bead"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum serde 1.0.75 (registry+https://github.com/rust-lang/crates.io-index)" = "22d340507cea0b7e6632900a176101fea959c7065d93ba555072da90aaaafc87"
"checksum serde_derive 1.0.75 (registry+https://github.com/rust-lang/crates.io-index)" = "234fc8b737737b148ccd625175fc6390f5e4dacfdaa543cb93a3430d984a9119"
"checksum serde_json 1.0.26 (registry+https://github.com/rust-lang/crates.io-index)" = "44dd2cfde475037451fa99b7e5df77aa3cfd1536575fa8e7a538ab36dcde49ae"
"checksum serde_urlencoded 0.5.3 (registry+https://github.com/rust-lang/crates.io-index)" = "aaed41d9fb1e2f587201b863356590c90c1157495d811430a0c0325fe8169650"
update cursive from 0.7 to 0.9
2018-08-25 01:14:03 -04:00
"checksum signal-hook 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "bfc9a251608ddaef559cd5b08b539cbda8c36d0efe0506f9a864765d75dbd665"
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"
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 slab 0.3.0 (registry+https://github.com/rust-lang/crates.io-index)" = "17b4fcaed89ab08ef143da37bc52adbcc04d4a69014f4c1208d6b51f0c47bc23"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum slab 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)" = "5f9776d6b986f77b35c6cf846c11ad986ff128fe0b2b63a3628e3755e8d3102d"
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 smallvec 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "4c8cbcd6df1e117c2210e13ab5109635ad68a929fcbb8964dc965b76cb5ee013"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum smallvec 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)" = "153ffa32fd170e9944f7e0838edf824a754ec4c1fc64746fcc9fe1f8fa602e5d"
"checksum stable_deref_trait 1.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "dba1a27d3efae4351c8051072d619e3ade2820635c3958d826bfea39d59b54c8"
"checksum strsim 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "bb4f380125926a99e52bc279241539c018323fab05ad6368b56f93d9369ff550"
"checksum syn 0.14.9 (registry+https://github.com/rust-lang/crates.io-index)" = "261ae9ecaa397c42b960649561949d69311f08eeaea86a65696e6e46517cf741"
"checksum synstructure 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)" = "85bb9b7550d063ea184027c9b8c20ac167cd36d3e06b3a40bceb9d746dc1a7b7"
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 take 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "b157868d8ac1f56b64604539990685fa7611d8fa9e5476cf0c02cf34d32917c5"
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 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"
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"
"checksum time 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)" = "d825be0eb33fda1a7e68012d51e9c7f451dc1a69391e7fdc197060bb8c56667b"
"checksum tokio 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)" = "fbb6a6e9db2702097bfdfddcb09841211ad423b86c75b5ddaca1d62842ac492c"
"checksum tokio-codec 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "881e9645b81c2ce95fcb799ded2c29ffb9f25ef5bef909089a420e5961dd8ccb"
"checksum tokio-core 0.1.17 (registry+https://github.com/rust-lang/crates.io-index)" = "aeeffbbb94209023feaef3c196a41cbcdafa06b4a6f893f68779bb5e53796f71"
"checksum tokio-current-thread 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "8fdfb899688ac16f618076bd09215edbfda0fd5dfecb375b6942636cb31fa8a7"
"checksum tokio-executor 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "84823b932d566bc3c6aa644df4ca36cb38593c50b7db06011fd4e12e31e4047e"
"checksum tokio-fs 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "b5cbe4ca6e71cb0b62a66e4e6f53a8c06a6eefe46cc5f665ad6f274c9906f135"
"checksum tokio-io 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)" = "8d6cc2de7725863c86ac71b0b9068476fec50834f055a243558ef1655bbd34cb"
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 tokio-proto 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "8fbb47ae81353c63c487030659494b295f6cb6576242f907f203473b191b0389"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum tokio-reactor 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "df6a7ea7d65e0fc1398de28959de8be96909986a7d2e01d4f86d3433dfb91aed"
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 tokio-service 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "24da22d077e0f15f55162bdbdc661228c1581892f52074fb242678d015b45162"
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 tokio-signal 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "e8f46863230f9a05cf52d173721ec391b9c5782a2465f593029922b8782b9ffe"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum tokio-tcp 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "5b4c329b47f071eb8a746040465fa751bd95e4716e98daef6a9b4e434c17d565"
"checksum tokio-threadpool 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "a5758cecb6e0633cea5d563ac07c975e04961690b946b04fd84e7d6445a8f6af"
"checksum tokio-timer 0.2.6 (registry+https://github.com/rust-lang/crates.io-index)" = "d03fa701f9578a01b7014f106b47f0a363b4727a7f3f75d666e312ab7acbbf1c"
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 tokio-tls 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "772f4b04e560117fe3b0a53e490c16ddc8ba6ec437015d91fa385564996ed913"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum tokio-udp 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "da941144b816d0dcda4db3a1ba87596e4df5e860a72b70783fe435891f80601c"
"checksum tokio-uds 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "424c1ed15a0132251813ccea50640b224c809d6ceafb88154c1a8775873a0e89"
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 toml 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)" = "a0263c6c02c4db6c8f7681f9fd35e90de799ebd4cfdeab77a38f4ff6b3d8c0d9"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum try-lock 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ee2aa4715743892880f70885373966c83d73ef1b0838a664ef0c76fffd35e7c2"
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 ucd-util 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "fd2be2d6639d0f8fe6cdda291ad456e23629558d466e2789d2c3e9892bda285d"
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"
"checksum unicase 2.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "284b6d3db520d67fbe88fd778c21510d1b0ba4a551e5d0fbb023d33405f6de8a"
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum unicode-normalization 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)" = "6a0180bc61fc5a987082bfa111f4cc95c4caff7f9799f3e46df09163a937aa25"
"checksum unicode-segmentation 1.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "aa6024fc12ddfd1c6dbc14a80fa2324d4568849869b779f6bd37e5e4c03344d1"
"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 (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"checksum unreachable 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "382810877fe448991dfc7f0dd6e3ae5d58088fd0ea5e35189655f84e6814fa56"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum url 1.7.1 (registry+https://github.com/rust-lang/crates.io-index)" = "2a321979c09843d272956e73700d12c4e7d3d92b2ee112b31548aef0d4efc5a6"
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
"checksum utf8-ranges 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "662fab6525a98beff2921d7f61a39e7d59e0b425ebc7d0d9e66d316e55124122"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum uuid 0.6.5 (registry+https://github.com/rust-lang/crates.io-index)" = "e1436e58182935dcd9ce0add9ea0b558e8a87befe01c1a301e6020aeb0876363"
"checksum vcpkg 0.2.6 (registry+https://github.com/rust-lang/crates.io-index)" = "def296d3eb3b12371b2c7d0e83bfe1403e4db2d7a0bba324a12b21c4ee13143d"
"checksum version_check 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "7716c242968ee87e5542f8021178248f267f295a5c4803beae8b8b7fd9bc6051"
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
"checksum void 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "6a02e4885ed3bc0f2de90ea6dd45ebcbb66dacffe03547fadbb0eeae2770887d"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum want 0.0.4 (registry+https://github.com/rust-lang/crates.io-index)" = "a05d9d966753fa4b5c8db73fcab5eed4549cfe0e1e4e66911e5564a0085c35d1"
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"
upgrade a few deps
2018-08-25 01:06:14 -04:00
"checksum winapi 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)" = "773ef9dcc5f24b7d850d0ff101e542ff24c3b090a9768e03ff889fdef41f00fd"
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"