Debugging a real-life problem is not easy (e.g. #268), and we have some ways to ease it such as --record flag to generate a video to see what's going on (though the feature is broken with a snap confinement #253).
However, there is no way to see the actual browser in action to debug something further unless we set up a dev environment outside of a snap such as: https://github.com/canonical/ght/blob/main/HACKING.md#local-development
It would be nice if the ght snap offers those debugging method out of the box, for example by having --headless=false option. For the record, passing NODE_ENV=development doesn't work as a workaround.
$ NODE_ENV=development ght replicate -i
✖ Error replicating job post: Error: Failed to launch the browser process!
error: error running snapctl: snap "ght" has no plug or slot named "password-manager-service"
[589471:589471:0520/223550.629816:FATAL:credentials.cc(131)] Check failed: . : Permission denied (13)
[0520/223550.662432:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)
TROUBLESHOOTING: https://pptr.dev/troubleshooting
Debugging a real-life problem is not easy (e.g. #268), and we have some ways to ease it such as
--recordflag to generate a video to see what's going on (though the feature is broken with a snap confinement #253).However, there is no way to see the actual browser in action to debug something further unless we set up a dev environment outside of a snap such as: https://github.com/canonical/ght/blob/main/HACKING.md#local-development
It would be nice if the ght snap offers those debugging method out of the box, for example by having
--headless=falseoption. For the record, passingNODE_ENV=developmentdoesn't work as a workaround.