<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Transient bugs that self-resolved]]></title><description><![CDATA[<p dir="auto">Two issues that reproduced initially, then resolved on their own within a few days — known/fixed bugs?</p>
<p dir="auto">Two lower-priority items from our Enterprise trial evaluation that we wanted to flag, mainly for our own confidence that they won't regress, since both resolved without any change on our end.</p>
<ol>
<li>
<p dir="auto">pgutil vulns assess returning 500 — for every assessment type, regardless of auth method. Re-tested three days later with no changes on our side — now completes successfully.</p>
</li>
<li>
<p dir="auto">Non-admin package promotion via the API returning 403 — with every combination of "Promote Packages" permission we could construct, while the identical action succeeded via the web UI. Re-tested the same account three days later with a fresh package — now succeeds via the API too, confirmed by a real download.</p>
</li>
</ol>
<p dir="auto">Were either of these known issues fixed in a point release during that window, or something else (e.g. a permissions-cache propagation delay, similar to what we found separately with restart-dependent permission changes)? Just want to understand the root cause well enough to trust it won't come back.</p>
<p dir="auto">Thanks,<br />
Sai</p>
]]></description><link>https://forums.inedo.com/topic/5841/transient-bugs-that-self-resolved</link><generator>RSS for Node</generator><lastBuildDate>Tue, 15 Sep 2026 21:20:19 GMT</lastBuildDate><atom:link href="https://forums.inedo.com/topic/5841.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 15 Sep 2026 15:55:20 GMT</pubDate><ttl>60</ttl></channel></rss>