This happened while running a very long conversion on BitBucket. Is this a case of the same token (maybe the same connection object?) being used for the duration of the entire run? And if so, could you renegotiate the session and get a new token in the handler for this exception?
My SSH knowledge is very poor, so I can't say if this theory makes any sense whatsoever.
This happened while running a very long conversion on BitBucket. Is this a case of the same token (maybe the same connection object?) being used for the duration of the entire run? And if so, could you renegotiate the session and get a new token in the handler for this exception?
My SSH knowledge is very poor, so I can't say if this theory makes any sense whatsoever.