Ce Gao

I ran the chrome extension successfully, but we cannot get the correct os/editor/machine because of the user-agent. The user-agent from the browser looks like `Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,...

I updated these parts in the chrome extension: - https://github.com/wakatime/chrome-wakatime/blob/master/manifest.json#L34 Added my own hostname here. - https://github.com/wakatime/chrome-wakatime/blob/master/assets/js/config.js#L21 Change the config to my own endpoints

Thanks! We can maintain a chrome-wakatime fork to support wakapi.dev. But it is hard to keep one extension for all self-hosted instances. We need to work around ajax/chrome extension CORS...

I can help with it. I am a backend guy but used to hack on chrome wakatime plugin. Will see what I can do here.

Yeah but do not have much bandwidth for it. :worried:

Can you please show the image tag of the gateway and kernel?

OK I will verify it today.

@ycsong1212 Did you follow the guide here? https://github.com/skai-x/elastic-jupyter-operator/tree/master/docs#remote-kernels Remote kernel or Remote kernels with custom configuration

Or this https://github.com/skai-x/elastic-jupyter-operator/blob/master/docs/quick-start.md

I did not reproduce it before. I will take a look ASAP but not sure if I can reproduce this time.