You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SDK team is trying to add missing tspconfig.yaml for workloads/Workloads.SAPVirtualInstance.Management in our April release but we found the tsv checked all 4 libs under the same workloads folder. Since other 3 haven't have language configurations yet so we failed with TypeSpec Validation and the log is here.
I think ultimately all spec should have configs but for now spec repos have some missing configurations libs, Could eng team have one-time fix for them?
Otherwise pr authors will be blocked by failures that is un-relevant to current services. Also I am curious why we include all libs under the same RP, any reasons to do that?
The text was updated successfully, but these errors were encountered:
MaryGao
changed the title
[Discussion] Should tsv check all tspconfig.yaml under RP directory?
[TSV][Discussion] Should tsv check all tspconfig.yaml under RP directory?
Apr 24, 2025
Our goal is making all tspconfig are correct at the end.
I feel like after a while, when all/most of tspconfig are correct, it won't be a big issue.
But I'm not sure about what's the opinon of the TSV's owner. so cc @mikeharder
MaryGao
changed the title
[TSV][Discussion] Should tsv check all tspconfig.yaml under RP directory?
[TSV][Discussion] Should tsv check all tspconfig.yaml under the same RP directory?
Apr 24, 2025
MaryGao
changed the title
[TSV][Discussion] Should tsv check all tspconfig.yaml under the same RP directory?
[TSV][Bug] Fix the missing configurations for current repo so it won't block normal customers
Apr 24, 2025
MaryGao
changed the title
[TSV][Bug] Fix the missing configurations for current repo so it won't block normal customers
[TSV][Bug] Fix the missing configuration for current repo so it won't block normal customers
Apr 24, 2025
SDK team is trying to add missing
tspconfig.yaml
forworkloads/Workloads.SAPVirtualInstance.Management
in our April release but we found the tsv checked all 4 libs under the sameworkloads
folder. Since other 3 haven't have language configurations yet so we failed with TypeSpec Validation and the log is here.I think ultimately all spec should have configs but for now spec repos have some missing configurations libs, Could eng team have one-time fix for them?
Otherwise pr authors will be blocked by failures that is un-relevant to current services. Also I am curious why we include all libs under the same RP, any reasons to do that?
The text was updated successfully, but these errors were encountered: