4 ms·
GitHub says there could have been sessions that were leaked but can't be identified now: "While our log analysis, conducted from March 5 through March 8, confi
by Boltgolt 6y ago
GitHub says there could have been sessions that were leaked but can't be identified now:
"While our log analysis, conducted from March 5 through March 8, confirmed that this was a rare issue, it could not rule out the possibility that a session had been incorrectly returned but then never used."
Those sessions are now invalidated and apparently never used