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
I messed up and added a trailing comma in my jails.json file, and it took a while to figure out why jails won't respect the configuration, because I haven't seen anything in the logs about config not being valid. Seems like the server just silently applies the defaults if something goes wrong. Maybe a log entry about failing to parse the config file would be useful for situations like this.
The text was updated successfully, but these errors were encountered:
I also had a fair bit of confusion trying to configure it correctly. It seems like VS code shows the default compilerPath under Workspace settings, even when you click reset and it's supposed to be inheriting the path from User settings. Idk if this is a VS Code bug or what.. but eventually it started working. I think you also have to restart the extension every time you update the config for it to take effect, that seemed to help me.
I messed up and added a trailing comma in my jails.json file, and it took a while to figure out why jails won't respect the configuration, because I haven't seen anything in the logs about config not being valid. Seems like the server just silently applies the defaults if something goes wrong. Maybe a log entry about failing to parse the config file would be useful for situations like this.
The text was updated successfully, but these errors were encountered: