socket.py | Python socket 编程实战 | Socket library

I modified some things in the code but never got the saame error as you. This code works for me and even with the exact link of your video :

You need to specify the port. In this case, it's 587 for TSL.

Somehow it works, but I don't have profound knowledge to explain why.

I had the same problem, so there is a solution:

As I understand it, coverage is about reporting how much of your codebase is tested, not which tests to run. What you're doing is excluding things from a report, not stopping the data for the report being created.

What you should do is skip tests if you know they're going to fail (due to external configuration). Fortunately pytest provides for this with the skipif decorator.

I would create a function in tests/conftest.py which skips tests if the VPN is active. Something like:

try these:

AttributeError: module 'mysql' has no attribute 'connector'

Attribute error:module 'mysql' has no attribute 'connector'

basically change the import to

from mysql import connector

Try this1

The link you posted was a website link, not an FTP link.

However, this would work at the start of your script:

For completeness, moving the answer from @Clement in a comment to an answer:

This error can happen when loading the oscrypto (libcrypto) if the memory usage is too high. The OOM state cascades upward.

@hardillb was right the error message had to do with an connection issue. The broker was never able to connect due to the fact that within docker it wasn't in the correct network within docker.

Reduce the chunk_size from 10000 to the default of 500 and I'd expect it to work. You probably want to disable automatic retries if that can give you duplicates.

When creating your Elasticsearch object, you specified chunk_size=10000. This means that the streaming_bulk call will try to insert chunks of 10000 elements. The connection to elasticsearch has a configurable timeout, which by default is 10 seconds. So, if your elasticsearch server takes more than 10 seconds to process the 10000 elements you want to insert, a timeout will happen and this will be handled as an error.

When creating your Elasticsearch object, you also specified retry_on_timeout as True and in the streaming_bulk_call you set max_retries=max_insert_retries, which is 3.

This means that when such a timeout happens, the library will try reconnecting 3 times, however, when the insert still has a timeout after that, it will give you the error you noticed. (Documentation)

Also, when the timeout happens, the library can not know whether the documents were inserted successfully, so it has to assume that they were not. Thus, it will try to insert the same documents again. I don't know how your input lines look like, but if they do not contain an _id field, this would create duplicates in your index. You probably want to prevent this -- either by adding some kind of _id, or by disabling the automatic retry and handling it manually.

There is two ways you can go about this:

• Increase the timeout
• Reduce the chunk_size

streaming_bulk by default has chunk_size set to 500. Your 10000 is much higher. I don't you can expect a high performance gain when increasing this over 500, so I'd advice you to just use the default of 500 here. If 500 still fails with a timeout, you may even want to reduce it further. This could happen if the documents you want to index are very complex.

You could also increase the timeout for the streaming_bulk call, or, alternatively, for your es object. To only change it for the streaming_bulk call, you can provide the request_timeout keyword argument: