`drupalorg issue:show --format=llm` unable to find latest comments

[wimleers]

Genuinely started using the skill you announced at https://mglaman.dev/blog/drupalorg-cli-080-gitlab-issue-fork-and-merge-request-commands — thanks so much! 🙏

Context

• I have your drupalorg-cli AI skills installed :)
• I have an AI working on https://www.drupal.org/project/canvas/issues/3578142
• While it was doing its thing, I was doing research in Drupal core. I updated the issue with new info in comment #6
• I informed the AI: "FYI a new comment with a new insight was posted — ensure the relevant @todo is added to the code you propose."

Problem

That is when I observed an inability to fetch this new comment, which is impairing real-time human-in-the-loop collaboration.

Output

Let me check the latest comment on the issue:
# Fetch latest issue comments
$ drupalorg issue:show 3578142 --with-comments --format=llm

then it did

The issue still shows the same comments I read before — the API cache might be stale. Let me try clearing the cache and fetching again:
# Clear cache and re-fetch issue
$ drupalorg cache:clear && drupalorg issue:show 3578142 --with-comments --format=llm
There are no commands defined in the "cache" namespace.

😂

Then:

# Fetch issue without cache
$ drupalorg issue:show 3578142 --with-comments --format=llm --no-cache 2>/dev/null || drupalorg issue:show 3578142 --with-comments --format=text

Finally:

The issue still shows the same 5 comments. Let me check the issue page directly via web fetch to see if there's a newer comment:
% WebFetch https://www.drupal.org/project/canvas/issues/3578142
Found it. Comment #6 mentions the upstream issue #3001284: Allow plugin derivers to specify cache tags for their definitions. And the issue summary was updated to include:

It's totally possible that d.o's HTTP API caching is what's getting in the way, but I think this repo's skill would be the ideal place to standardize some strategy to handle this.

[mglaman]

I bet it's the http caching on D.o, I removed all internal caching here (but the AI seems to think it exists! Something must have snuck into a skill).

I wonder if there's a comments endpoint to filter by issue ID that is busted faster. But I guess the problem would also exist for issue summary updates on the issue

[wimleers]

I'd bet the same.

Could we add a --now parameter to drupalorg-cli that would bypass it by then (and only then!) setting ?ts=<unix timestamp>?