WLJS LogoWLJS Notebook

Troubleshooting

If something isn't working as intended, please post an issue on GitHub and include information evaluated in your Wolfram Engine (wolframscript), such as:

$Version
$SystemID
WLJS works correctly with Wolfram Engine > 14.1. The older versions are not supported due to some missing I/O features

Also, please, specify how you are running the app (as a normal desktop application or as a Docker image on a server).

App does not start (CODE -1)

It may show on a lanucher screen something like no hup, exit code -1. Then close an app, open a terminal and run

wolframscript -activate

Start WLJS app again.

Make sure that no other processes wolframscript or Wolfram Kernel are running. WLJS uses 2 processes: 1 for UI, frontend and 1 for actual evaluation. This is the maximum allowed by freeware Wolfram Engine license.

In addition, please, visit https://account.wolfram.com/products and verify that one of the Wolfram Engine basic keys has (Available) next to it.

Caching Issues

This is only relevant for Docker images

Sometimes after an update, your browser's cache may still be outdated. Try the following options depending on your browser:

  • Ctrl-F5 or ⌘-R
  • Force Reload (from the top menu of desktop application window)
  • Reload Window (from the top menu of desktop application window)
  • Clear Cache and Reload (from the top menu)

General advice

Take a screenshot and provide the context of what went wrong

Bypass WLJS Renderer and use MMA's

To bypass the standard form of expression used in WLJS Notebook, use MMAView

Plot[x, {x,0,1}] // MMAView

WLJS Notebook does not cover all possible styling options for plots, graphics and diagram types. For that reason we give an option to use the default renderer of Wolfram Engine.

Logs Dump

If you're comfortable sharing logs (and it doesn't violate your privacy), you can enable DEBUG mode at startup:

  1. Restart the app and click DEBUG in the launcher window.
  2. Perform the actions that lead to the error.
  3. Close the app normally.
  4. A window with the collected log file will appear.
  5. Send the log to us via Telegram, email to one of the maintainers, or submit to GitHub Issues.

Ask community

Use a built-in feature of the command palette bar to submit a focused cell group to our Github Discussion even if it is just a question:

General Discussions

We are encouraging you to share anyhting on our Github Discussion page.

Hotline Support

Join out community:

Submit issues through GitHub

On this page