Lance Edgar
6b4280a6aa
feat: switch from setup.cfg to pyproject.toml + hatchling
2024-06-10 21:21:19 -05:00
Lance Edgar
784f75ac3f
Fix default dist filename for release task
...
not sure why this fix was needed, did setuptools behavior change?
2024-05-30 11:15:07 -05:00
Lance Edgar
f01faaf2f9
Update changelog
2024-05-30 11:14:16 -05:00
Lance Edgar
3fde33ac84
Fix pidfile args in typer commands
2024-05-29 07:27:22 -05:00
Lance Edgar
3f46ee6a30
Fix typo for purge command
2024-05-17 09:38:55 -05:00
Lance Edgar
9a39db4546
Add typer equivalents for rattail commands
2024-05-16 20:55:42 -05:00
Lance Edgar
d8b865da71
Update changelog
2023-11-30 22:24:15 -06:00
Lance Edgar
7a11ee7ad7
Update subcommand entry point group names, per wuttjamaican
2023-11-22 18:05:58 -06:00
Lance Edgar
e82e714417
Update changelog
2023-05-16 17:40:36 -05:00
Lance Edgar
a16f2ba718
Replace setup.py contents with setup.cfg
2023-05-16 13:21:26 -05:00
Lance Edgar
b887875f80
Update changelog
2023-02-12 11:22:06 -06:00
Lance Edgar
995e0dde0a
Refactor Query.get() => Session.get() per SQLAlchemy 1.4
2023-02-11 22:24:56 -06:00
Lance Edgar
f7f60eff85
Avoid error when re-running release task
2023-02-10 21:12:57 -06:00
Lance Edgar
acfc7f7d80
Update changelog
2023-02-10 21:09:51 -06:00
Lance Edgar
304cec9dd5
Address a warning from SQLAlchemy for declarative_base
...
as of 1.4 that has moved
2023-02-08 10:57:04 -06:00
Lance Edgar
fea643145a
Officially drop support for python2
2023-02-08 10:53:27 -06:00
Lance Edgar
a45a0b44d5
Use build module instead of invoking setup.py for release
2022-08-06 21:10:57 -05:00
Lance Edgar
1efdd9debd
Update changelog
2022-08-06 21:10:11 -05:00
Lance Edgar
1ddeb8a030
Register email profiles provided by this pkg
2022-08-06 21:09:27 -05:00
Lance Edgar
28ecdda0e6
Update changelog
2020-09-22 19:56:10 -05:00
Lance Edgar
4eebd454d5
Declare sort order for Appliance.probes relationship
2020-04-04 19:30:37 -05:00
Lance Edgar
1b03841c7f
Remove config for deprecated 'tempmon_critical_temp' email
...
we now have critical_high and critical_low as separate emails
2019-06-13 12:06:49 -05:00
Lance Edgar
873cd3def9
Update changelog
2019-04-23 22:22:07 -05:00
Lance Edgar
353abcc172
Make sure we use zero as fallback/default timeout values
2019-04-09 12:43:00 -05:00
Lance Edgar
8187c9532f
Update changelog
2019-01-28 15:48:57 -06:00
Lance Edgar
cf27af81d4
Modify tempmon server logic to take "unfair" time windows into account
...
when a client or probe first are (re-)enabled, we can't expect to have readings
within the time window we'd normally be checking. previously we'd get false
alarms about "probe error status" etc. when this happened; hopefully no longer!
2019-01-25 19:49:46 -06:00
Lance Edgar
f31a0c4c22
Convert enabled for Client, Probe to use datetime instead of boolean
...
value is null if disabled, else timestamp of when it was last enabled
2019-01-25 19:33:49 -06:00
Lance Edgar
c45baaed5e
Add more template context for email previews
...
just to keep things from breaking outright..although this hasn't been given
much attention still, numbers may not make total sense
2018-10-31 17:20:35 -05:00
Lance Edgar
3b14a0b288
Update changelog
2018-10-25 09:01:19 -05:00
Lance Edgar
7212b07504
Fix bug when sending certain emails while checking probe readings
...
use common method to add more context for email template
2018-10-25 09:00:17 -05:00
Lance Edgar
ad3e647160
Update changelog
2018-10-24 19:20:44 -05:00
Lance Edgar
8220082359
Add try/catch for client's "read temp" logic
...
this can isolate an error for a certain probe, so that other probes can go
ahead and take their readings during each client run. that way only the bad
one is marked as "error" status by the server
2018-10-23 17:39:18 -05:00
Lance Edgar
b644818eef
Don't mark client as online unless it's also enabled
2018-10-23 17:38:38 -05:00
Lance Edgar
30f0fe0a84
Add "default" probe timeout logic for server readings check
...
this way we don't have to set those timeouts on every single probe
2018-10-23 10:25:08 -05:00
Lance Edgar
1f8507508a
Make dummy probe use tighter pattern for random readings
...
to make for a more reasonable-looking graph
2018-10-20 04:17:42 -05:00
Lance Edgar
44d012b3fd
Update release task to use twine for upload
2018-10-19 20:31:49 -05:00
Lance Edgar
157873dc16
Update changelog
2018-10-19 20:30:07 -05:00
Lance Edgar
0ff20eb753
Add image fields for Appliance table
...
raw, normalized, thumbnail
2018-10-19 19:16:06 -05:00
Lance Edgar
6be6467f59
Add appliance table, and probe "location" in that context
2018-10-19 17:51:25 -05:00
Lance Edgar
871a9154da
Update some timeout field docstrings, per latest refactor
2018-10-19 16:47:20 -05:00
Lance Edgar
19553edda6
Add per-status timeouts and tracking for probe status
...
i.e. this lets us keep track of when a probe becomes "high temp" and then later
if it becomes "critical high temp" we can still know how long it's been high
2018-10-19 14:58:30 -05:00
Lance Edgar
8be64c0580
Update changelog
2018-10-17 19:31:37 -05:00
Lance Edgar
5830c7bd15
Fix logic bug when checking readings for client
...
yikes! first probe whose readings were checked okay, was causing other probes
to just be skipped
2018-10-17 19:26:48 -05:00
Lance Edgar
3aa4185de9
Leverage common "now" value when sending emails from server
...
i.e. don't generate new "now" when sending an email, just use the "now" we
established when starting to check the readings
2018-10-17 19:18:34 -05:00
Lance Edgar
71db57b2e0
Add probe URL to email template context
2018-10-17 18:08:54 -05:00
Lance Edgar
d6ab9a60f1
Update changelog
2018-10-09 16:36:07 -05:00
Lance Edgar
5bf69a0c21
Add "recent readings" to email template context
2018-10-08 00:52:16 -05:00
Lance Edgar
b4c52319c6
Make client more tolerant of database restart
...
note that a retry is *not* attempted within a given "take readings" run.
rather, client will consider that full readings take to have failed, if any
part of it fails.
but then we keep track of type/amount of some (database connection) failures,
and will suppress logging the full error for first 3 attempts. in practice
this lets us recover from simple database restarts, and if database becomes
truly unavailable we'll hear about it shortly.
any other type of error is immediately logged on first failure.
2018-10-07 18:47:02 -05:00
Lance Edgar
2f7fa3430a
Make server more tolerant of database restart
...
note that a retry is *not* attempted within a given "check readings" run.
rather, server will consider that full readings check to have failed, if any
part of it fails.
but then we keep track of type/amount of some (database connection) failures,
and will suppress logging the full error for first 3 attempts. in practice
this lets us recover from simple database restarts, and if database becomes
truly unavailable we'll hear about it shortly.
any other type of error is immediately logged on first failure.
2018-10-07 18:16:18 -05:00
Lance Edgar
b4fa6a17c5
Add "status since" to template context for email alerts
2018-10-06 20:17:46 -05:00
