[PR #2867] [CLOSED] validate cron expressions on startup #3168

New issue

Closed

opened 2026-03-03 09:41:41 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 09:41:41 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/dani-garcia/vaultwarden/pull/2867
Author: @stefan0xC
Created: 10/26/2022
Status: ❌ Closed

Base: main ← Head: validate-config

📝 Commits (1)

1d2b8c5 validate cron expressions on startup

📊 Changes

1 file changed (+21 additions, -0 deletions)

View changed files

📝 src/config.rs (+21 -0)

📄 Description

Since the current way of panicking is not very user friendly (see #2593 and #2865) I've added validations for the cron expressions so the user will know which setting is misconfigured right away.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/dani-garcia/vaultwarden/pull/2867 **Author:** [@stefan0xC](https://github.com/stefan0xC) **Created:** 10/26/2022 **Status:** ❌ Closed **Base:** `main` ← **Head:** `validate-config` --- ### 📝 Commits (1) - [`1d2b8c5`](https://github.com/dani-garcia/vaultwarden/commit/1d2b8c55398a52cc0c27030b92d0b8b6c268179c) validate cron expressions on startup ### 📊 Changes **1 file changed** (+21 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/config.rs` (+21 -0) </details> ### 📄 Description Since the current way of panicking is not very user friendly (see #2593 and #2865) I've added validations for the cron expressions so the user will know which setting is misconfigured right away. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>