Date: Tue, 06 Jun 2023 13:06:57 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 271867] security/gvmd missing dates in reports Message-ID: <bug-271867-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271867 Bug ID: 271867 Summary: security/gvmd missing dates in reports Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: acm@FreeBSD.org Reporter: stewart+FreeBSD-BugZilla@arnos-vale.net Assignee: acm@FreeBSD.org Flags: maintainer-feedback?(acm@FreeBSD.org) Created attachment 242636 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D242636&action= =3Dedit Wrap colon-adding code block in #ifndef __FreeBSD__ For reasons I've not gotten to the bottom of, the iso_time_internal() funct= ion of utils.c tries to add an extra colon but results in an "HH:MM::SS" time-format (i.e. doubled-up colon) which the moment.js front-end (correctl= y) fails to parse, thus all report dates (and likely elsewhere too) are render= ed as an empty string and appear missing. The attached patch wraps what I found to be the errant code block in #ifndef __FreeBSD__, which fixes it for me. I'd be interested to know if this is something specific to my setup though (13.2-RELEASE on AMD64), since I've not seen any mention of this elsewhere. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-271867-7788>