Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

load_meshes #33

Closed
AnthonyAndroulakis opened this issue Jun 27, 2023 · 1 comment
Closed

load_meshes #33

AnthonyAndroulakis opened this issue Jun 27, 2023 · 1 comment

Comments

@AnthonyAndroulakis
Copy link
Contributor

bug when calling load_meshes() function. Error thrown due to gl property of niivue not being initialized

will investigate further

(issue brought up through mail)

@christian-oreilly
Copy link
Collaborator

@cdrake As discussed at the meeting today, this function just sits forever when called on my MacOS system, on VS Code.

I tried it on a jupyter notebook server, and the server spits out:

[W 11:20:23.939 NotebookApp] IOPub data rate exceeded.
    The notebook server will temporarily stop sending output
    to the client in order to avoid crashing it.
    To change this limit, set the config variable
    `--NotebookApp.iopub_data_rate_limit`.
    
    Current values:
    NotebookApp.iopub_data_rate_limit=1000000.0 (bytes/sec)
    NotebookApp.rate_limit_window=3.0 (secs)

That being said, as far as I can tell, it displayed the meshes fine. Maybe the issue this function has in the CI (#38) is related to this error message? I am not sure why the call to this function sits forever in VS code. I looked a bit at some doc (https://code.visualstudio.com/api/extension-guides/notebook) but it would require me more time to digest that doc! Your input would be most welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants