Execution TIme is not displayed

I am completely new in python.
I have installed the extention via pip as well as conda. But the execution time is not displayed.

There is a tab "Execute Time" under Advance Settings and it is also activated, but I don't get any information about the execution time if i run a cell.

I am using juypterLab version 3.5.3.

I can't find the place where to enter {"recordTiming": true}.
For me it looks like this under setting:

Can you search for record?

Thanks for your reply.
here how it looks

I got the same problem. My jupyter lab version is 3.6.4. I have installed this extension succesfully. And for my installation., the parameter recordTiming default is false. So I modified to true and saved the configuration as well. No matter I refreshed the jupyter lab in browser or restarted the jupyter lab, the cell executing time was still not showing below the cell.

Same issue. Seems like a bug in v3.0.0. Work around is to revert back to v2.3.1.

Thanks ianalis, it works after downgraded jupyterlab_execute_time to version 2.3.1.

Same here, version 2.3.1 works while 3.0.0 not

Per the changelogs, 3.0.0 only supports JupyterLab@4.x - https://github.com/deshaw/jupyterlab-execute-time/blob/master/CHANGELOG.md#300-2023-05-19

i revert back to v2.3.1, but it still can't display time in cell.

i already setting user preference {"recordTiming":true}, but it still can't display execute time in cell. how can i solve this problem

Same issue here, cannot display the cell execution time after setting the recordTiming field to true.
Using jupyterlab-desktop with jupyterlab version 4.0.2 and installed the extension with mamba. How do I resolve this

i revert back to v2.3.1, but it still can't display time in cell.

@gasdaf you have a pretty outdated JupyterLab installation. Since other users report 2.3.1 works with Lab 3.x, maybe they are using a newer version of Lab 3.x, e.g. 3.6.x?

Pinning version of JupyterLab in:

jupyterlab-execute-time/setup.py

Line 44 in d9be071

install_requires=["jupyter_server>=2.0.1,<3"],

and yanking 3.0.0 from PyPI is the simplest solution.

Another approach would be to release a 3.0.1 as cross-compatible with both Lab 3.x and 4.0. This should be feasible but a bit more involved on the maintenance and testing end.

Mine also worked when I downgraded to 2.3.1