mirrors/arti.git/crates/arti/src/watch_cfg.rs, branch arti-v0.3.0

squash! Bump every crate's edition to 2021.

2022-04-25T17:06:26Z

Remove all `use` statements for `TryFrom` and `TryInto`. These are now redundant in Rust 2021.

ApplicationConfig: abolish accessor

2022-03-21T12:39:50Z

Move ArtiConfig to new arti::cfg module

2022-03-21T11:42:33Z

Code motion and import fixups.

arti: Make main module entrypoints pub

2022-03-11T18:28:15Z

This does not constitute any kind of stable API promise. But it might allow people to use our arti client code in novel ways.

Upgrade to newer version of config crate.

2022-02-25T14:20:48Z

Properly linkify two doc comment xrefs to issues

2022-02-04T15:11:44Z

Fixes these messages: warning: this URL is not a hyperlink --> crates/arti/src/watch_cfg.rs:115:5 | 115 | /// https://github.com/notify-rs/notify/issues/165 and | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use an automatic link instead: `` | = note: `#[warn(rustdoc::bare_urls)]` on by default = note: bare URLs are not automatically turned into clickable links warning: this URL is not a hyperlink --> crates/arti/src/watch_cfg.rs:116:5 | 116 | /// https://github.com/notify-rs/notify/pull/166 . | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use an automatic link instead: `` | = note: bare URLs are not automatically turned into clickable links

Document that `notify` behavior is strange with symlinks

2022-02-03T16:11:21Z

(More specifically, `notify` behaves differently on different platforms. On some, it can watch specific directory objects on the filesystem, and so it only notices when _those_ directories change. If you change a symlink so that the canonical configuration file location is now in some other directory, `notify` won't notice. But on other platforms, notify just does "stat()" in a loop. On those, it _will_ notice if the configuration file changes.)

Avoid a potential infinite loop in configuration-watching

2022-02-03T14:38:58Z

Since the user can put their logfiles and configuration files in the same directory, writing to the log can trigger an event from `notify`. If we log every non-interesting event from `notify`, then we'll trigger the logs every time we log, and fill up the disk. This commit removes the offending log and adds a comment about why. If we someday decide we do need to log here, maybe we can rate-limit the messages or something.

Treat rescan events as meaning "reload configuration".

2022-02-03T14:36:12Z

Add a couple of TODOs about configuration-watching.

2022-02-02T20:43:42Z