Fix freply crash on unmatched braces

[lorenzo132]

No description provided.

[Copilot]

Pull request overview

This PR updates the bot’s SafeFormatter to avoid crashing when user-provided format strings (notably freply) contain malformed/unmatched braces, by falling back to formatting only complete {field} occurrences instead of rejecting the entire message.

Changes:

• Added a SafeFormatter.format() override that catches certain brace-related ValueErrors from string.Formatter.
• Implemented a regex-based fallback that formats complete replacement fields individually and leaves malformed parts untouched.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Suppressed comments (1)

core/models.py:373

• The fallback path depends on exact ValueError message strings to decide whether to recover, which is brittle across Python versions. Additionally, the per-field formatter currently swallows any ValueError and returns the raw placeholder, which can silently hide real formatting errors (e.g., invalid format specs) whenever the message contains an unrelated unmatched brace.

Consider always attempting the safe per-field fallback on ValueError, but only suppressing ValueErrors that are truly brace-related; re-raise other ValueErrors so formatting errors aren’t silently ignored.

    def format(self, format_string, /, *args, **kwargs):
        try:
            return super().format(format_string, *args, **kwargs)
        except ValueError as exc:
            if str(exc) not in self._UNMATCHED_BRACE_ERRORS:

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

[sebkuip]

LGTM