Skip to content

fix: add robust date parsing in schedule_fn #655

fix: add robust date parsing in schedule_fn

fix: add robust date parsing in schedule_fn #655

Re-run triggered November 4, 2025 17:58
Status Failure
Total duration 23s
Artifacts 1

ci.yaml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

1 error and 9 warnings
lint
Process completed with exit code 1.
format
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>05D4KaQAAAABmPoTXG68gQbwQEkAGihoUUEhYMzFFREdFMDYxOABFZGdl
format
Failed to restore: Cache service responded with 400
docs
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>06z4KaQAAAAA6ssyhhzh4SIIFvnyZV1xdUEhMMzBFREdFMDQxNABFZGdl
docs
Failed to restore: Cache service responded with 400
test (3.10)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>06j4KaQAAAACHJlo3zLL1RbuRj+Mbe8iSUEFPRURHRTA1MTQARWRnZQ==
test (3.10)
Failed to restore: Cache service responded with 400
test (3.12)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>06z4KaQAAAADrnJ3qUk44R4YzkpywBgEzUEhMMzBFREdFMDExOQBFZGdl
test (3.12)
Failed to restore: Cache service responded with 400
lint
Failed to restore: Cache service responded with 400

Artifacts

Produced during runtime
Name Size Digest
reference-docs
71.6 KB
sha256:72dde8bb6c0a03b6df09c23f5207649053a21c2001451be3c087ecd621749b52