microsoft / microsoft/Microsoft-Fabric-workload-development-sample
[Bug] Unable to upload .nupkg file with schema version 1.0.0
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 58
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Workload Manifest Schema Version
1.0.0
Description
I am trying to upload and publish the NuGet package for my workload, but am getting an error notification saying "Please ensure you upload a valid .nupkg package file". This worked on March 9th, and did not work on March 16th. The only difference between the two uploads is the workload version in the WorkloadManifest.xml.
I tried running the validator from this repo, but it fails when trying to download the ItemDefinition.xsd with schema version 1.0.0.
Steps to Reproduce
- Set the schema version in the src/packages/manifest/Item1.xml and src/packages/manifest/WorkloadManifest.xml to 1.0.0.
- Build the backend project.
- In Fabric, attempt to upload a new version of the workload, choosing the .nupkg file from the bin corresponding to the build configuration you used.
Expected vs Actual Behavior
Expected: The new version of the workload should be uploaded.
Actual: The new version of the workload is not uploaded. Instead, a notification toast displays the following error: "Please ensure you upload a valid .nupkg package file".
Relevant Logs / Error Codes
Additional Context
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with src/packages/manifest/Item1.xml and src/packages/manifest/WorkloadManifest.xml, then inspect the validator path that downloads ItemDefinition.xsd for schema version 1.0.0. Reproduce the backend build and Fabric upload using schema 1.0.0; done means the validator accepts the package and Fabric uploads the .nupkg instead of showing the invalid-package notification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, xml
- Domain
- backend, build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100