Skip to content

from_cloudpath does not supply token when middleauth+ is present in cloudpath #693

Open

Description

@ceesem

We use on-demand precomputed annotation formatting backed by the standard CAVE services.
For example, such a dynamic cloudpath could be: precomputed://middleauth+https://minnie.microns-daf.com/materialize/api/v3/datastack/minnie65_phase3_v1/table/cell_type_multifeature_combo/precomputed.

However, using

import cloudvolume
anno_path = `precomputed://middleauth+https://minnie.microns-daf.com/materialize/api/v3/datastack/minnie65_phase3_v1/table/cell_type_multifeature_combo/precomputed`
cloudvolume.from_cloudpath(anno_path)

results in the error:
HTTPError: 401 Client Error: UNAUTHORIZED for url: https://minnie.microns-daf.com/materialize/api/v3/datastack/minnie65_phase3_v1/table/cell_type_multifeature_combo/precomputed/info

Which suggests that the correct token was not provided since I have no auth issues with a different endpoint on the same server: cloudvolume.CloudVolume('graphene://middleauth+https://minnie.microns-daf.com/segmentation/table/minnie3_v1')

Activity

  1. william-silversmith commented on May 2, 2026

    @william-silversmith
    Contributor

    Huh. This worked for me. Have you tried updating CloudFiles? I was initially experiencing the same issue on 6.1.1 but it works on 6.3.0.

  2. ceesem commented on Jun 4, 2026

    @ceesem
    CollaboratorAuthor

    If I'm using cloud volume to do a task, it seems I should not have to guess which dependency I need to manually update to make it work.

  3. william-silversmith commented on Jun 4, 2026

    @william-silversmith
    Contributor

    I feel bad this caused problems, but all I can really offer is always make sure your environment is updated with all dependencies if you encounter an issue. Try a clean install in a new environment when a problem feels intractable, especially when using a newer feature (as cloudvolume.from_cloudpath and annotation reading are currently). cloud-files is frequently updated in tandem with CloudVolume (at one point in the distant past it was part of the CloudVolume repo). Hopefully, the code is stable enough now that these issues will not impact anyone for a bit (I haven't been seeing bug reports on this subsystem for now).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions