jfrog / jfrog/jfrog-cli

vscode extension and filespec-schema.json fail

Open
#3,452 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
595
Forks
307
Avg merge
4d 17h
Merged PRs (30d)
17

Description

Describe the bug

The extension uses an url as listed in the instructions
I get the following error when it tries to utilize the extension.

Unable to load schema from 'https://github.com/jfrog/jfrog-cli/raw/v2/schema/filespec-schema.json': Not Found. The requested location could not be found.

I'm using pretty simple filespec example.

{
  "files": [
    {
      "aql": {
        "items.find": {
          "repo": "artifactory-repo",
          "type": "file",
          "path": {
            "$match": "*_assets*"
          },
          "$or": [
            {
              "$and": [
                {
                  "created": { "$gt": "${lastbackup}" }
                },
                {
                  "created": { "$lt": "${currenttime}" }
                }
              ]
            }
          ]
        }
      }
    }
  ]
}

Current behavior

Error's out

Reproduction steps

load vscode extension, and open a filespec.json file.

Expected behavior

not error

JFrog CLI version

2.102.0

Operating system type and version

"mcr.microsoft.com/devcontainers/python:3.12"

JFrog Artifactory version

No response

JFrog Xray version

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the VS Code extension's schema URL and its filespec-schema.json reference, then reproduce the problem by opening a filespec.json file in VS Code. Done means the extension resolves the schema without a Not Found error and the sample filespec opens without schema-loading errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
json, vscode
Domain
tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.