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 Aug 9, 2021. It is now read-only.
Login and open the inspector. The error below is shown for every space. This error shows, but it does not prevent me accessing hub as normal. Inside hub everything works as expected, except one other error which may, or may not related . - in the activity section, some activities are showing with more recent time occurrences than when they happened (ie changes made in the Erasure hackathon show up as an hour ago, when they happend 2wks + ago)
See error
at l (formatters.js:411)
at index.js:152
at Array.map (<anonymous>)
at l.formatInput (index.js:150)
at l.toPayload (index.js:187)
at S.r [as getCode] (index.js:528)
at getActivity.js:246
at c (runtime.js:45)
at Generator._invoke (runtime.js:264)
at Generator.E.forEach.e.<computed> [as next] (runtime.js:98)
Expected behavior
These errors would not be shown in the developer console. For the second erro
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: [e.g. iOS] macOS Catalina 10.15.2
Browser [e.g. chrome, safari] Chrome
Version [e.g. 22] Version 79.0.3945.88 (Official Build) (64-bit)
Additional context @oznekenzo also reports seeing the same issue, does not look like its caused by Hub but by the backend.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
Capitalization Checksun error.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
These errors would not be shown in the developer console. For the second erro
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
@oznekenzo also reports seeing the same issue, does not look like its caused by Hub but by the backend.
The text was updated successfully, but these errors were encountered: