Quiet routine per-tick service logs, surface real failures at WARNING

BaseService logged "Next run in Ns" at INFO on every single execution
of every service, including the 1-2s-interval pub/sub bridges
(presence/notification/live-view relays), drowning the console in
routine noise while actual failures (run_once errors, loop errors,
on_disable errors) were logged at the same INFO level and got lost in
it. log() now takes an optional level (default INFO, unchanged for
existing callers); the routine tick line drops to DEBUG and the three
failure paths move to WARNING. Added DEVPLACE_LOG_LEVEL (default INFO)
so DEBUG-level ticks stay available on demand without a code change.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Vnp7vzE4hvsytMo5YjszJm

This commit is contained in:

retoor

2026-09-08 20:47:16 +02:00

co-authored by

Claude Sonnet 5

parent 36e5378f19

commit eec1b3e3de

4 changed files with 11 additions and 8 deletions

									
										pyproject.toml
									
		+1
		-1
	
												View File
												
				@@ -1,6 +1,6 @@

				[project]

				name = "devplacepy"

				version = "1.0.8"

				version = "1.0.9"

				description = "DevPlace - The Developer Social Network"

				requires-python = ">=3.12"

				dependencies = [