Debug logs not visible anymore

Issue #2178 duplicate
Kevin Germain created an issue

When I try to access debug log, now the panel is totally blank.

I’ve tried to:

  • Removed the tab and access it manually, same result
  • Restart the IDE, same result

If I access another repo, it works well.

Comments (6)

  1. Scott Wells repo owner

    Hi can you please verify that you're on the very latest versions of both the base JetBrains IDE and the IC2 plugin? If so and this is still happening, can you please send me your idea.log from right after you open the Log Analyzer tool window? You can find it using Help>Show Log in Explorer.

  2. Kevin Germain reporter

    Hi Scott, thank you for your answer, sorry for the delay due to the weekend.

    I confirm that Intellij and IC2 are up to date.

    During my last test on Friday, no error message or other appeared.
    This morning when I opened the Log Analyzer to export a log file, an invalid session error message appeared (no credentials issue but really session-related message).
    Sorry I didn't think to make a screenshot.

    I set up a new OAuth connection and assigned it to the project and it works again.
    So I think that's where the problem lies.

    For information, I am constantly working on this project and had proceeded to a deployment the minute before so the connection was theoretically valid.

    I think that for the moment this issue can be marked as solved.
    I keep it handy and if the problem occurs again I will refer to it in my new message.

    Thank you again for your reactivity.

  3. Scott Wells repo owner

    Okay. I've seen a situation reported by a few folks where the access token reported by the CLI may not be valid any longer and the workaround is to remove/re-auth the same connection. That could well be what's going on as deployment uses the CLI but Log Analyzer uses the access token to invoke APIs directly, and that would explain the behavior you saw. Certainly if you see this again, feel free to reopen and we'll investigate further.

  4. Scott Wells repo owner

    Merging this into #2182 (even though this one came first) as it documents the stale session ID issue much more thoroughly.

  5. Log in to comment