Keep system page independent of trading config refresh
All checks were successful
deploy / deploy (push) Successful in 1m49s

Proof: System page no longer waits for unrelated trading-config refresh work; full npm test and production dashboard build pass before deployment.

Assumptions: System summary uses service and persisted operational sources only, while funds and strategy retain runtime trading-config refresh.

Still fake: Pod-local pg_stat_activity and deployed-image tag evidence remain unavailable without cluster credentials; exact all-time submission totals remain unavailable.
This commit is contained in:
philipp 2026-07-25 13:35:05 +02:00
parent fdde4d9e95
commit 727a7027a2

View file

@ -731,7 +731,7 @@ async function loadQuoteLifecycleLookupPayload({ identifier }) {
async function loadDashboardPage({ page, auth }) {
const sourceErrors = [];
const tradingConfig = await tradingConfigStore.forceRefresh();
const tradingConfig = page === 'system' ? null : await tradingConfigStore.forceRefresh();
const runtimeConfig = buildRuntimeConfig(tradingConfig);
const generatedAt = new Date().toISOString();
const load = (name, loader, fallback) => safeSourceLoad(name, loader, fallback, sourceErrors);
@ -1021,6 +1021,7 @@ function bodyField(body, snakeKey, camelKey) {
}
function buildRuntimeConfig(tradingConfig) {
tradingConfig = tradingConfig || {};
return {
...config,
...tradingConfig,