Luis López

@mfisher87 correct! we could also implement pagination like in the stac search results `results.next_page()` if we don't want to load all the results in one go.

We currently have no retry attempts, the only "smart" thing `earthaccess` does is that if a granule already exist in the target path it won't try to download it again....

Hi Dean, thanks for opening this issue! This is happening because local instances are not shared automatically in Dask distributed computations. When we distribute the function to the workers the...

The check is intended to verify in-region execution but shouldn't be limited to EC2, I think your change would be a valid PR if it works the same way in...

I think we should keep it open until one of the proposed solutions works for this use case.

Just keep in mind that for Dask we should try to match the worker number to the available CPUs. The total memory of the VM will be divided equally for...

Nice! (the part of the original issue being resolved) but this should be documented. I wonder if we can have a "earthaccess for distributed workflows" tutorial. FWIW, I managed to...

> Maybe there could be an option to suppress the output? Certainly, that could be implemented (probably upstream to pqdm)

For some reason `%%capture` didn't work with Dask output.

I like what you're proposing @jhkennedy, and one would think that this should already be on a package that would work in all the execution environments in AWS, EC2, ECS,...