Open davidovich opened 1 year ago
Hi :) Could you please provide a small sample project where this can be reproduced?
Also: Does this still happen with 0.27.1 (or newer)?
I can test next week, but the failure happens on a tree of mixed classical spec.json based envs and one dynamic env.
Le jeu. 20 juin 2024 à 03:33, Horst Gutmann @.***> a écrit :
Also: Does this still happen with 0.27.1 (or newer)?
— Reply to this email directly, view it on GitHub https://github.com/grafana/tanka/issues/893#issuecomment-2180010559, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAK7U4UMTK6Y4UABBZ5FXZDZIKAT5AVCNFSM6AAAAAA23R7PRKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBQGAYTANJVHE . You are receiving this because you authored the thread.Message ID: @.***>
When trying to list imports of a tanka project, tanka fails with this message:
Failure seems to origin from imports.go.
A very shallow investigation points to tanka using
<internal>
as a kind of sentinel, but that special file seems to be included in the files treated by the imports machinery.