Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Breaking Change] ERROR: Schema violation: Array is too short (0) #6168

Closed
konrad-jamrozik opened this issue May 12, 2023 · 3 comments
Closed

[Breaking Change] ERROR: Schema violation: Array is too short (0) #6168

konrad-jamrozik opened this issue May 12, 2023 · 3 comments
Assignees
@konrad-jamrozik
Labels
Breaking Changes Improvements to Breaking Changes tooling bug This issue requires a change to an existing behavior in the product in order to be resolved. Central-EngSys This issue is owned by the Engineering System team. Spec PR Tools Tooling that runs in azure-rest-api-specs repo.

Comments

@konrad-jamrozik
Copy link
Contributor

konrad-jamrozik commented May 12, 2023 •
edited
Loading

GH comment:

GH check:

Exception build log:

Previous title of this issue:

  • [Breaking Change] Cross-Version Runtime Exception: 'Error: Command failed'
@konrad-jamrozik konrad-jamrozik added Central-EngSys This issue is owned by the Engineering System team. Spec PR Tools Tooling that runs in azure-rest-api-specs repo. labels May 12, 2023
@konrad-jamrozik konrad-jamrozik self-assigned this May 12, 2023
@konrad-jamrozik konrad-jamrozik changed the title [Breaking Change] Cross-Version Runtime Exception: [Breaking Change] Cross-Version Runtime Exception: Error: Command failed May 12, 2023
This was referenced May 12, 2023
Open
Merged
@mikekistler mikekistler added Breaking Changes Improvements to Breaking Changes tooling bug This issue requires a change to an existing behavior in the product in order to be resolved. labels Jun 19, 2023
@konrad-jamrozik konrad-jamrozik changed the title [Breaking Change] Cross-Version Runtime Exception: Error: Command failed [Breaking Change] ERROR: Schema violation: Array is too short (0) Sep 26, 2023
@konrad-jamrozik
Copy link
Contributor Author

konrad-jamrozik commented Sep 26, 2023 •
edited
Loading

This appears to me to be error coming up from AutoRest reporting failure. In that sense, it is similar to the investigation I described here:

@konrad-jamrozik
Copy link
Contributor Author

For analysis of runtime error buckets, see:

@konrad-jamrozik
Copy link
Contributor Author

Addressed by:

  • Pull Request 500754: Implement support for pretty-printing runtime errors originating from AutoRest invocation from within OAD (breaking change detector)

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

@konrad-jamrozik konrad-jamrozik

Labels
Breaking Changes Improvements to Breaking Changes tooling bug This issue requires a change to an existing behavior in the product in order to be resolved. Central-EngSys This issue is owned by the Engineering System team. Spec PR Tools Tooling that runs in azure-rest-api-specs repo.
Projects
Azure SDK EngSys 📈
Archived in project
Spec PR Tools
Status: 🎊 Closed
Milestone
No milestone
Development

No branches or pull requests
2 participants
@konrad-jamrozik @mikekistler