FuelLabs/sway · error · anyhow::Error

dep_path: registry dependencies are not yet supported

Error message

dep_path: registry dependencies are not yet supported

What it means

Error "dep_path: registry dependencies are not yet supported" thrown in FuelLabs/sway.

Source

Thrown at forc-pkg/src/source/reg/mod.rs:420

                        node if node == IPFSNode::public() => IPFSNode::fuel(),
                        node => node,
                    };
                    fetch(fetch_id, &pinned, &node).await
                })?;
            }
        }
        let path = {
            let _guard = lock.read()?;
            manifest::find_within(path, ctx.name())
                .ok_or_else(|| anyhow!("failed to find package `{}` in {}", ctx.name(), self))?
        };
        PackageManifestFile::from_file(path)
    }
}

impl source::DepPath for Pinned {
    fn dep_path(&self, _name: &str) -> anyhow::Result<source::DependencyPath> {
        bail!("dep_path: registry dependencies are not yet supported");
    }
}

impl From<Pinned> for source::Pinned {
    fn from(p: Pinned) -> Self {
        Self::Registry(p)
    }
}

/// Resolve a CID from index file and pinned package. Basically goes through
/// the index file to find corresponding entry described by the pinned instance.
fn resolve_to_cid(index_file: &IndexFile, pinned: &Pinned) -> anyhow::Result<Cid> {
    let other_versions = index_file
        .versions()
        .filter(|ver| **ver != pinned.source.version)
        .map(|ver| format!("{}.{}.{}", ver.major, ver.minor, ver.patch))
        .collect::<Vec<_>>()
        .join(",");

View on GitHub (pinned to 47e5e902fa)

When it happens

Trigger: Thrown at forc-pkg/src/source/reg/mod.rs:420 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of FuelLabs/sway@47e5e902fa (2026-08-16). Data as JSON: /api/errors/39f64f535837b9f0. Report an issue: GitHub.