You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2022. It is now read-only.
I am trying to create a notebook channel in a private group, and after successfully creating two notebooks, on attempt of creating a third (titled, Notices), i get sent the the error page with the following stack trace warning and a prompt to file this as an issue.
The notebook appears to have been created, but if trying to join from either the host ship, or a member-admin, it sends me to this same error message. Might be a moot point with groups 2 coming up, but figured I would log the bug for the important reason of:
The system gave me the stack trace and made it super easy to click a button and end up at this issue creation screen with the context that appears like it would be useful to a developer tasked with looking into this issue.
The text was updated successfully, but these errors were encountered:
It seems to me that the issue is actually not with creating the notebook, but with accessing the notebook. Like OP said, the Notebook was created, but if I try to click on it to open it, I get the same stacktrace every time:
However, after I clicked Refresh in the browser, it appears I am able to access this notebook.
First instinct is this is some sort of app state mismatch where the backend is aware of this notebook but the front-end state isn't - after refresh, state is synchronized. Very typical React nonsense.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am trying to create a notebook channel in a private group, and after successfully creating two notebooks, on attempt of creating a third (titled,
Notices
), i get sent the the error page with the following stack trace warning and a prompt to file this as an issue."c.includes is not a function"
The notebook appears to have been created, but if trying to join from either the host ship, or a member-admin, it sends me to this same error message. Might be a moot point with groups 2 coming up, but figured I would log the bug for the important reason of:
The system gave me the stack trace and made it super easy to click a button and end up at this issue creation screen with the context that appears like it would be useful to a developer tasked with looking into this issue.
The text was updated successfully, but these errors were encountered: