NotTheDr01ds's questions

While the OpenAI detector has been useful in identifying content that is created by ChatGPT and other OpenAI-based models, as usage increases (especially by users here on Stack Exchange sites), it's been down more and more frequently.

After installing it locally per the project README, I receive the following error when attempting to run it from the repo directory using python -m detector.server ../gpt-2-models/detector-base.pt:

Traceback (most recent call last):
  File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/home/ntd/src/gpt-2-output-dataset/detector/server.py", line 120, in <module>
    fire.Fire(main)
  File "/home/ntd/src/venv/openai-detector/lib/python3.10/site-packages/fire/core.py", line 141, in Fire
    component_trace = _Fire(component, args, parsed_flag_args, context, name)
  File "/home/ntd/src/venv/openai-detector/lib/python3.10/site-packages/fire/core.py", line 475, in _Fire
    component, remaining_args = _CallAndUpdateTrace(
  File "/home/ntd/src/venv/openai-detector/lib/python3.10/site-packages/fire/core.py", line 691, in _CallAndUpdateTrace
    component = fn(*varargs, **kwargs)
  File "/home/ntd/src/gpt-2-output-dataset/detector/server.py", line 89, in main
    model.load_state_dict(data['model_state_dict'])
  File "/home/ntd/src/venv/openai-detector/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1671, in load_state_dict
    raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for RobertaForSequenceClassification:
        Missing key(s) in state_dict: "roberta.embeddings.position_ids".
        Unexpected key(s) in state_dict: "roberta.pooler.dense.weight", "roberta.pooler.dense.bias".

I attempted to change transformers==2.9.1 per comments in this issue, but then pip install -r requirements.txt fails as well.

After performing a sudo systemctl poweroff in Ubuntu in WSL and restarting, I'm seeing:

<3>WSL (814) ERROR: UtilTranslatePathList:2671: Failed to translate C:\Program Files\PowerShell\7
<3>WSL (814) ERROR: UtilTranslatePathList:2671: Failed to translate C:\Windows\System32\OpenSSH\
<3>WSL (814) ERROR: UtilTranslatePathList:2671: Failed to translate C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common
<3>WSL (814) ERROR: UtilTranslatePathList:2671: Failed to translate C:\Program Files\dotnet\
...

Ubuntu starts, but no Windows drives are mounted into WSL. In addition, Ubuntu exits a short while later. After restarting, everything seems fine.

What's going on, and how can I resolve this?

After enabling Systemd per this answer in Ubuntu 22.04, sudo systemctl status shows State: degraded.

Additionally:

$ sudo systemctl --failed

  UNIT                     LOAD   ACTIVE SUB    DESCRIPTION
● systemd-sysusers.service loaded failed failed Create System Users

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.

How can I transition from degraded to running?

Ubuntu 22.04 LTS (Jammy) for WSL has a new installer (called the "Out of Box Experience" by Canonical) that provides a graphical UI to walk users through the installation. However, it is substantially slower than the older text-based install that other WSL distributions (including 20.04) use. For comparison:

• 22.04 Jammy: ~ 1 minute 30 seconds for all screens, even just accepting the defaults (other than username/password)
• 20.04 Focal: ~ 20 seconds (9 seconds + however long it takes to type your username and password twice)

This probably isn't an issue for most people, but I like to "spin up" a 22.04 (or other distribution) quickly, try something out, then throw it away with wsl --unregister Ubuntu-22.04.

Jammy's installer goes through multiple steps, only some of which seem "useful" compared to the previous installer:

• "Unpacking the distro" -- 11-12 seconds on my relatively fast NVMe drive.

• "Almost done. The installer will require your attention soon." -- ~14 seconds

• "We are almost done - Just a few steps to be completed in the main installer window. Can we quit this one and go there?"

• A language selection screen

• The username/password screen

• "Advanced Setup" where mount options can be set

• "Applying Changes" -- The biggest issue, since it takes more than 30 seconds, and says it may take longer if the network connection is slow.

  It's really not clear what's going on in this step since it shouldn't even need an internet connection to apply changes to a local WSL installation of Ubuntu.

By comparison, Focal needs only about 10 seconds to complete the first step (unpacking), at which point it is ready to accept the username/password, and then it's done.

Is there any way to speed up the Jammy OOBE/Installer, perhaps by skipping certain steps?

Attempting to install USB/IP on Ubuntu 22.04 per the Microsoft docs:

On Ubuntu, run this command:

sudo apt install linux-tools-5.4.0-77-generic hwdata
sudo update-alternatives --install /usr/local/bin/usbip usbip /usr/lib/linux-tools/5.4.0-77-generic/usbip 20

But running that results in:

E: Unable to locate package linux-tools-5.4.0-77-generic
E: Couldn't find any package by glob 'linux-tools-5.4.0-77-generic'

How do I install USB/IP on Ubuntu 22.04 on WSL?