I have created a JupyterLab extension
that converts a SAS file (*.sas) to a Jupyter notebook (*.ipynb).
The extension works fine on my development systems (ubuntu and osx) but when I try and use it inside of binder I get 404 errors.
Here is the browser console when working:
Here is the browser console inside of binder (not working):
Obviously there is something different between the two environments but I can't figure out what it is.
The extensions appear to be installed correctly in binder, so I'm not sure what to do next.
jadean#6541034d7640:~$ jupyter server extension list
Config dir: /home/jadean/.jupyter
/srv/conda/envs/notebook/lib/python3.9/site-packages/jupyter_server/transutils.py:13: FutureWarning: The alias `_()` will be deprecated. Use `_i18n()` instead.
warnings.warn(warn_msg, FutureWarning)
Config dir: /srv/conda/envs/notebook/etc/jupyter
jupyterlab enabled
- Validating jupyterlab...
jupyterlab 3.0.12 OK
nbclassic enabled
- Validating nbclassic...
nbclassic OK
sas2nb enabled
- Validating sas2nb...
sas2nb 0.1.0 OK
Config dir: /usr/local/etc/jupyter
jadean#6541034d7640:~$ jupyter labextension list
/srv/conda/envs/notebook/lib/python3.9/site-packages/jupyter_server/transutils.py:13: FutureWarning: The alias `_()` will be deprecated. Use `_i18n()` instead.
warnings.warn(warn_msg, FutureWarning)
JupyterLab v3.0.12
/srv/conda/envs/notebook/share/jupyter/labextensions
jlab-create-sas-file v0.1.0 enabled OK (python, jlab_create_sas_file)
sas2nb v0.1.0 enabled OK
#jupyter-widgets/jupyterlab-manager v3.0.0 enabled OK (python, jupyterlab_widgets)
Related
I know this has been asked and answered many times: Reenable urllib3 warnings,
How to suppress warnings about lack of cert verification in a requests HTTPS call?
Even I had it working as well previously with below solution:
import requests
requests.packages.urllib3.disable_warnings()
But since I had enabled extension for pyLint in VSCode it stopped working.(I know pyLint may not have impacted it but I have started facing this only after enabling pyLint extension)
So pyLint started complaining about "packages" is not there in "requests"
I have tried another solution being discussed in above posts, which is:
import urllib3
urllib3.disable_warnings()
Which doesn't work as well.
Someone also suggested to use
requests.urllib3.disable_warnings()
instead of
requests.packages.urllib3.disable_warnings()
but in my case it seems "requests" doesn't have "urllib3" inside it.
So is there any other way to ignore these warnings.
I am having below setup:
Python - 3.10.6
requests - 2.28.1
urllib3 - 1.26.12
pyLint extension for VSCode - v2022.4.0
I am facing similar issue like this mentioned in the post:
Triying to run VLC for unity plugin demo
Build platform is WIN 10 x64 (build 2004).
I am using LibVLC from the nightly build: https://artifacts.videolan.org/vlc/nightly-win64-llvm/20200914-0434/
LibVLCSharp gets built successfully (https://code.videolan.org/videolan/LibVLCSharp/-/tree/master/).
I was trying to build "VLCUnityPlugin.dll" but failing (have installed https://github.com/mstorsjo/llvm-mingw/tree/20200325 (LLVM MinGW)), using MSYS64 to run ./build.sh and it was coming up with this error:
MSYS error while building VLCUnity plugin dll
I thought maybe since "VLCUnityPlugin.dll" is NOT present, Unity x64 (v 2019.4.8f1) keeps on complaining with the following errors:
UNITY errors
But after, I hacked "common" make file as shown below:
make file changes to build VLCUnityPlugin.dll
I successfully built VLCUnityPlugin.dll and my plugin file structure looks like this now:
Plugin directory structure
Still, I do see UNITY Errors:
"Assets\VLCUnity\Demos\Scripts\MinimalPlayback.cs(99,39): error CS1061: 'MediaPlayer' does not contain a definition for 'GetTexture' and no accessible extension method 'GetTexture' accepting a first argument of type 'MediaPlayer' could be found (are you missing a using directive or an assembly reference?)"
The free trial version is available for download here https://videolabs.io/vlc-unity/vlc-unity-windows-trial.unitypackage.
That being said, if you want to build it yourself, you should follow what the CI does https://code.videolan.org/videolan/vlc-unity/-/blob/master/.gitlab-ci.yml
The libvlcsharp build is a special one, you need to define UNITY when you build it. It has the added GetTexture method.
For VLCPlugin.dll, you should crosscompile from Linux, where you install llvm-mingw and run it from bash (for example). MSYS not needed.
Intellisense isn't working in VSCode. Examples like:
F2 (rename symbol): shows "initializing JS/TS language feature", but stucks forever issue-image
dropdown suggestions not coming up directly, ctrl+enter shows loading, but not getting completed
doesn't show error even in case of genuine error, etc.
Already tried below things:
restarted VScode multiple times
Ctrl+Shift+P > typescript: Restart TS server --> nothing happens
Installed & uninstalled extension (TSLint, JsHint, ESLint)
"Help" -> "check for updates" --> says "there are currently no updates available"
re-ran all command i.e. npm run setup-npm-auth, npm install etc.
tried force build
{verified my solution is getting built properly}
Current versions:
npm: 6.9.0
node: 10.16.3
VScode version
I just had the same issue. Fortunately I was able to fix the problem following this steps from vscode github's comments. You can enable ts language server's log and debug your issue. To enable ts server logging:
Set "typescript.tsserver.trace": "verbose" (Restart vscode)
Reproduce the problem
Open the output panel and view the TypeScript section
In my case my code was referencing to the directory outside of the workspace. So VSCode could never finish the task. I am not sure it's bug or limitation, nevertheless make sure all of your working code is included in your VSCode workspace (or added to working folders). Otherwise it'll stuck like this even code you're referring to exists side by side but not included in your workspace (or visible) in your VSCode.
i use vscode on Mac for nodejs applications.
I installed the **Mocha Side Bar** module, for help me test my unit tests.
The problem is that vscode doesnt see the 'Nodejs' installation, and each time i try to execute the 'mocha test run', i am getting these errors:
The root of my nodejs installation is on that path: /Users/theodoros.itzaris/.nvm/versions/node/v6.11.5/bin/node
It seems a simple configuration issue, but i m new to both mac & vscode.
And i did not manage to find any tutorial on that.
You can specify an absolute path to your nodejs installation by setting the program attribute in your launch.json:
"program": "/Users/theodoros.itzaris/.nvm/versions/node/v6.11.5/bin/node"
All available launch configuration attributes can be found in this docs.
Update
Here is explained how the extension works and furthermore stated
It will search for the installed Node.js as indicated by environmental variable PATH
Therefore ensure that you have added node.js to your system's PATH variable.
How can I install Gunicorn using Cygwin?
I cant seem to find the Gunicorn Package on Cygwin...Unless I'm understanding the issue on github wrong, I think it does support Gunicorn.
Also I found this in the changelog:
0.17.2 / 2013-01-07
optimize readline
make imports errors more visiblle when loading an app or a logging class
fix tornado worker: don’t pass ssl options if there are none
fix PEP3333: accept only bytetrings in the response body
fix support on CYGWIN platforms