RichardScottOZ

I have a a nice irregular highly patchy survey to have a look at some of this with.

Tricky, but reality...has to be done generally. It is a complicated thing to do in a general sense, so I don't think that matters...basic tests for the generic use cases...

Sounds reasonable to me!

This is just running one of the example files in the repo doing some simple calcs.

```python timed out 2024-11-23 06:49:50,337 [DEBUG] standalone.py:277 -- Found 0 free workers connected to VM instance lithops-master-dadab3 2024-11-23 06:49:50,337 [DEBUG] standalone.py:281 -- Going to create 2 new workers {'username': 'ubuntu',...

some testing yesterday I did this, which enabled the master VM to start ```python def get_ssh_client(self): """ Creates an ssh client against the VM """ #if self.public: if self.public and...

Here, looking at public IP I think? ```python 2024-11-23 07:10:32,657 [DEBUG] ssh_client.py:59 -- 10.1.111.11 ssh client created 2024-11-23 07:10:34,094 [DEBUG] standalone.py:277 -- Found 0 free workers connected to VM instance...

When I changed it from default spot, got further ```python 2024-11-23 07:22:02,997 [DEBUG] aws_ec2.py:1275 -- VM instance lithops-worker-f12ca4e5 created successfully 2024-11-23 07:22:03,973 [DEBUG] aws_ec2.py:1275 -- VM instance lithops-worker-d10f6430 created successfully...

I wouldn't think that example takes very long to run though ```python 2024-11-23 07:22:09,590 [INFO] wait.py:101 -- ExecutorID 661f55-0 - Waiting for 3 function activations to complete 2024-11-23 07:22:13,440 [DEBUG]...

and with not spot lithops worker list tells me ```bash Worker Name Created Instance Type Processes Runtime Mode Status TTD ----------------------- ----------------------- --------------- ----------- --------- ------ ---------- ------- lithops-worker-f12ca4e5 2024-11-22...