Skip to content

Release v1.445.0

Latest

Choose a tag to compare

@github-actions github-actions released this 20 Nov 20:18
· 2 commits to main since this release
90a8cca

This release was merged in PR #5621

@chainlink/tokenized-equity-adapter@1.8.0

Minor Changes

  • #5607 b751f0c Thanks @kyleburton-cl! - Add opt-in session-start gating to the 24/7 issuer-price-247 endpoint (env-gated via ISSUER_247_SESSION_START_GATING_ENABLED, default off): reports whose lastSeenTimestampNs predates the start of the session their marketStatus declares are rejected with 503 PRE_SESSION(...); WEEKEND/closed-span reports gate against the end of the last trading phase before the gap. An open-status report (REGULAR/PRE/POST/OVERNIGHT) is gated only while the market is currently open, so on a day tradinghours marks closed the schedule resolves no session start and gating falls through to the hard-coded fallback (or fails closed when no tier resolves one) rather than anchoring to a session open from up to five days back (a phase without an end counts as not open, so a missing end cannot bypass the guard). Indeterminate sessions (UNKNOWN/unmapped marketStatus or an unresolvable session start) fail closed with 503 Session start unknown — there is no fail-open toggle (ADR-0007). Also flattens the hard-coded fallback session schedule to a single per-market entry with per-phase end times (24/5 behavior unchanged), parses the tradinghours market-session endTime passthrough, and routes both gating paths' tradinghours schedule fetches through a shared in-process stale-while-revalidate cache (TRADINGHOURS_SESSION_CACHE_TTL_MS, default 60s) whose blocking fetches are deduped per key and, after a failure, suppressed for TRADINGHOURS_SESSION_CACHE_FAILURE_BACKOFF_MS (default 5s) so an outage cannot stampede tradinghours or add the fetch timeout to every gated request. A missing or empty endTime is treated as "no end" rather than a malformed schedule. See docs/issuer-247-session-start-gating-tdd.md and docs/adr/0007-247-session-start-gating-weekend-and-fail-closed.md.

Patch Changes

  • #5607 b751f0c Thanks @kyleburton-cl! - Alert-facing logging for session-start gating schedule failures (24/5 and 24/7): a distinct error line (Market schedule undetermined: …) now discriminates the two no-schedule-tier causes — an invalid market session name (unknown sessionMarketType, logged up front since tradinghours cannot resolve the type either) vs. no fallback schedule entry for the market (logged only when the tradinghours fetch also fails or cannot run — a healthy tradinghours is itself a schedule tier, so the line stays quiet during healthy operation) — which previously surfaced only as an unattributed 503 Session start unknown. A malformed tradinghours schedule (unparseable phase time/endTime) is now rejected whole and lands in the existing TradingHoursEA request failed line instead of silently propagating NaN timestamps. The 24/7 gate gains the 24/5 fallback-activation warn (fetched schedule has no transition opening the report's session). The TradingHoursEA request failed line is now throttled to one per minute per market/type, so a sustained outage stays visible without re-logging on every gated request (the cache's failure backoff suppresses the upstream fetch, not the caller's log). No gating behavior change.

@chainlink/tradinghours-adapter@0.9.0

Minor Changes

  • #5607 b751f0c Thanks @kyleburton-cl! - Add endTime to each market-session transition (additive passthrough of the upstream phase end), so callers can derive the start of closed spans (weekends/holidays), and widen the hours-multiday query window from [now-1d, now+1d] to [now-5d, now+1d] so the last phase before a multi-day closure stays in reach. See docs/adr/0001-market-session-exposes-phase-end-times.md.

Patch Changes

  • #5607 b751f0c Thanks @kyleburton-cl! - market-session: endTime is now typed optional to match upstream (which may omit end on some phases) and is only emitted when the upstream phase end is non-empty — an empty-string end previously passed through and parsed to NaN downstream, rejecting the whole schedule. A schedule with recognized phases missing their end logs one warning per parse (listing the phases) instead of one error per phase, in case upstream omits an end. Consumers that derive closed-span (WEEKEND/holiday) starts from phase ends treat phases without an end as having no end and fall back to their hard-coded schedule.