Log safemode errors #555
No reviewers
Labels
No labels
question
blocked
duplicate
needs
approval
needs
criteria
needs
estimate
needs
tests
question
step
doing
step
review
step
testing
step
todo
step
uat
type
admin
type
alert
type
bug
type
change
type
defect
type
dependencies
type
epic
type
idea
type
incident
type
investigation
type
spike
type
story
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
External/card-drop!555
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/554-log-safemode-error"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Log safemode errors so that its easier for maintainers to see when a card is wrong
#554
WIP: Log safemode errorsto Log safemode errorsApproved — this cleanly addresses #554 and improves operator visibility when safe mode engages.
Highlights:
CardMetadataFunctionnow logs the fullfile: messagestring when enabling safe mode (not just the message), and reuses the sameerrorMessagefor the API response.resynccorrectly gates onresult.IsSuccessinstead of truthiness on the result object — an important fix so failed runs are handled and logged.gdrivesync/resyncuser-facing copy now states that safe mode was activated and surfacesErrorMessagein the reply.Config.SetValue, and parse-failure paths.No merge blockers from my side.