needing to re-login to jira approximately every hour

[Bill Barry]

All day long I am seeing this in my vscode log:

  [2022-01-21 15:26:51:299] ---------------------------------------------------------------------- 
  [2022-01-21 15:26:51:299] curl -X GET -H "User-Agent:atlascode/2.x axios/0.19.2" -H "X-Atlassian-Token:no-check" -H "Content-Type:application/json" -H "Authorization:Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6Ik16bERNemsxTVRoRlFVRTJRa0ZGT0VGRk9URkJOREJDTVRRek5EZzJSRVpDT1VKRFJrVXdNZyJ9.eyJo..." "https://api.atlassian.com/ex/jira/.../rest/api/2/search?jql=...&maxResults=100&startAt=0" 
  [2022-01-21 15:26:51:299] ---------------------------------------------------------------------- 
  [2022-01-21 15:26:51:311] -4340 seconds remaining for auth token. 
  [2022-01-21 15:26:51:311] Need new auth token. 
  [2022-01-21 15:26:51:311] Checking to see if we're the ruling pid 
  [2022-01-21 15:26:51:311] Starting round 0 of negotiations 
  [2022-01-21 15:26:51:311] Pinging 16128 
  [2022-01-21 15:26:51:314] Attempting to ping atlascode-16128 
  [2022-01-21 15:26:51:315] 16128 acked 
  [2022-01-21 15:26:51:315] 16128 responded. 
  [2022-01-21 15:26:51:315] Ruling pid? false 
  [2022-01-21 15:26:51:315] This process isn't in charge of refreshing credentials. 
  [2022-01-21 15:26:51:604]   Error: Error executing JQL: Error: Request failed with status code 401
  [2022-01-21 15:26:56:338] getClient factory 
  [2022-01-21 15:26:56:338] creating client for https://api.atlassian.com/ex/jira/.../rest 
  [2022-01-21 15:26:56:338] client created 
  [2022-01-21 15:26:56:339] returning new client 
  [2022-01-21 15:26:56:339] Creating client for https://api.atlassian.com/ex/jira/.../rest 
  [2022-01-21 15:26:56:340] ---------------------------------------------------------------------- 

And the Jira issue list is not updating. When I open settings and log in it works for an hour and then starts failing again.

‌

vscode:

Version: 1.63.2 (user setup)
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3
Date: 2021-12-15T09:40:02.816Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19043

‌

Atlassian.atlascode 2.10.4

[Nick Rundquist]

I’m sorry to hear you’re having this issue. I have a few questions to help me diagnose this:

• If you log out the site (Remove it from the list on the extension configuration screen by clicking the 'x' on the right hand side) and log back in does it resolve the issue?
• Do you have multiple VS Code windows open?
• Do you have multiple Atlassian Accounts? (i.e. more than one username / password pairs you use to log in)

‌

[Bill Barry]

I will try this and see what happens in an hour.
I do have 3 Code windows open, all 3 connected to the same Jira and BB account (different repositories).
I have 1 account connected to a microsoft online account (office365 maybe? I don’t manage that bit)

[Bill Barry]

It is still happening.

[Nick Rundquist]

Bill, sorry to take so long to get back to you. If you’re still having trouble there is something you can do to help me track this down. After updating to the latest version (10.2.7) if you could check the logs from around the time you get logged out. Specifically, when you get logged out look for the window with logs that include the messages "Is responsible process: true" "Refreshing credentials." and see if there are any errors logged around that event.

‌

[Bill Barry]

Looking more into each window, it seems whenever this happens 1 or 2 windows have the -xxx seconds remain and the other is is fine. I cannot find any “Is responsible process: true” in the log for any of them and once I switch to the window that is logged in and interact with Jira within it, the other windows work again.

I do periodically get errors reaching bitbucket:

[2022-02-07 14:38:29:582] ----------------------------------------------------------------------
[2022-02-07 14:38:29:591]   Error: Error executing JQL: Error: getaddrinfo EAI_AGAIN api.atlassian.com
[2022-02-07 14:38:29:591]   Error: Error executing JQL: Error: getaddrinfo EAI_AGAIN api.atlassian.com
[2022-02-07 14:38:29:591]   Error: Error executing JQL: Error: getaddrinfo EAI_AGAIN api.atlassian.com
[2022-02-07 14:38:29:591]   Error: Error executing JQL: Error: getaddrinfo EAI_AGAIN api.atlassian.com
[2022-02-07 14:38:29:591]   Error: Error executing JQL: Error: getaddrinfo EAI_AGAIN api.atlassian.com
[2022-02-07 14:38:29:591]   Error: Error executing JQL: Error: getaddrinfo EAI_AGAIN api.atlassian.com
[2022-02-07 14:38:29:591]   Error: Error executing JQL: Error: getaddrinfo EAI_AGAIN api.atlassian.com
[2022-02-07 14:38:29:591]   Error: Error executing JQL: Error: getaddrinfo EAI_AGAIN api.atlassian.com
[2022-02-07 14:38:29:591]   Error: Error executing JQL: Error: getaddrinfo EAI_AGAIN api.atlassian.com
[2022-02-07 14:38:29:591]   Error: Error executing JQL: Error: getaddrinfo EAI_AGAIN api.atlassian.com
[2022-02-07 14:38:29:591]   Error: Error executing JQL: Error: getaddrinfo EAI_AGAIN api.atlassian.com
[2022-02-07 14:38:29:592]   Error: Error executing JQL: Error: getaddrinfo EAI_AGAIN api.atlassian.com
[2022-02-07 14:38:29:592]   Error: Error executing JQL: Error: getaddrinfo EAI_AGAIN api.atlassian.com
[2022-02-07 14:38:29:592]   Error: Error executing JQL: Error: getaddrinfo EAI_AGAIN api.atlassian.com
[2022-02-07 14:38:29:595] ----------------------------------------------------------------------

‌

This seems to be whenever I am doing something that uses significant bandwidth on the vpn tunnel, the corporate installed DNSFilter service on the machine loses a connection and prevents any new requests to anything from occurring. I don’t think they are related to this login issue (I am guessing based on behavior that it is some sort of issue about variables between windows).

Why are the jql lists being refreshed independently in each window if the auth token is shared across them?