Peter Fogh

I also got the same `Loading widget...` error and later on when trying to fix it I also got the `Widget loads, returns Error displaying widget: model not found` error...

Hi @thomasaarholt, Unix, more specific: ``` > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic ``` Yah, I should say...

I have the same problem "got Future attached to a different loop" when using windows credentials with `storage_options={'account_name': account_name, 'anon': False}`. I use dask version `dask.__version__ ='2022.7.0'` This exact code...

After updating my `adlfs` version I do not have the "got Future attached to a different loop" problem anymore. Old version: ``` - python=3.9.13=h6244533_2 - adlfs=2022.10.0=pyhd8ed1ab_0 - azure-common=1.1.27=pyhd3eb1b0_0 - azure-core=1.26.0=pyhd8ed1ab_0...

Okay @faurholdt thanks for the quick reply, :)

I cannot close the issue - @faurholdt please close it if you can - else I'm sure @hayesgb can? :)

I think this issue is fixed by #328, thus it can be closed. And the comment about the issue can be removed from https://github.com/fsspec/adlfs/blob/b01b30d5bbffcb0a49033cc4c90af1cba9da3fe2/adlfs/spec.py#L255

Hi all, @mdekstrand and @dmpetrov. I do not have any strong opinions about DVC and parallelisation, I can just give my point of view. I’m not sure, what of the...

@dmpetrov, yes, of course. We benefit from Dask in multiple ways. 1. We can sent computation to a remote machine or cluster, all nicely hidden away with a common abstract...