flatpak-vscode icon indicating copy to clipboard operation
flatpak-vscode copied to clipboard

No Flatpak manifest found in this workspace

Open mijorus opened this issue 1 year ago • 6 comments

2023-12-29 20:02:10.883 [error] Error: No Flatpak manifest found in this workspace.
	at ManifestManager.<anonymous> (/home/lorenzo/.vscode/extensions/bilelmoussaoui.flatpak-vscode-0.0.36/out/manifestManager.js:214:23)
	at Generator.next (<anonymous>)
	at fulfilled (/home/lorenzo/.vscode/extensions/bilelmoussaoui.flatpak-vscode-0.0.36/out/manifestManager.js:5:58) flatpak-vscode.build-and-run {"value":"bilelmoussaoui.flatpak-vscode","_lower":"bilelmoussaoui.flatpak-vscode"}

From the same folder, GNOME Builder runs just file

mijorus avatar Dec 29 '23 19:12 mijorus

I dug a little deeper on this. Apparently, the issue seems to be the fact that, for some reason, Code is not activating the extension:

bilelmoussaoui.flatpak-vscode, startup: false, activationEvent: 'workspaceContains:**/*.{json,yaml,yml}'

mijorus avatar Dec 30 '23 16:12 mijorus

The manifest may also be a good start. Is it possible to show it here, including the file name?

SeaDve avatar Dec 31 '23 00:12 SeaDve

Any updates on this one?

bilelmoussaoui avatar Jan 21 '24 19:01 bilelmoussaoui

Any updates on this one?

Not really, it still happens but I don't know why

mijorus avatar Jan 23 '24 07:01 mijorus

Yes but we would need a way to reproduce it like sharing the manifest with us or the project itself if it is open source.

bilelmoussaoui avatar Jan 23 '24 07:01 bilelmoussaoui

FYI I am experiencing this on a clone of https://github.com/sonnyp/Workbench But I can't reproduce with a new fresh clone

sonnyp avatar Mar 16 '24 07:03 sonnyp

I'm having this issue persistently too. I don't know what exactly I changed. but Flatpak VSCode will now consistently ignore my build manifest until I move it to a separate directory and then move it back while VSCode is running.

This is extremely challenging because it means that Flatpak VSCode will now then recompile everything.

This could potentially be fixed by adding a command to manually re-lookup manifests in the project.

vixalien avatar Jul 14 '24 14:07 vixalien

I realized that simply by renaming the file is enough to trigger a rescan

mijorus avatar Jul 15 '24 08:07 mijorus

Yeah but that triggers a rebuild of all the modules

Le lun. 15 juil. 2024 à 10:14, Lorenzo Paderi @.***> a écrit :

I realized that simply by renaming the file is enough to trigger a rescan

— Reply to this email directly, view it on GitHub https://github.com/bilelmoussaoui/flatpak-vscode/issues/229#issuecomment-2227932090, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJB5FCIHTRPPCPDVWR2BLSTZMOAHRAVCNFSM6AAAAABBG5OTQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRXHEZTEMBZGA . You are receiving this because you commented.Message ID: @.***>

vixalien avatar Jul 15 '24 16:07 vixalien

I think https://github.com/bilelmoussaoui/flatpak-vscode/pull/239 should fix the issue for you.

bilelmoussaoui avatar Aug 18 '24 18:08 bilelmoussaoui