Skip to content

SG-34910 Fixup SSLEOFError exception#346

Merged
julien-lang merged 5 commits into
masterfrom
ticket/SG-34910-fixup-ssl-eol-exception
Jun 7, 2024
Merged

SG-34910 Fixup SSLEOFError exception#346
julien-lang merged 5 commits into
masterfrom
ticket/SG-34910-fixup-ssl-eol-exception

Conversation

@julien-lang
Copy link
Copy Markdown
Member

Use the existing re-attempt strategy in case of SSLEOFError

@julien-lang julien-lang marked this pull request as ready for review June 5, 2024 17:05
@julien-lang julien-lang force-pushed the ticket/SG-34910-fixup-ssl-eol-exception branch from e626ed4 to f9f50d3 Compare June 5, 2024 23:07
Copy link
Copy Markdown
Contributor

@carlos-villavicencio-adsk carlos-villavicencio-adsk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Comment thread shotgun_api3/shotgun.py
# the connection and make a new attempt.
LOG.debug("SSLEOFError: {}".format(e))
self._close_connection()
if attempt == max_rpc_attempts:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

self.config.max_rpc_attempts is hardcoding the value of 3. Maybe we can now get rid of this one and use self.MAX_ATTEMPTS instead. WDYT?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hardcoded yes and no. It's the default value of the config object but users can select a different value.

Also, I see that this variable is still used at other places. So I kind of want to keep it as is for the moment.

@julien-lang julien-lang merged commit f3a2230 into master Jun 7, 2024
@julien-lang julien-lang deleted the ticket/SG-34910-fixup-ssl-eol-exception branch June 7, 2024 19:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants