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

1472 lines
67 KiB
Plaintext
Raw Normal View History

update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
[[package]]
name = "adler32"
version = "1.0.2"
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 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.4"
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
]
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"
version = "0.3.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"backtrace-sys 0.1.16 (registry+https://github.com/rust-lang/crates.io-index)",
"cfg-if 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
"rustc-demangle 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "backtrace-sys"
version = "0.1.16"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"cc 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.36 (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]]
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 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.9.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 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
"byteorder 1.2.1 (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"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "build_const"
version = "0.2.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 = "byteorder"
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.2.1"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade to 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 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.4.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"
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 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
"byteorder 1.2.1 (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 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.0.4"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
update dependencies * The mylog update fixes a couple bad bugs. * Otherwise, just keep up with the Rust ecosystem.
2017-06-11 15:57:55 -04:00
name = "cfg-if"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
version = "0.1.2"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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 deps
2018-01-31 01:05:39 -05:00
version = "0.4.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 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 0.1.41 (registry+https://github.com/rust-lang/crates.io-index)",
"time 0.1.39 (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 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
"libc 0.2.36 (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 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
"libc 0.2.36 (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 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.7.0"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update dependencies
2017-11-17 02:01:09 -05:00
"build_const 0.2.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
]
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
[[package]]
name = "cursive"
upgrade 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.7.5"
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
"log 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)",
"maplit 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
"ncurses 5.91.0 (registry+https://github.com/rust-lang/crates.io-index)",
"num 0.1.41 (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)",
"toml 0.4.5 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies * The mylog update fixes a couple bad bugs. * Otherwise, just keep up with the Rust ecosystem.
2017-06-11 15:57:55 -04:00
"unicode-segmentation 1.2.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
"unicode-width 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 = "docopt"
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.8.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
"lazy_static 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
"regex 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
"serde 1.0.27 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_derive 1.0.27 (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
"strsim 0.6.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"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
version = "0.4.2"
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"
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"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"backtrace 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)",
"failure_derive 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "failure_derive"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"quote 0.3.15 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 0.11.11 (registry+https://github.com/rust-lang/crates.io-index)",
"synstructure 0.6.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
[[package]]
name = "flate2"
version = "1.0.1"
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
"libc 0.2.36 (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 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
"bitflags 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
"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 deps
2018-01-31 01:05:39 -05:00
version = "0.1.18"
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 deps
2018-01-31 01:05:39 -05:00
"futures 0.1.18 (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
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://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 = "gcc"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
version = "0.3.54"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://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"
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 deps
2018-01-31 01:05:39 -05:00
source = "git+https://github.com/scottlamb/http-serve#210d6f5fe04cb38cc0208933e26be876ab94b354"
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 = [
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
"flate2 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
"futures 0.1.18 (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 deps
2018-01-31 01:05:39 -05:00
"hyper 0.11.16 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"mime 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)",
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
"smallvec 0.6.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
"time 0.1.39 (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 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.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"
[[package]]
name = "hyper"
upgrade deps
2018-01-31 01:05:39 -05:00
version = "0.11.16"
source = "git+https://github.com/scottlamb/hyper?branch=moonfire-on-0.11.x#0891fdb0962c835edc486e2ba99041c16ce9b1d3"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
dependencies = [
upgrade deps, 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
"base64 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
"bytes 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
"futures 0.1.18 (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)",
"httparse 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)",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://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 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.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"mime 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)",
"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 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
"time 0.1.39 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-core 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"tokio-io 0.1.4 (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)",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://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 = "hyper"
version = "0.11.16"
source = "registry+https://github.com/rust-lang/crates.io-index"
replace = "hyper 0.11.16 (git+https://github.com/scottlamb/hyper?branch=moonfire-on-0.11.x)"
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"
version = "0.1.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 deps
2018-01-31 01:05:39 -05:00
"futures 0.1.18 (registry+https://github.com/rust-lang/crates.io-index)",
"hyper 0.11.16 (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)",
"tokio-core 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"tokio-io 0.1.4 (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"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
version = "0.1.4"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update 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
"matches 0.1.6 (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)",
"unicode-normalization 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
]
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 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
"libc 0.2.36 (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"
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"
[[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"
version = "1.0.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"
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 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.36"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://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 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.14"
update dependencies * The mylog update fixes a couple bad bugs. * Otherwise, just keep up with the Rust ecosystem.
2017-06-11 15:57:55 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"adler32 1.0.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
"byteorder 1.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
"crc 1.7.0 (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 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.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"
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
"cc 1.0.4 (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
"pkg-config 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)",
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"vcpkg 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
]
[[package]]
name = "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"
[[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 = [
"log 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "log"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"cfg-if 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
[[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"
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.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"
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 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
"libc 0.2.36 (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 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
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.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
]
update several dependencies I left serde alone because uuid hasn't been updated for the new version.
2017-01-27 23:58:04 -05:00
[[package]]
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
name = "mime"
update dependencies
2017-11-17 02:01:09 -05:00
version = "0.3.5"
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 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.0-alpha.3"
update dependencies * The mylog update fixes a couple bad bugs. * Otherwise, just keep up with the Rust ecosystem.
2017-06-11 15:57:55 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update dependencies
2017-11-17 02:01:09 -05:00
"mime 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)",
"phf 0.7.21 (registry+https://github.com/rust-lang/crates.io-index)",
"phf_codegen 0.7.21 (registry+https://github.com/rust-lang/crates.io-index)",
"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 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
"cc 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.36 (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 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.12"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://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)",
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.3.9 (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)",
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"net2 0.2.31 (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)",
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "mio-uds"
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.6.4"
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
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
"mio 0.6.12 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
]
[[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)",
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"net2 0.2.31 (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 = [
"failure 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
"parking_lot 0.5.3 (registry+https://github.com/rust-lang/crates.io-index)",
"time 0.1.39 (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
[[package]]
name = "moonfire-db"
version = "0.0.1"
dependencies = [
"failure 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
"fnv 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)",
"lazy_static 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
"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)",
"openssl 0.10.2 (registry+https://github.com/rust-lang/crates.io-index)",
"parking_lot 0.5.3 (registry+https://github.com/rust-lang/crates.io-index)",
"protobuf 1.4.3 (registry+https://github.com/rust-lang/crates.io-index)",
"regex 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
"rusqlite 0.13.0 (registry+https://github.com/rust-lang/crates.io-index)",
"tempdir 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
"time 0.1.39 (registry+https://github.com/rust-lang/crates.io-index)",
"uuid 0.6.0 (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
[[package]]
name = "moonfire-ffmpeg"
version = "0.0.1"
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
"cc 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
"log 0.4.1 (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
"pkg-config 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)",
]
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
name = "moonfire-nvr"
version = "0.1.0"
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
"byteorder 1.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
"cursive 0.7.5 (registry+https://github.com/rust-lang/crates.io-index)",
"docopt 0.8.3 (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
"failure 0.1.1 (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 deps
2018-01-31 01:05:39 -05:00
"futures 0.1.18 (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)",
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
"http-serve 0.0.1 (git+https://github.com/scottlamb/http-serve)",
upgrade deps
2018-01-31 01:05:39 -05:00
"hyper 0.11.16 (registry+https://github.com/rust-lang/crates.io-index)",
"lazy_static 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps, including http-serve bugfix This was including the wrong Content-Encoding: header on gzipped json responses, so Chrome wouldn't understand them at all.
2018-01-30 19:51:32 -05:00
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
"log 0.4.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
"memmap 0.6.2 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"mime 0.3.5 (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 deps
2018-01-31 01:05:39 -05:00
"openssl 0.10.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
"parking_lot 0.5.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 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
"regex 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
"reqwest 0.8.4 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"rusqlite 0.13.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
"serde 1.0.27 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_derive 1.0.27 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_json 1.0.9 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
"smallvec 0.6.0 (registry+https://github.com/rust-lang/crates.io-index)",
"tempdir 0.3.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
"time 0.1.39 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-core 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-signal 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"url 1.6.0 (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
"uuid 0.6.0 (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 deps
2018-01-31 01:05:39 -05:00
"chrono 0.4.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
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
"log 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
"parking_lot 0.5.3 (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)",
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
"openssl 0.9.23 (registry+https://github.com/rust-lang/crates.io-index)",
"schannel 0.1.10 (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)",
upgrade deps
2018-01-31 01:05:39 -05:00
"tempdir 0.3.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
]
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 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 = "5.91.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 deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"gcc 0.3.54 (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
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"pkg-config 0.3.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 = "net2"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
version = "0.2.31"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"cfg-if 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
"libc 0.2.36 (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)",
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"
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.41"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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-bigint 0.1.41 (registry+https://github.com/rust-lang/crates.io-index)",
"num-complex 0.1.41 (registry+https://github.com/rust-lang/crates.io-index)",
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"num-integer 0.1.35 (registry+https://github.com/rust-lang/crates.io-index)",
"num-iter 0.1.34 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
"num-rational 0.1.41 (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-traits 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
]
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-bigint"
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.41"
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"num-integer 0.1.35 (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-traits 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)",
"rand 0.3.20 (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
"rustc-serialize 0.3.24 (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"
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.41"
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
"num-traits 0.1.42 (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
"rustc-serialize 0.3.24 (registry+https://github.com/rust-lang/crates.io-index)",
new "moonfire-nvr config" subcommand This is a ncurses-based user interface for configuration. This fills a major usability gap: the system can be configured without manual SQL commands.
2017-02-05 22:58:41 -05:00
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "num-integer"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
version = "0.1.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 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-traits 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
]
[[package]]
name = "num-iter"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
version = "0.1.34"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"num-integer 0.1.35 (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-traits 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
]
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"
upgrade deps
2018-01-31 01:05:39 -05:00
version = "0.1.41"
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
"num-bigint 0.1.41 (registry+https://github.com/rust-lang/crates.io-index)",
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"num-integer 0.1.35 (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-traits 0.1.42 (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
"rustc-serialize 0.3.24 (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 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.42"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[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 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
"libc 0.2.36 (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"
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.9.23"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update 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)",
"lazy_static 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
"openssl-sys 0.9.24 (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"
version = "0.10.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"bitflags 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
"foreign-types 0.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
"lazy_static 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
"openssl-sys 0.9.24 (registry+https://github.com/rust-lang/crates.io-index)",
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "openssl-sys"
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.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 = [
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
"cc 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.36 (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
"pkg-config 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)",
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"vcpkg 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
]
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 = [
"stable_deref_trait 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
name = "parking_lot"
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.5.3"
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 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
"parking_lot_core 0.2.10 (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 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.10"
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
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
"rand 0.3.20 (registry+https://github.com/rust-lang/crates.io-index)",
"smallvec 0.6.0 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.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
]
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"
version = "0.7.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"phf_shared 0.7.21 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "phf_codegen"
version = "0.7.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"phf_generator 0.7.21 (registry+https://github.com/rust-lang/crates.io-index)",
"phf_shared 0.7.21 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "phf_generator"
version = "0.7.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"phf_shared 0.7.21 (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
"rand 0.3.20 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
]
[[package]]
name = "phf_shared"
version = "0.7.21"
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 = [
"siphasher 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
"unicase 1.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
]
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "pkg-config"
update several dependencies I left serde alone because uuid hasn't been updated for the new version.
2017-01-27 23:58:04 -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"
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"
version = "1.4.3"
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"
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.3.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"
[[package]]
name = "rand"
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.20"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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)",
"libc 0.2.36 (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"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"fuchsia-zircon 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.4 (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 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.37"
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"
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"
source = "git+https://github.com/diwic/reffers-rs#22b9f2eb77f9ca97f217a098a2a50c80b9fc2a80"
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 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.5"
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 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
"aho-corasick 0.6.4 (registry+https://github.com/rust-lang/crates.io-index)",
"memchr 2.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
"regex-syntax 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
"thread_local 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)",
add matching time parsing and formatting routines * add a --ts subcommand to convert between numeric and human-readable representations. This is handy when directly inspecting the SQLite database or API output. * also take the human-readable form in the web interface's camera view. * to reduce confusion, when using trim=true on the web interface's camera view, trim the displayed starting and ending times as well as the actual .mp4 file links.
2017-01-13 02:09:02 -05:00
"utf8-ranges 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "regex-syntax"
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.4.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 (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 = [
"futures 0.1.18 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "remove_dir_all"
version = "0.3.0"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
upgrade deps
2018-01-31 01:05:39 -05:00
"kernel32-sys 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.2.8 (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 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.8.4"
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
"bytes 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
"futures 0.1.18 (registry+https://github.com/rust-lang/crates.io-index)",
"hyper 0.11.16 (registry+https://github.com/rust-lang/crates.io-index)",
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"hyper-tls 0.1.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
"libflate 0.1.14 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
"mime_guess 2.0.0-alpha.3 (registry+https://github.com/rust-lang/crates.io-index)",
"native-tls 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"serde 1.0.27 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_json 1.0.9 (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
"serde_urlencoded 0.5.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
"tokio-core 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"tokio-io 0.1.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
"tokio-tls 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"url 1.6.0 (registry+https://github.com/rust-lang/crates.io-index)",
"uuid 0.5.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
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
name = "rusqlite"
update dependencies
2017-11-17 02:01:09 -05:00
version = "0.13.0"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update dependencies
2017-11-17 02:01:09 -05:00
"bitflags 1.0.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
"libsqlite3-sys 0.9.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
"lru-cache 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps, including http-serve bugfix This was including the wrong Content-Encoding: header on gzipped json responses, so Chrome wouldn't understand them at all.
2018-01-30 19:51:32 -05:00
"time 0.1.39 (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"
version = "0.1.6"
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 = "rustc-serialize"
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.3.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"
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 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.10"
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 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.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 = "scoped-tls"
version = "0.1.0"
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 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
"libc 0.2.36 (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 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
"libc 0.2.36 (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 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.0.27"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://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 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.0.27"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://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
"quote 0.3.15 (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
"serde_derive_internals 0.19.0 (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
"syn 0.11.11 (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 = "serde_derive_internals"
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.19.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"
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
"syn 0.11.11 (registry+https://github.com/rust-lang/crates.io-index)",
"synom 0.11.3 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
]
[[package]]
name = "serde_json"
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.0.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"
dependencies = [
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"dtoa 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
"itoa 0.3.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
"num-traits 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)",
"serde 1.0.27 (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"
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.5.1"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"dtoa 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
"itoa 0.3.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
"serde 1.0.27 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"url 1.6.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 dependencies
2017-11-17 02:01:09 -05:00
[[package]]
name = "siphasher"
version = "0.2.2"
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"
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 = "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"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
[[package]]
update dependencies * The mylog update fixes a couple bad bugs. * Otherwise, just keep up with the Rust ecosystem.
2017-06-11 15:57:55 -04:00
name = "stable_deref_trait"
version = "1.0.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"
[[package]]
name = "strsim"
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
version = "0.6.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"
[[package]]
name = "syn"
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.11.11"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update 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
"quote 0.3.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
"synom 0.11.3 (registry+https://github.com/rust-lang/crates.io-index)",
"unicode-xid 0.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "synom"
version = "0.11.3"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update several dependencies I left serde alone because uuid hasn't been updated for the new version.
2017-01-27 23:58:04 -05:00
"unicode-xid 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
]
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"
version = "0.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"quote 0.3.15 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 0.11.11 (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 = "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"
upgrade deps
2018-01-31 01:05:39 -05:00
version = "0.3.6"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
upgrade deps
2018-01-31 01:05:39 -05:00
"rand 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
"remove_dir_all 0.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
add matching time parsing and formatting routines * add a --ts subcommand to convert between numeric and human-readable representations. This is handy when directly inspecting the SQLite database or API output. * also take the human-readable form in the web interface's camera view. * to reduce confusion, when using trim=true on the web interface's camera view, trim the displayed starting and ending times as well as the actual .mp4 file links.
2017-01-13 02:09:02 -05:00
]
[[package]]
name = "thread_local"
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.5"
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 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 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"unreachable 1.0.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 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.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 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
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
"redox_syscall 0.1.37 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.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
]
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 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.12"
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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
"bytes 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
"futures 0.1.18 (registry+https://github.com/rust-lang/crates.io-index)",
"iovec 0.1.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
"log 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)",
"mio 0.6.12 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade to async hyper serve_generated_bytes is >3X faster. One caveat is that the reactor thread may stall when reading from the memory-mapped slice. Moonfire NVR is basically a single-user program, so that may not be so bad, but we'll see.
2017-03-02 22:29:28 -05:00
"scoped-tls 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"slab 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 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 = "tokio-io"
update dependencies
2017-11-17 02:01:09 -05: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 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
"bytes 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
upgrade deps
2018-01-31 01:05:39 -05:00
"futures 0.1.18 (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 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 deps
2018-01-31 01:05:39 -05:00
"futures 0.1.18 (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)",
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"net2 0.2.31 (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
"rand 0.3.20 (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 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-core 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"tokio-io 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
"tokio-service 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "tokio-service"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
upgrade deps
2018-01-31 01:05:39 -05:00
"futures 0.1.18 (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"
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.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 deps
2018-01-31 01:05:39 -05:00
"futures 0.1.18 (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
"libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)",
"mio 0.6.12 (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
"mio-uds 0.6.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
"tokio-core 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
"tokio-io 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.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
]
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 deps
2018-01-31 01:05:39 -05:00
"futures 0.1.18 (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)",
"tokio-core 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
"tokio-io 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 dependencies
2017-11-17 02:01:09 -05:00
version = "0.4.5"
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
"serde 1.0.27 (registry+https://github.com/rust-lang/crates.io-index)",
update dependencies
2017-11-17 02:01:09 -05:00
]
[[package]]
name = "unicase"
version = "1.4.2"
update dependencies * The mylog update fixes a couple bad bugs. * Otherwise, just keep up with the Rust ecosystem.
2017-06-11 15:57:55 -04:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update dependencies
2017-11-17 02:01:09 -05:00
"version_check 0.1.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
]
[[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 = [
update dependencies
2017-11-17 02:01:09 -05:00
"version_check 0.1.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 = "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 = [
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
"matches 0.1.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 = "unicode-normalization"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -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]]
name = "unicode-segmentation"
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 = "1.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"
[[package]]
name = "unicode-width"
version = "0.1.4"
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 = "unicode-xid"
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
version = "0.0.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"
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"
update dependencies
2017-11-17 02:01:09 -05:00
version = "1.6.0"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"idna 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
"matches 0.1.6 (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"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
version = "0.5.1"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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
"rand 0.3.20 (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
]
[[package]]
name = "uuid"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"rand 0.4.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
"serde 1.0.27 (registry+https://github.com/rust-lang/crates.io-index)",
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
2016-12-03 00:50:37 -05:00
]
update dependencies * The mylog update fixes a couple bad bugs. * Otherwise, just keep up with the Rust ecosystem.
2017-06-11 15:57:55 -04:00
[[package]]
name = "vcpkg"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
version = "0.2.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"
update dependencies
2017-11-17 02:01:09 -05:00
[[package]]
name = "version_check"
version = "0.1.3"
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"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://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"
version = "0.3.4"
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)",
]
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://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]
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"checksum adler32 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "6cbd0b9af8587c72beadc9f72d35b9fbb070982c9e6203e46e93f10df25f8f45"
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 aho-corasick 0.6.4 (registry+https://github.com/rust-lang/crates.io-index)" = "d6531d44de723825aa81398a6415283229725a00fa30713812ab9323faa82fc4"
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
"checksum backtrace 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)" = "ebbbf59b1c43eefa8c3ede390fcc36820b4999f7914104015be25025e0d62af2"
"checksum backtrace-sys 0.1.16 (registry+https://github.com/rust-lang/crates.io-index)" = "44585761d6161b0f57afc49482ab6bd067e4edef48c12a152c237eb0203f7661"
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 base64 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)" = "229d032f1a99302697f10b27167ae6d03d49d032e6a8e2550e8d3fc13356d2b4"
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"
update dependencies
2017-11-17 02:01:09 -05:00
"checksum bitflags 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)" = "b3c30d3802dfb7281680d6285f2ccdaa8c2d8fee41f93805dba5c4cf50dc23cf"
"checksum build_const 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "e90dc84f5e62d2ebe7676b83c22d33b6db8bd27340fb6ffbff0a364efa0cb9c9"
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 byteorder 1.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "652805b7e73fada9d85e9a6682a4abd490cb52d96aeecc12e33a0de34dfd0d23"
"checksum bytes 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)" = "1b7db437d718977f6dc9b2e3fd6fc343c02ac6b899b73fdd2179163447bd9ce9"
"checksum cc 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)" = "deaf9ec656256bb25b404c51ef50097207b9cbb29c933d31f92cae5a8a0ffee0"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"checksum cfg-if 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "d4c819a1287eb618df47cc647173c5c4c66ba19d888a6e50d605672aed3140de"
upgrade deps
2018-01-31 01:05:39 -05:00
"checksum chrono 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "7c20ebe0b2b08b0aeddba49c609fe7957ba2e33449882cb186a180bc60682fa9"
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 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 crc 1.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "bd5d02c0aac6bd68393ed69e00bbc2457f3e89075c6349db7189618dc4ddc1d7"
"checksum cursive 0.7.5 (registry+https://github.com/rust-lang/crates.io-index)" = "82b96a092541def4e42095b3201a5b4111971c551e579c091b3f121a620fe12e"
"checksum docopt 0.8.3 (registry+https://github.com/rust-lang/crates.io-index)" = "d8acd393692c503b168471874953a2531df0e9ab77d0b6bbc582395743300a4a"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"checksum dtoa 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)" = "09c3753c3db574d215cba4ea76018483895d7bff25a31b49ba45db21c48e50ab"
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
"checksum failure 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "934799b6c1de475a012a02dab0ace1ace43789ee4b99bcfbf1a2e3e8ced5de82"
"checksum failure_derive 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "c7cdda555bb90c9bb67a3b670a0f42de8e73f5981524123ad8578aafec8ddb8b"
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
"checksum flate2 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)" = "9fac2277e84e5e858483756647a9d0aa8d9a2b7cba517fd84325a0aaa69a0909"
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 deps
2018-01-31 01:05:39 -05:00
"checksum futures 0.1.18 (registry+https://github.com/rust-lang/crates.io-index)" = "0bab5b5e94f5c31fc764ba5dd9ad16568aae5d4825538c01d6bca680c9bf94a7"
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"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"checksum gcc 0.3.54 (registry+https://github.com/rust-lang/crates.io-index)" = "5e33ec290da0d127825013597dbdfc28bee4964690c7ce1166cbc2a7bd08b1bb"
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
"checksum http-serve 0.0.1 (git+https://github.com/scottlamb/http-serve)" = "<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 httparse 1.2.4 (registry+https://github.com/rust-lang/crates.io-index)" = "c2f407128745b78abc95c0ffbe4e5d37427fdc0d45470710cfef8c44522a2e37"
upgrade deps
2018-01-31 01:05:39 -05:00
"checksum hyper 0.11.16 (git+https://github.com/scottlamb/hyper?branch=moonfire-on-0.11.x)" = "<none>"
"checksum hyper 0.11.16 (registry+https://github.com/rust-lang/crates.io-index)" = "6a82c41828dd6f271f4d6ebc3f1db78239a4b2b3d355dfdb5f8bbf55f004463a"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"checksum hyper-tls 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "9c81fa95203e2a6087242c38691a0210f23e9f3f8f944350bd676522132e2985"
"checksum idna 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "014b298351066f1512874135335d62a789ffe78a9974f94b43ed5621951eaf7d"
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"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"checksum itoa 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)" = "8324a32baf01e2ae060e9de58ed0bc2320c9a2833491ee36cd3b4c414de4db8c"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://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"
"checksum lazy_static 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "c8f31047daa365f19be14b47c29df4f7c3b581832407daabe6ae77397619237d"
"checksum lazycell 0.6.0 (registry+https://github.com/rust-lang/crates.io-index)" = "a6f08839bc70ef4a3fe1d566d5350f519c5912ea86be0df1740a7d247c7fc0ef"
"checksum libc 0.2.36 (registry+https://github.com/rust-lang/crates.io-index)" = "1e5d97d6708edaa407429faa671b942dc0f2727222fb6b6539bf1db936e4b121"
"checksum libflate 0.1.14 (registry+https://github.com/rust-lang/crates.io-index)" = "1a429b86418868c7ea91ee50e9170683f47fd9d94f5375438ec86ec3adb74e8e"
"checksum libsqlite3-sys 0.9.1 (registry+https://github.com/rust-lang/crates.io-index)" = "0e9eb7b8e152b6a01be6a4a2917248381875758250dc3df5d46caf9250341dda"
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 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"
"checksum log 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)" = "89f010e843f2b1a31dbd316b3b8d443758bc634bed37aabade59c686d644e0a2"
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"
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 matches 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "100aabe6b8ff4e4a7e32c1c13523379802df0772b82466207ac25b013f193376"
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 dependencies
2017-11-17 02:01:09 -05:00
"checksum mime 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)" = "e2e00e17be181010a91dbfefb01660b17311059dc8c7f48b9017677721e732bd"
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 mime_guess 2.0.0-alpha.3 (registry+https://github.com/rust-lang/crates.io-index)" = "013572795763289e14710c7b279461295f2673b2b338200c235082cd7ca9e495"
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 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 mio 0.6.12 (registry+https://github.com/rust-lang/crates.io-index)" = "75f72a93f046f1517e3cfddc0a096eb756a2ba727d36edc8227dee769a50a9b0"
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 mio-uds 0.6.4 (registry+https://github.com/rust-lang/crates.io-index)" = "1731a873077147b626d89cc6c2a0db6288d607496c5d10c0cfcf3adc697ec673"
"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"
"checksum ncurses 5.91.0 (registry+https://github.com/rust-lang/crates.io-index)" = "431cc11a5225e21cb85ea479858ac2e0b3c7a67c9506016cd8818de15dcdc8f1"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"checksum net2 0.2.31 (registry+https://github.com/rust-lang/crates.io-index)" = "3a80f842784ef6c9a958b68b7516bc7e35883c614004dd94959a4dca1b716c09"
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 0.1.41 (registry+https://github.com/rust-lang/crates.io-index)" = "cc4083e14b542ea3eb9b5f33ff48bd373a92d78687e74f4cc0a30caeb754f0ca"
"checksum num-bigint 0.1.41 (registry+https://github.com/rust-lang/crates.io-index)" = "bdc1494b5912f088f260b775799468d9b9209ac60885d8186a547a0476289e23"
"checksum num-complex 0.1.41 (registry+https://github.com/rust-lang/crates.io-index)" = "58de7b4bf7cf5dbecb635a5797d489864eadd03b107930cbccf9e0fd7428b47c"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"checksum num-integer 0.1.35 (registry+https://github.com/rust-lang/crates.io-index)" = "d1452e8b06e448a07f0e6ebb0bb1d92b8890eea63288c0b627331d53514d0fba"
"checksum num-iter 0.1.34 (registry+https://github.com/rust-lang/crates.io-index)" = "7485fcc84f85b4ecd0ea527b14189281cf27d60e583ae65ebc9c088b13dffe01"
upgrade deps
2018-01-31 01:05:39 -05:00
"checksum num-rational 0.1.41 (registry+https://github.com/rust-lang/crates.io-index)" = "0b950f75e042fdd710460084d19c8efdcd72d65183ead8ecd04b90483f5a55d2"
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-traits 0.1.42 (registry+https://github.com/rust-lang/crates.io-index)" = "9936036cc70fe4a8b2d338ab665900323290efb03983c86cbe235ae800ad8017"
"checksum num_cpus 1.8.0 (registry+https://github.com/rust-lang/crates.io-index)" = "c51a3322e4bca9d212ad9a158a02abc6934d005490c054a2778df73a70aa0a30"
upgrade deps
2018-01-31 01:05:39 -05:00
"checksum openssl 0.10.2 (registry+https://github.com/rust-lang/crates.io-index)" = "454359fda553386f93bb47f9c331263f50e03f3588bcc3d98081c49bb2c9e9e5"
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 openssl 0.9.23 (registry+https://github.com/rust-lang/crates.io-index)" = "169a4b9160baf9b9b1ab975418c673686638995ba921683a7f1e01470dcb8854"
"checksum openssl-sys 0.9.24 (registry+https://github.com/rust-lang/crates.io-index)" = "14ba54ac7d5a4eabd1d5f2c1fdeb7e7c14debfa669d94b983d01b465e767ba9e"
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 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 parking_lot 0.5.3 (registry+https://github.com/rust-lang/crates.io-index)" = "3e7f7c9857874e54afeb950eebeae662b1e51a2493666d2ea4c0a5d91dcf0412"
"checksum parking_lot_core 0.2.10 (registry+https://github.com/rust-lang/crates.io-index)" = "9f35048d735bb93dd115a0030498785971aab3234d311fbe273d020084d26bd8"
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"
"checksum phf 0.7.21 (registry+https://github.com/rust-lang/crates.io-index)" = "cb325642290f28ee14d8c6201159949a872f220c62af6e110a56ea914fbe42fc"
"checksum phf_codegen 0.7.21 (registry+https://github.com/rust-lang/crates.io-index)" = "d62594c0bb54c464f633175d502038177e90309daf2e0158be42ed5f023ce88f"
"checksum phf_generator 0.7.21 (registry+https://github.com/rust-lang/crates.io-index)" = "6b07ffcc532ccc85e3afc45865469bf5d9e4ef5bfcf9622e3cfe80c2d275ec03"
"checksum phf_shared 0.7.21 (registry+https://github.com/rust-lang/crates.io-index)" = "07e24b0ca9643bdecd0632f2b3da6b1b89bbb0030e0b992afc1113b23a7bc2f2"
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
"checksum pkg-config 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)" = "3a8b4c6b8165cd1a1cd4b9b120978131389f64bdaf456435caa41e630edba903"
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
"checksum protobuf 1.4.3 (registry+https://github.com/rust-lang/crates.io-index)" = "bec26e67194b7d991908145fdf21b7cae8b08423d96dcb9e860cd31f854b9506"
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 quote 0.3.15 (registry+https://github.com/rust-lang/crates.io-index)" = "7a6e920b65c65f10b2ae65c831a81a073a89edd28c7cce89475bff467ab4167a"
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 rand 0.3.20 (registry+https://github.com/rust-lang/crates.io-index)" = "512870020642bb8c221bf68baa1b2573da814f6ccfe5c9699b1c303047abe9b1"
upgrade deps
2018-01-31 01:05:39 -05:00
"checksum rand 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)" = "eba5f8cb59cc50ed56be8880a5c7b496bfd9bd26394e176bc67884094145c2c5"
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 redox_syscall 0.1.37 (registry+https://github.com/rust-lang/crates.io-index)" = "0d92eecebad22b767915e4d529f89f28ee96dbbf5a4810d2b844373f136417fd"
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 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 regex 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)" = "744554e01ccbd98fff8c457c3b092cd67af62a555a43bfe97ae8a0451f7799fa"
"checksum regex-syntax 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)" = "8e931c58b93d86f080c734bfd2bce7dd0079ae2331235818133c8be7f422e20e"
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"
"checksum remove_dir_all 0.3.0 (registry+https://github.com/rust-lang/crates.io-index)" = "b5d2f806b0fcdabd98acd380dc8daef485e22bcb7cddc811d1337967f2528cf5"
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 reqwest 0.8.4 (registry+https://github.com/rust-lang/crates.io-index)" = "449c45f593ce9af9417c91e22f274fb8cea013bcf3d37ec1b5fb534b623bc708"
update dependencies
2017-11-17 02:01:09 -05:00
"checksum rusqlite 0.13.0 (registry+https://github.com/rust-lang/crates.io-index)" = "d9409d78a5a9646685688266e1833df8f08b71ffcae1b5db6c1bfb5970d8a80f"
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
"checksum rustc-demangle 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "f312457f8a4fa31d3581a6f423a70d6c33a10b95291985df55f1ff670ec10ce8"
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 rustc-serialize 0.3.24 (registry+https://github.com/rust-lang/crates.io-index)" = "dcf128d1287d2ea9d80910b5f1120d0b8eede3fbf1abe91c40d39ea7d51e6fda"
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 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 schannel 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)" = "acece75e0f987c48863a6c792ec8b7d6c4177d4a027f8ccc72f849794f437016"
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 scoped-tls 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "f417c22df063e9450888a7561788e9bd46d3bb3c1466435b4eccb903807f147d"
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 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 serde 1.0.27 (registry+https://github.com/rust-lang/crates.io-index)" = "db99f3919e20faa51bb2996057f5031d8685019b5a06139b1ce761da671b8526"
"checksum serde_derive 1.0.27 (registry+https://github.com/rust-lang/crates.io-index)" = "f4ba7591cfe93755e89eeecdbcc668885624829b020050e6aec99c2a03bd3fd0"
"checksum serde_derive_internals 0.19.0 (registry+https://github.com/rust-lang/crates.io-index)" = "6e03f1c9530c3fb0a0a5c9b826bdd9246a5921ae995d75f512ac917fc4dd55b5"
"checksum serde_json 1.0.9 (registry+https://github.com/rust-lang/crates.io-index)" = "c9db7266c7d63a4c4b7fe8719656ccdd51acf1bed6124b174f933b009fb10bcb"
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 serde_urlencoded 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "ce0fd303af908732989354c6f02e05e2e6d597152870f2c6990efb0577137480"
update dependencies
2017-11-17 02:01:09 -05:00
"checksum siphasher 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "0df90a788073e8d0235a67e50441d47db7c8ad9debd91cbf43736a2a92d36537"
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"
update dependencies
2017-11-17 02:01:09 -05:00
"checksum slab 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "fdeff4cd9ecff59ec7e3744cbca73dfe5ac35c2aedb2cfba8a1c715a18912e9d"
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"
crate rename: http-(entity|file) -> http-serve
2018-01-23 14:08:21 -05:00
"checksum smallvec 0.6.0 (registry+https://github.com/rust-lang/crates.io-index)" = "44db0ecb22921ef790d17ae13a3f6d15784183ff5f2a01aa32098c7498d2b4b9"
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 stable_deref_trait 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "15132e0e364248108c5e2c02e3ab539be8d6f5d52a01ca9bbf27ed657316f02b"
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
"checksum strsim 0.6.0 (registry+https://github.com/rust-lang/crates.io-index)" = "b4d15c810519a91cf877e7e36e63fe068815c678181439f2f29e2562147c3694"
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 syn 0.11.11 (registry+https://github.com/rust-lang/crates.io-index)" = "d3b891b9015c88c576343b9b3e41c2c11a51c219ef067b264bd9c8aa9b441dad"
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 synom 0.11.3 (registry+https://github.com/rust-lang/crates.io-index)" = "a393066ed9010ebaed60b9eafa373d4b1baac186dd7e008555b0f702b51945b6"
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
"checksum synstructure 0.6.1 (registry+https://github.com/rust-lang/crates.io-index)" = "3a761d12e6d8dcb4dcf952a7a89b475e3a9d69e4a69307e01a470977642914bd"
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"
upgrade deps
2018-01-31 01:05:39 -05:00
"checksum tempdir 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)" = "f73eebdb68c14bcb24aef74ea96079830e7fa7b31a6106e42ea7ee887c1e134e"
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 thread_local 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)" = "279ef31c19ededf577bfd12dfae728040a21f635b06a24cd670ff510edd38963"
"checksum time 0.1.39 (registry+https://github.com/rust-lang/crates.io-index)" = "a15375f1df02096fb3317256ce2cee6a1f42fc84ea5ad5fc8c421cfe40c73098"
"checksum tokio-core 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)" = "52b4e32d8edbf29501aabb3570f027c6ceb00ccef6538f4bddba0200503e74e8"
update dependencies
2017-11-17 02:01:09 -05:00
"checksum tokio-io 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "514aae203178929dbf03318ad7c683126672d4d96eccb77b29603d33c9e25743"
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 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"
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-signal 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "57c4031b97651d28c87a0a071e1c2809d70609d3120ce285b302eb7d52c96906"
"checksum tokio-tls 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "772f4b04e560117fe3b0a53e490c16ddc8ba6ec437015d91fa385564996ed913"
update dependencies
2017-11-17 02:01:09 -05:00
"checksum toml 0.4.5 (registry+https://github.com/rust-lang/crates.io-index)" = "a7540f4ffc193e0d3c94121edb19b055670d369f77d5804db11ae053a45b6e7e"
"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"
"checksum unicode-normalization 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "51ccda9ef9efa3f7ef5d91e8f9b83bbe6955f9bf86aec89d5cce2c874625920f"
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 unicode-segmentation 1.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "a8083c594e02b8ae1654ae26f0ade5158b119bd88ad0e8227a5d8fcd72407946"
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
"checksum unicode-width 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "bf3a113775714a22dcb774d8ea3655c53a32debae63a063acc00a91cc586245f"
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
"checksum unicode-xid 0.0.4 (registry+https://github.com/rust-lang/crates.io-index)" = "8c1f860d7d29cf02cb2f3f359fd35991af3d30bac52c57d265a3c461074cb4dc"
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"
update dependencies
2017-11-17 02:01:09 -05:00
"checksum url 1.6.0 (registry+https://github.com/rust-lang/crates.io-index)" = "fa35e768d4daf1d85733418a49fb42e10d7f633e394fccab4ab7aba897053fe2"
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"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"checksum uuid 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "bcc7e3b898aa6f6c08e5295b6c89258d1331e9ac578cc992fb818759951bdc22"
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
"checksum uuid 0.6.0 (registry+https://github.com/rust-lang/crates.io-index)" = "2bcacdce7c75ad110c0dba131d6628c64398593e3895025d043ee2fcf97c4b6e"
update deps (particularly hyper) + fix warnings
2017-09-22 00:51:58 -04:00
"checksum vcpkg 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "9e0a7d8bed3178a8fb112199d466eeca9ed09a14ba8ad67718179b4fd5487d0b"
update dependencies
2017-11-17 02:01:09 -05:00
"checksum version_check 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "6b772017e347561807c1aa192438c5fd74242a670a6cffacc40f2defd1dc069d"
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"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://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 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 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)" = "04e3bd221fcbe8a271359c04f21a76db7d0c6028862d1bb5512d85e1e2eb5bb3"
commit Cargo.lock This is the best practice according to the Cargo FAQ: http://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"