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/CHANGELOG.md

208 lines
10 KiB
Markdown
Raw Normal View History

changelog, including upcoming 0.6.2
2021-03-10 20:53:29 -05:00
# Moonfire NVR change log
Below are some highlights in each release. For a full description of all
changes, see Git history.
Each release is tagged in Git and on the Docker repository
[`scottlamb/moonfire-nvr`](https://hub.docker.com/r/scottlamb/moonfire-nvr).
tweaks to api and docs In particular, the docs now talk about the CSRF protection. This is increasing relevant as we start having more mutation endpoints. And make the signals api expect a csrf for session auth to match the newer users api.
2023-01-05 13:11:28 -05:00
Backwards-incompatible database schema changes happen on on major version
upgrades, e.g. `0.6.x` -> `0.7.x`. The config file format and
config file reference and doc reorganization
2023-01-06 12:40:41 -05:00
[API](ref/api.md) currently have no stability guarantees, so they may change
tweaks to api and docs In particular, the docs now talk about the CSRF protection. This is increasing relevant as we start having more mutation endpoints. And make the signals api expect a csrf for session auth to match the newer users api.
2023-01-05 13:11:28 -05:00
even on minor releases, e.g. `0.7.5` -> `0.7.6`.
upgrade to Retina 0.4.1 Fixes #234
2022-08-09 11:02:07 -04:00
## unreleased
upgrade Rust deps
2023-01-05 18:35:26 -05:00
* bump minimum Rust version to 1.64.
make `GET /api/` return current permissions This is useful for e.g. deciding whether or not to present the user admin UI in navigation. As part of this change, I adjusted the casing in Permissions, and then all the toml stuff for consistency. Noted in changelog.
2022-12-31 12:08:26 -05:00
* expect camelCase in `moonfire-nvr.toml` file, for consistency with the JSON
API. You'll need to adjust your config file when upgrading.
Retina 0.4.4
2023-01-05 17:38:13 -05:00
* use Retina 0.4.4.
* This version is newly compatible with rtsp-simple-server v0.19.3 and some
TP-Link cameras. Fixes [#238](https://github.com/scottlamb/moonfire-nvr/issues/238).
* Fixes problems connecting to cameras that use RTP extensions.
retrieve and set users' permissions
2022-12-24 12:38:13 -05:00
* expanded API interface for examining and updating users:
* `admin_users` permission for operating on arbitrary users.
more user admin actions
2022-12-24 15:21:06 -05:00
* `GET /users/` endpoint to list users
user admin api improvements
2023-01-08 04:14:03 -05:00
* `POST /users/` endpoint to add a user
more user admin actions
2022-12-24 15:21:06 -05:00
* `GET /users/<id>` endpoint to examine a user in detail
user admin api improvements
2023-01-08 04:14:03 -05:00
* expanded `PATCH /users/<id>` endpoint, including password and
retrieve and set users' permissions
2022-12-24 12:38:13 -05:00
permissions.
more user admin actions
2022-12-24 15:21:06 -05:00
* `DELETE /users/<id>` endpoint to delete a user
config file reference and doc reorganization
2023-01-06 12:40:41 -05:00
* improved API documentation in [`ref/api.md`](ref/api.md).
user admin UI
2023-01-07 12:52:50 -05:00
* first draft of a web UI for user administration. Rough edges expected!
`moonfire-nvr login --permissions`: take JSON This improves usability and shrinks the binary: 12.0 MiB to 11.0 MiB just now.
2023-02-11 15:07:29 -05:00
* `moonfire-nvr login --permissions` now accepts the JSON format documented
in `ref/api.md`, not an undocumented plaintext protobuf format.
upgrade to Retina 0.4.1 Fixes #234
2022-08-09 11:02:07 -04:00
prepare 0.7.5 with Retina 0.3.10 Fixes #224
2022-05-09 16:08:52 -04:00
## 0.7.5 (2022-05-09)
ignore port number in ws origin check Fixes #219
2022-04-14 00:45:45 -04:00
* [#219](https://github.com/scottlamb/moonfire-nvr/issues/219): fix
live stream failing with `ws close: 1006` on URLs with port numbers.
build docker image with lto
2022-04-14 13:53:03 -04:00
* build Docker images with link-time optimization.
update a few deps
2022-05-02 14:22:14 -04:00
* bump minimum Rust version to 1.60.
prepare 0.7.5 with Retina 0.3.10 Fixes #224
2022-05-09 16:08:52 -04:00
* [#224](https://github.com/scottlamb/moonfire-nvr/issues/224): upgrade to
Retina 0.3.10, improving compatibility with OMNY M5S2A 2812 cameras that
send invalid `rtptime` values.
ignore port number in ws origin check Fixes #219
2022-04-14 00:45:45 -04:00
prepare v0.7.4
2022-04-13 18:08:15 -04:00
## 0.7.4 (2022-04-13)
upgrade to Retina v0.3.9 This alone improves interop and diagnostics, as noted in Retina's release notes. We also now give the camera name to the session group (for improved logging of TEARDOWN operations) and expose the RTSP server's "tool" attribute in debug logs and the config UI's "Test" button. Fixes #209 Fixes #213
2022-04-12 17:57:16 -04:00
prepare v0.7.4
2022-04-13 18:08:15 -04:00
* upgrade to Retina 0.3.9, improving camera interop and diagnostics.
Fixes [#213](https://github.com/scottlamb/moonfire-nvr/issues/213),
[#209](https://github.com/scottlamb/moonfire-nvr/issues/209).
seamless mid-stream video parameter changes For #217. This handles the recording logic. May still need fixes to playback and/or live stream logic.
2022-04-13 17:37:45 -04:00
* [#217](https://github.com/scottlamb/moonfire-nvr/issues/217): no longer
drop the connection to the camera when it changes video parameters, instead
continuing the run seamlessly.
mention #206 in v0.7.4 changelog
2022-04-13 21:14:57 -04:00
* [#206](https://github.com/scottlamb/moonfire-nvr/issues/206#issuecomment-1086442543):
fix `teardown Sender shouldn't be dropped: RecvError(())` errors on shutdown.
upgrade to Retina v0.3.9 This alone improves interop and diagnostics, as noted in Retina's release notes. We also now give the camera name to the session group (for improved logging of TEARDOWN operations) and expose the RTSP server's "tool" attribute in debug logs and the config UI's "Test" button. Fixes #209 Fixes #213
2022-04-12 17:57:16 -04:00
create gh release on tag For #210 * update changelog format so that `parse-changelog` is happy. * add the example from taiki-e/create-gh-release-action verbatim. Fingers crossed it works in my setup.
2022-04-13 18:00:30 -04:00
## 0.7.3 (2022-03-22)
check WebSocket origin This fixes a real cross-site WebSocket hijacking (CSWSH) vulnerability. If the attacker knows the URL of an NVR installation this user is authenticated to and the UUID of a camera, and can trick the user into visiting their webpage, they can grab the live stream. At least there's some entropy in the camera UUID, but it was never intended to be a secret.
2022-03-22 17:28:25 -04:00
* security fix: check the `Origin` header on live stream WebSocket requests
to avoid cross-site WebSocket hijacking (CSWSH).
* RTSP connections always use the Retina library rather than FFmpeg.
create gh release on tag For #210 * update changelog format so that `parse-changelog` is happy. * add the example from taiki-e/create-gh-release-action verbatim. Fingers crossed it works in my setup.
2022-04-13 18:00:30 -04:00
## 0.7.2 (2022-03-16)
fix #182: error on upgrade when onvif_host empty
2021-11-23 13:12:28 -05:00
tweak config format (#133) * switch from json to toml. I think this will be more user-friendly. It allows comments and has less punctuation. Fewer surprises than yaml (which has e.g. the "Norway problem"). I might have stayed with JSON if I could see a good serde json library that allows comments, but hson is unmaintained and serde-json strictly follows the spec. * switch from camelCase to snake_case. Seems more idiomatic for TOML and matches the Rust source. * forbid unknown keys. Better to spot errors sooner. * rename "trust_forward_hdrs" to "trust_forward_headers". Nothing else is abbreviated.
2022-03-16 15:28:08 -04:00
* introduce a configuration file `/etc/moonfire-nvr.toml`; you will need
introduce /etc/moonfire-nvr.json (#133)
2022-03-09 16:12:33 -05:00
to create one when upgrading.
fix #187 via a dependency upgrade I did a full `cargo upgrade` and fixed what it broke: * a couple things for the latest protobuf 3.0 alphas (note alphas don't promise API stability) * new minimum supported Rust version This should have some other nice effects: parking_lot now uses inline assembler, tokio has gotten faster, etc.
2022-03-08 14:22:01 -05:00
* bump minimum Rust version from 1.53 to 1.56.
* fix [#187](https://github.com/scottlamb/moonfire-nvr/issues/187):
incompatibility with cameras that (incorrectly) omit the SDP origin line.
fix #182: error on upgrade when onvif_host empty
2021-11-23 13:12:28 -05:00
* fix [#182](https://github.com/scottlamb/moonfire-nvr/issues/182): error
on upgrade from schema 6 to schema 7 when a camera's `onvif_host` is empty.
include ext stream in API response; better docs In particular, the docs now explicitly call out that API changes can happen at any version, and from 0.7.0 onward they're described in the changelog.
2021-11-23 16:01:20 -05:00
* API bugfix: in the `GET /api/` response, include `ext` streams if
configured.
update retina and http-serve deps * new retina notably fixes #184 * new http-serve removes an accidental debug print on stdout
2021-12-30 01:14:49 -05:00
* fix [#184](https://github.com/scottlamb/moonfire-nvr/issues/184):
Moonfire NVR would stop recording on a camera that hit the live555 stale
file descriptor bug, rather than waiting for the stale session to expire.
reduce debug output in release/bench builds This reduces the binary size from 154 MiB to 70 MiB (#70 progress). Tools like `cargo flamegraph` still work fine. As suggested by "EarthFeet" on reddit: https://www.reddit.com/r/rust/comments/rw0jad/cargos_strip_profile_option_has_been_stabilized/hra193k/
2022-01-05 12:55:30 -05:00
* progress on [#70](https://github.com/scottlamb/moonfire-nvr/issues/184):
shrink the binary from 154 MiB to 70 MiB by reducing debugging information.
fix #182: error on upgrade when onvif_host empty
2021-11-23 13:12:28 -05:00
create gh release on tag For #210 * update changelog format so that `parse-changelog` is happy. * add the example from taiki-e/create-gh-release-action verbatim. Fingers crossed it works in my setup.
2022-04-13 18:00:30 -04:00
## 0.7.1 (2021-10-27)
revert cursive upgrade SelectView::set_selection doesn't seem to be working properly. The symptom is editing an existing camera will clear the sample file dir, and thus hitting edit without making any changes will fail.
2021-10-27 17:20:51 -04:00
* bugfix: editing a camera from `nvr config` would erroneously clear the
sample file directory associated with its streams.
allow setting rtsp transport per-stream
2021-10-27 17:27:23 -04:00
* RTSP transport (TCP or UDP) can be set per-stream from `nvr config`.
revert cursive upgrade SelectView::set_selection doesn't seem to be working properly. The symptom is editing an existing camera will clear the sample file dir, and thus hitting edit without making any changes will fail.
2021-10-27 17:20:51 -04:00
create gh release on tag For #210 * update changelog format so that `parse-changelog` is happy. * add the example from taiki-e/create-gh-release-action verbatim. Fingers crossed it works in my setup.
2022-04-13 18:00:30 -04:00
## 0.7.0 (2021-10-27)
preparing v0.7.0
2021-10-26 21:54:26 -04:00
* [schema version 7](guide/schema.md#version-7)
include ext stream in API response; better docs In particular, the docs now explicitly call out that API changes can happen at any version, and from 0.7.0 onward they're described in the changelog.
2021-11-23 16:01:20 -05:00
* Changes to the [API](guide/api.md):
* Added fields to the `GET /api/` response:
* `serverVersion`
* Altered fields in the `GET /api/` response:
* `session` was moved into a new `user` object, to support providing
information about the user when authenticating via Unix uid rather
than session cookie (a planned feature). `session.username` is now
`user.name`; `session.csrf` is now `user.session.csrf`. `user.id`
and `user.preferences` have been added.
* `signals.source` is now `signals.uuid`. The UUID is now expected to
be unique, where before only (source, type) was guaranteed to be
unique.
* `camera.config` has been altered and extended. `onvifHost` has
become `onvifBaseUrl` to allow selecting between `http` and `https`.
* `camera.description` was moved to `camera.config.description`.
(This might have been an oversight; now it's only possible to see
the description with the `read_camera_configs` permission. This
field can be re-introduced if desired.)
* `stream.config` has been altered and extended. `rtspUrl` has become
`url` to (in the future) represent a URL for other streaming
protocols. The `record` boolean was replaced with `mode`, which
currently may be either absent or the string `record`.
* Added `POST /api/users/<id>` for altering a user's UI preferences.
preparing v0.7.0
2021-10-26 21:54:26 -04:00
create gh release on tag For #210 * update changelog format so that `parse-changelog` is happy. * add the example from taiki-e/create-gh-release-action verbatim. Fingers crossed it works in my setup.
2022-04-13 18:00:30 -04:00
## 0.6.7 (2021-10-20)
trim whitespace from /etc/timezone
2021-09-24 13:49:04 -04:00
* trim whitespace when detecting time zone by reading `/etc/timezone`.
prepare v0.6.7 w/ Retina v0.3.3 This improves authentication over RTSP.
2021-10-20 17:59:33 -04:00
* (Retina 0.3.2) better `TEARDOWN` handling with the default
`--rtsp-library=retina` (see
[scottlamb/retina#34](https://github.com/scottlamb/retina/34)).
Retina 0.3.2, better TEARDOWNs
2021-09-29 08:55:12 -04:00
This means faster recovery after an error when using UDP or when the
camera's firmware is based on an old live555 release.
prepare v0.6.7 w/ Retina v0.3.3 This improves authentication over RTSP.
2021-10-20 17:59:33 -04:00
* (Retina 0.3.3) better authentication support with the default
`--rtsp-library=retina` (see
[scottlamb/retina#25](https://github.com/scottlamb/retina/25)).
trim whitespace from /etc/timezone
2021-09-24 13:49:04 -04:00
create gh release on tag For #210 * update changelog format so that `parse-changelog` is happy. * add the example from taiki-e/create-gh-release-action verbatim. Fingers crossed it works in my setup.
2022-04-13 18:00:30 -04:00
## 0.6.6 (2021-09-23)
bump etag format version when headers change I forgot to do this in 27395ec resulting in #146. Bump the version now, and update the digest used in the tests so they will remind me to bump the version any time the headers change.
2021-08-19 12:48:10 -04:00
* fix [#146](https://github.com/scottlamb/moonfire-nvr/issues/146): "init
segment fetch error" when browsers have cached data from `v0.6.4` and
before.
document and check minimum SQLite version Fixes #147
2021-08-19 13:02:25 -04:00
* fix [#147](https://github.com/scottlamb/moonfire-nvr/issues/147): confusing
`nvr init` failures when using very old versions of SQLite.
add changelog entry for #157
2021-08-31 19:44:53 -04:00
* fix [#157](https://github.com/scottlamb/moonfire-nvr/issues/157): broken
live view when using multi-view and selecting the first listed camera
then selecting another camera for the upper left grid square.
handle stale RTSP sessions * upgrade to Retina 0.3.1 which automatically tears down sessions * wait out stale sessions before reconnecting * wait for teardown to complete before shutting down This adds some pressure on #117: it will keep waiting for the stale session to expire even if the user has requested shutdown. I'll try to address that next.
2021-09-10 00:14:01 -04:00
* support `--rtsp-transport=udp`, which may work better with cameras that
use old versions of the live555 library, including many Reolink models.
* send RTSP `TEARDOWN` requests on UDP or with old live555 versions; wait out
stale sessions before reconnecting to the same camera. This may improve
reliability with old live555 versions when using TCP also.
* improve compatibility with cameras that send non-compliant SDP, including
models from Geovision and Anpviz.
shutdown better After a frustrating search for a suitable channel to use for shutdown (tokio::sync::watch::Receiver and futures::future::Shared<tokio::sync::oneshot::Receiver> didn't look quite right) in which I rethought my life decisions, I finally just made my own (server/base/shutdown.rs). We can easily poll it or wait for it in async or sync contexts. Most importantly, it's convenient; not that it really matters here, but it's also efficient. We now do a slightly better job of propagating a "graceful" shutdown signal, and this channel will give us tools to improve it over time. * Shut down even when writer or syncer operations are stuck. Fixes #117 * Not done yet: streamers should instantly shut down without waiting for a connection attempt or frame or something. I'll probably implement that when removing --rtsp-library=ffmpeg. The code should be cleaner then. * Not done yet: fix a couple places that sleep for up to a second when they could shut down immediately. I just need to do the plumbing for mock clocks to work. I also implemented an immediate shutdown mode, activated by a second signal. I think this will mitigate the streamer wait situation.
2021-09-23 18:55:53 -04:00
* fix [#117](https://github.com/scottlamb/moonfire-nvr/issues/117): honor
changelog tweak
2021-09-23 21:16:29 -04:00
shutdown requests when out of disk space, instead of retrying forever.
shutdown better After a frustrating search for a suitable channel to use for shutdown (tokio::sync::watch::Receiver and futures::future::Shared<tokio::sync::oneshot::Receiver> didn't look quite right) in which I rethought my life decisions, I finally just made my own (server/base/shutdown.rs). We can easily poll it or wait for it in async or sync contexts. Most importantly, it's convenient; not that it really matters here, but it's also efficient. We now do a slightly better job of propagating a "graceful" shutdown signal, and this channel will give us tools to improve it over time. * Shut down even when writer or syncer operations are stuck. Fixes #117 * Not done yet: streamers should instantly shut down without waiting for a connection attempt or frame or something. I'll probably implement that when removing --rtsp-library=ffmpeg. The code should be cleaner then. * Not done yet: fix a couple places that sleep for up to a second when they could shut down immediately. I just need to do the plumbing for mock clocks to work. I also implemented an immediate shutdown mode, activated by a second signal. I think this will mitigate the streamer wait situation.
2021-09-23 18:55:53 -04:00
* shut down immediately on a second `SIGINT` or `SIGTERM`. The normal
"graceful" shutdown will still be slow in some cases, eg when waiting for a
RTSP UDP session to time out after a `TEARDOWN` failure. This allows the
impatient to get fast results with ctrl-C when running interactively, rather
than having to use `SIGKILL` from another terminal.
bump etag format version when headers change I forgot to do this in 27395ec resulting in #146. Bump the version now, and update the digest used in the tests so they will remind me to bump the version any time the headers change.
2021-08-19 12:48:10 -04:00
create gh release on tag For #210 * update changelog format so that `parse-changelog` is happy. * add the example from taiki-e/create-gh-release-action verbatim. Fingers crossed it works in my setup.
2022-04-13 18:00:30 -04:00
## 0.6.5 (2021-08-13)
switch default RTSP library to retina
2021-06-28 19:38:21 -04:00
UI: improve aspect ratio handling As written in the changelog: Live streams formerly worked around a Firefox pixel aspect ratio bug by forcing all videos to 16:9, which dramatically distorted 9:16 camera views. Playback didn't, so anamorphic videos looked correct on Chrome but slightly stretched on Firefox. Now both live streams and playback are fully correct on all browsers.
2021-08-12 16:32:01 -04:00
* UI: improve video aspect ratio handling. Live streams formerly worked
around a Firefox pixel aspect ratio bug by forcing all videos to 16:9, which
dramatically distorted 9:16 camera views. Playback didn't have the same
workaround, so anamorphic videos looked correct on Chrome but slightly
stretched on Firefox. Now both live streams and playback are fully correct
on all browsers.
better error msg on live view when misconfigured Improves (but doesn't fix) #119 and #120.
2021-08-13 15:02:42 -04:00
* UI: better error messages on live view when browser is unsupported,
`sub` stream is unconfigured, or `sub` stream is not set to record.
upgrade to retina v0.1.0
2021-08-13 14:48:58 -04:00
* upgrade to retina v0.1.0, which uses `SET_PARAMETERS` rather than
`GET_PARAMETERS` as a RTSP keepalive. GW Security cameras would ignored
the latter, causing Moonfire NVR to drop the connection every minute.
UI: improve aspect ratio handling As written in the changelog: Live streams formerly worked around a Firefox pixel aspect ratio bug by forcing all videos to 16:9, which dramatically distorted 9:16 camera views. Playback didn't, so anamorphic videos looked correct on Chrome but slightly stretched on Firefox. Now both live streams and playback are fully correct on all browsers.
2021-08-12 16:32:01 -04:00
create gh release on tag For #210 * update changelog format so that `parse-changelog` is happy. * add the example from taiki-e/create-gh-release-action verbatim. Fingers crossed it works in my setup.
2022-04-13 18:00:30 -04:00
## 0.6.4 (2021-06-28)
switch default RTSP library to retina
2021-06-28 19:38:21 -04:00
prepare v0.6.4
2021-06-28 23:30:42 -04:00
* Default to a new pure-Rust RTSP library, `retina`. If you hit problems, you
can switch back via `--rtsp-library=ffmpeg`. Please report a bug if this
helps!
* Correct the pixel aspect ratio of 9:16 sub streams (eg a standard 16x9
camera rotated 90 degrees) in the same way as 16:9 sub streams.
create gh release on tag For #210 * update changelog format so that `parse-changelog` is happy. * add the example from taiki-e/create-gh-release-action verbatim. Fingers crossed it works in my setup.
2022-04-13 18:00:30 -04:00
## 0.6.3 (2021-03-31)
build cleanly with nightly Rust 2021-03-14+ The CI nightly builds had been broken with the following error: ``` error: custom inner attributes are unstable --> /home/runner/work/moonfire-nvr/moonfire-nvr/server/target/debug/build/moonfire-db-415ce696a754c614/out/schema.rs:10:4 | 10 | #![rustfmt::skip] | ^^^^^^^^^^^^^ | = note: `#[deny(soft_unstable)]` on by default = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! = note: for more information, see issue #64266 <https://github.com/rust-lang/rust/issues/64266> ``` I'd thought this was by mistake given that #[rustfmt::skip] is still advertised on rustfmt's github page, but maybe not. Looks like rust-protobuf's newest version uses `#![cfg_attr(rustfmt, rustfmt::skip)]` to avoid this error. Also fix a warning on nightly about an extraneous semicolon.
2021-03-24 11:01:48 -04:00
Prepare v0.6.3 release ...including changelog and new screenshots in the README.
2021-03-31 18:21:09 -04:00
* New user interface! Besides a more modern appearance, it has better
error handling and an experimental live view UI.
build cleanly with nightly Rust 2021-03-14+ The CI nightly builds had been broken with the following error: ``` error: custom inner attributes are unstable --> /home/runner/work/moonfire-nvr/moonfire-nvr/server/target/debug/build/moonfire-db-415ce696a754c614/out/schema.rs:10:4 | 10 | #![rustfmt::skip] | ^^^^^^^^^^^^^ | = note: `#[deny(soft_unstable)]` on by default = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! = note: for more information, see issue #64266 <https://github.com/rust-lang/rust/issues/64266> ``` I'd thought this was by mistake given that #[rustfmt::skip] is still advertised on rustfmt's github page, but maybe not. Looks like rust-protobuf's newest version uses `#![cfg_attr(rustfmt, rustfmt::skip)]` to avoid this error. Also fix a warning on nightly about an extraneous semicolon.
2021-03-24 11:01:48 -04:00
* Compile fix for nightly rust 2021-03-14 and beyond.
fix incorrect prev_media_duration_90k calculation I spotted this by inspection: adding a media time and wall time didn't look right. I also confirmed the brokenness on my primary NVR: ``` sqlite> .mode column sqlite> select ...> r1.composite_id, ...> r1.prev_media_duration_90k, ...> r1.wall_duration_90k, ...> r1.media_duration_delta_90k, ...> r2.composite_id, ...> r2.prev_media_duration_90k ...> from ...> recording r1 join recording r2 on (r1.composite_id = r2.composite_id - 1) ...> where ...> r1.prev_media_duration_90k + r1.wall_duration_90k + r1.media_duration_delta_90k != ...> r2.prev_media_duration_90k ...> limit 5; 4296791095 2232623913716 5398956 154 4296791096 2232629312672 4296791096 2232629312672 5400016 38 4296791097 2232634712688 4296791097 2232634712688 5400729 105 4296791098 2232640113417 4296791098 2232640113417 5399024 80 4296791099 2232645512441 4296791099 2232645512441 5400770 124 4296791100 2232650913211 ``` In the first row, the second recording's prev_media_duration_90k is the first's prev_media_duration_90k plus its wall time, not its media time.
2021-03-26 01:09:29 -04:00
* Fix incorrect `prev_media_duration_90k` calculation. No current impact.
This field is intended to be used in an upcoming scrub bar UI, and when
not calculated properly there might be unexpected gaps or overlaps in
playback.
build cleanly with nightly Rust 2021-03-14+ The CI nightly builds had been broken with the following error: ``` error: custom inner attributes are unstable --> /home/runner/work/moonfire-nvr/moonfire-nvr/server/target/debug/build/moonfire-db-415ce696a754c614/out/schema.rs:10:4 | 10 | #![rustfmt::skip] | ^^^^^^^^^^^^^ | = note: `#[deny(soft_unstable)]` on by default = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! = note: for more information, see issue #64266 <https://github.com/rust-lang/rust/issues/64266> ``` I'd thought this was by mistake given that #[rustfmt::skip] is still advertised on rustfmt's github page, but maybe not. Looks like rust-protobuf's newest version uses `#![cfg_attr(rustfmt, rustfmt::skip)]` to avoid this error. Also fix a warning on nightly about an extraneous semicolon.
2021-03-24 11:01:48 -04:00
create gh release on tag For #210 * update changelog format so that `parse-changelog` is happy. * add the example from taiki-e/create-gh-release-action verbatim. Fingers crossed it works in my setup.
2022-04-13 18:00:30 -04:00
## 0.6.2 (2021-03-12)
changelog, including upcoming 0.6.2
2021-03-10 20:53:29 -05:00
prepare version 0.6.2
2021-03-12 15:36:20 -05:00
* Fix panics when a stream's PTS has extreme jumps
([#113](https://github.com/scottlamb/moonfire-nvr/issues/113))
changelog, including upcoming 0.6.2
2021-03-10 20:53:29 -05:00
* Improve logging. Console log output is now color-coded. ffmpeg errors
and panics are now logged in the same way as other messages.
prepare version 0.6.2
2021-03-12 15:36:20 -05:00
* Fix an error that could prevent the
`moonfire-nvr check --delete-orphan-rows` command from actually deleting
rows.
changelog, including upcoming 0.6.2
2021-03-10 20:53:29 -05:00
create gh release on tag For #210 * update changelog format so that `parse-changelog` is happy. * add the example from taiki-e/create-gh-release-action verbatim. Fingers crossed it works in my setup.
2022-04-13 18:00:30 -04:00
## 0.6.1 (2021-02-16)
changelog, including upcoming 0.6.2
2021-03-10 20:53:29 -05:00
* Improve the server's error messages on the console and in logs.
* Switch the UI build from the `yarn` package manager to `npm`.
This makes Moonfire NVR a bit easier to build from scratch.
* Extend the `moonfire-nvr check` command to clean up several problems that
can be caused by filesystem corruption.
* Set the page size to 16 KiB on `moonfire-nvr init` and
`moonfire-nvr upgrade`. This improves performance.
prepare version 0.6.2
2021-03-12 15:36:20 -05:00
* Fix mangled favicons
([#105](https://github.com/scottlamb/moonfire-nvr/issues/105))
changelog, including upcoming 0.6.2
2021-03-10 20:53:29 -05:00
create gh release on tag For #210 * update changelog format so that `parse-changelog` is happy. * add the example from taiki-e/create-gh-release-action verbatim. Fingers crossed it works in my setup.
2022-04-13 18:00:30 -04:00
## 0.6.0 (2021-01-22)
changelog, including upcoming 0.6.2
2021-03-10 20:53:29 -05:00
This is the first tagged version and first Docker image release. I chose the
version number 0.6.0 to match the current schema version 6.