Closed reaperhulk closed 8 years ago
Have a look here: https://github.com/rackspace/gophercloud/issues/498
You'll want to limit the number of retries; reauth will definitely recurse to death if left unchecked.
I should add a comment about that above the AllowReauth
field.
Ah, thank you. I will go ahead and implement those retry limits. A comment would definitely be helpful! :)
👍 thanks for the quick response. I'll go ahead and close this
@jrperritt Reflecting a bit more on this it seems like the set of circumstances that can lead to this crash are quite common so it feels a bit footgun-y to have it be the default reauth behavior. What do you think about having some retry limits be present by default?
I have a system using gophercloud to upload/download files from Rackspace Cloud Files. The relevant code looks something like this:
Originally we didn't have
Reauth
enabled so when the identity token expired we'd see errors. However, once we turned on reauth we eventually see a stack overflow that kills the go process entirely. The (mildly redacted) trace can be seen here.The trace seems to suggest that under certain conditions reauth may recurse until the stack limit is reached. I've looked a bit into it but haven't spotted what could cause that.