Ruslan Kuprieiev
Ruslan Kuprieiev
@martindurant We did initially, but after using that in dvc for awhile, the conclusion we've reached is that `fs.` makes more sense from the usability perspective https://github.com/fsspec/filesystem_spec/issues/747#issuecomment-1296356031
Hey folks. I think I have to admit defeat here for now, after me getting laid off from Iterative, I'm no longer actively using this and just don't have the...
I suspect that there was simply no use case for this before to make it public. Probably can just contribute a PR.
Hi @Bizarious . Sounds like a bug, maybe you could pinpoint specific line in the code? If you are getting a permission error, I suppose you have a traceback for...
Might be worth putting these per every plugin (e.g. into dvc-s3 for s3) and test particular functionality (like index building). Testing all clouds in `dvc-bench` might be an overkill, this...
Though we have the infra in dvc-bench for running with different clouds, so maybe should fit in here after all.
> The superclass implementation would presumably default to writable. Yep, `read_only` would default to `False` and `immutable` to `False` as well. Maybe one could argue about potential defaults like `None`...
Reopening, still worth looking into.
Thanks for the interest, folks. @MFreidank Sorry, missed your message 🙁 @Fletchersan All config-related logic is in https://github.com/iterative/dvc/blob/main/dvc/config.py , validation is happening in https://github.com/iterative/dvc/blob/8ea9d3edef146c239086a7aec3cec9ead1bd32a9/dvc/config.py#L383 so it is likely this validation...