-
-
Notifications
You must be signed in to change notification settings - Fork 32
Open
Description
It's pretty often when the release is created in a short time after closing some issues, but for that case dcli tool misses the recently closed issues for some reason.
So, when I close the issue and launch dcli maintainer:release-notes - I see the list of issues, but without last ones (one or more).
Here is an example - the output in 1-30 minutes after closing the 3364590 issue, the command: dcli maintainer:release-notes 1.0.0-alpha4:
<p><em>Add a summary here</em></p>
<h3>Contributors (1)</h3>
<p><a href="https://www.drupal.org/u/murz">Murz</a></p>
<h3>Changelog</h3>
<p><strong>Issues:</strong> 2 issues resolved.</p>
<p>Changes since <a href="https://www.drupal.org/project/opentelemetry/releases/1.0.0-alpha4">1.0.0-alpha4</a>:</p>
<h4>Feature</h4>
<ul>
<li><a href="https://www.drupal.org/node/3361612">#3361612</a> by <a href="https://www.drupal.org/u/murz">Murz</a>: Option to log each trace to Drupal Logger</li>
</ul>
<h4>Task</h4>
<ul>
<li><a href="https://www.drupal.org/node/3362985">#3362985</a> by <a href="https://www.drupal.org/u/murz">Murz</a>: Rework SpanExporter initialisation to catch all env variables</li>
</ul>
And here - is the same dcli maintainer:release-notes 1.0.0-alpha4 command output, but after several hours:
<p><em>Add a summary here</em></p>
<h3>Contributors (1)</h3>
<p><a href="https://www.drupal.org/u/murz">Murz</a></p>
<h3>Changelog</h3>
<p><strong>Issues:</strong> 3 issues resolved.</p>
<p>Changes since <a href="https://www.drupal.org/project/opentelemetry/releases/1.0.0-alpha4">1.0.0-alpha4</a>:</p>
<h4>Feature</h4>
<ul>
<li><a href="https://www.drupal.org/node/3364590">#3364590</a> by <a href="https://www.drupal.org/u/murz">Murz</a>: Add traceresponse HTTP header to responses</li>
<li><a href="https://www.drupal.org/node/3361612">#3361612</a> by <a href="https://www.drupal.org/u/murz">Murz</a>: Option to log each trace to Drupal Logger</li>
</ul>
<h4>Task</h4>
<ul>
<li><a href="https://www.drupal.org/node/3362985">#3362985</a> by <a href="https://www.drupal.org/u/murz">Murz</a>: Rework SpanExporter initialisation to catch all env variables</li>
</ul>
So, seems it's a caching issue on the Drupal.org infrastructure? Can we invent some workaround for this issue? Maybe just adding a timestamp or some random hash to a get parameter could resolve the problem?
Metadata
Metadata
Assignees
Labels
No labels