From the commit message for fd461335341ddabae96714b2b0841023c4020a9d:
In v6.3.6, we bumped atlassian-python-api from 3.41.4. That bump included a PR which changed the way the library fetched projects. This somehow affected our project when we fetched visible projects and issue types in the heartbeat. We never fully determined the root cause, but the while loop in the linked PR was suspect.
In this commit, we make further improvements to the code that's involved in the heartbeat to make it more efficient.
Note that one of the tradeoffs we made for now was hardcoding the maximum number of projects that may be configured at 50. This is due to the way we fetch issue types by project. This is something that we can fix in the future, but is not a problem that we need to solve for now since we only have 26 projects configured.
From the commit message for fd461335341ddabae96714b2b0841023c4020a9d:
In v6.3.6, we bumped atlassian-python-api from 3.41.4. That bump included a PR which changed the way the library fetched projects. This somehow affected our project when we fetched visible projects and issue types in the heartbeat. We never fully determined the root cause, but the while loop in the linked PR was suspect.
In this commit, we make further improvements to the code that's involved in the heartbeat to make it more efficient.
Note that one of the tradeoffs we made for now was hardcoding the maximum number of projects that may be configured at 50. This is due to the way we fetch issue types by project. This is something that we can fix in the future, but is not a problem that we need to solve for now since we only have 26 projects configured.