Genie Discord forum
I figure I should start with the video this time...
The first video shows me re-installing Genie Builder (again), with the previously deleted apps immediately reappearing.
The second video shows me trying to make another app, recreating the old app directories so that I can open the VSCode terminal, and generally trying to right click on things unsuccessfully and trying to stop the server unsuccessfully.
GenieFramework v1.9.0 julia> versioninfo() Julia Version 1.8.5 Commit 17cfb8e65ea (2023-01-08 06:45 UTC) Platform Info: OS: Linux (x86_64-linux-gnu) CPU: 16 × AMD Ryzen 9 5900HS with Radeon Graphics WORD_SIZE: 64 LIBM: libopenlibm LLVM: libLLVM-13.0.1 (ORCJIT, znver3) Threads: 1 on 16 virtual cores Environment: JULIA_EDITOR = code JULIA_NUM_THREADS =
for some reason I can't open the videos 😦 Still, apologies for the issues you're having. Could you try starting with a new environment by deleting the
~/.julia/geniebuilderfolder and re-launching Genie Builder? That should fix these problems
I tried that but get the error: "The terminal process failed to launch: Starting directory (cwd) "/home/graham/.julia/geniebuilder/apps/AnotherApp" does not exist."
Though that error is sort of tangential to the main issue. That error happens because geniebuilder leaves the terminal in the app directory, and when you restart vscode it tries to open the terminal in that now-nonexistent directory.
Ignoring that (it's easy to get around), there's just no error message, basically the state at the end of this most recent video
(I think this video works? Maybe uploading two videos at once made discord upset)
Here's maybe a better illustration of a more fundamental problem (having "fixed" the previous error by creating the empty directory "~/.julia/geniebuilder/apps/AnotherApp"; equivalently fixed by cd'ing to an existing directory)
So not only does VSCode think that the geniebuilder apps exist when they've been deleted, but it also insists on keeping them open as nonexistent folders in the current workspace
I'm happy to try debugging this myself, but I can't get it to produce anything including debug messages, so I have no idea where to start
(by debug messages, i just mean any vscode logging output)
I dont know if this may help but when i delete an app i have to delete it from the folder /geniebuilder/apps but also delete the folders in the genie builder sidebar in visual studio and then they are completely deleted (i also noticed visual studio keeps them )
That fits with what I'm seeing, but I also have the bug that I can't delete the apps from the sidebar :/
what version of Genie Builder are you on? The regular or the insider?
Thinks like these happen sometimes with GB and unfortunately the fastest way to solve/debug is to reset the environment by deleting .julia/geniebuilder and then add the app's code one by one. Sometimes the issue is with a bug in the code that prevents GB from executing the app, or perhaps a package that's being used but is not installed
I'm using the regular
The problem is that I already have deleted .julia/geniebuilder, including all the apps. None of the apps ever had any meaningful code. They were just the default. But when I try to run geniebuilder, it doesn't recreate the .julia folder and so it doesn't do anything. When I reinstall geniebuilder, it also doesn't recreate .julia/geniebuilder.
as I told earlier "recreate .julia/geniebuilder." this has to happen. It's how to plugin works. It installs plugins goodies in that directory when you install the plugin
I'm confused what you're suggesting I do. Recreating .julia/geniebuilder is not happening, and nothing short of reinstalling VSCode makes it happen. Not restarting VSCode. Not reinstalling Genie Builder. Since reinstalling VSCode wipes all my command history, I don't consider that a viable solution. How do I recreate .julia/geniebuilder once I've deleted it?
After writing that, I noticed the obvious "reboot the computer" wasn't on the list of things that doesn't fix it. Rebooting the computer causes Genie Builder to recreate .julia/geniebuilder the next time the server starts 🤦♂️
so consider this fixed