`wait_container_is_ready` throwing TimeoutException on first try
See original GitHub issueAfter updating to v3.5.0 our tests using PostgresContainer
s are failing.
My guess is that this has to do with the changes regarding transient exceptions. We use psycopg2
and the error thrown on unsuccessful connection is not inheriting sqlalchemy.exc.OperationalError
but rather is a plain AttributeError
with message:
'NoneType' object has no attribute '_stan_scope'
Issue Analytics
- State:
- Created a year ago
- Comments:10
Top Results From Across the Web
EJB Timer : put in a method with Exception, the @Timeout ...
In this case, the caller of an @Timeout method is the EJB container, which cannot know the intent of your application exception, so...
Read more >A reason for unexplained connection timeouts on Kubernetes ...
The Linux Kernel has a known race condition when doing source network address translation (SNAT) that can lead to SYN packets being dropped....
Read more >Waiting for containers to start or be ready - Testcontainers
This simple measure provides a basic check whether a container is ready for use ... If the default 60s timeout is not sufficient,...
Read more >Getting UnixHTTPConnectionPool read timeout #4486 - GitHub
I get this error message intermittently: ERROR: for testdb-data UnixHTTPConnectionPool(host='localhost', port=None): Read timed out.
Read more >Investigating timeout exceptions in StackExchange.Redis for ...
This setting means that if a synchronous call doesn't complete in the stipulated time, it will throw a timeout error. The error thrown...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, indeed I am using Instana! I’ll give 3.5.3 a go and see if that fixes it 🤞
Hm, good point. I’m really not sure where that
AttributeError
is coming from. Are you by any chance using https://github.com/instana/python-sensor/? That’s the only piece of code that I could find that references_stan_scope
.