parse-community / parse-community/parse-dashboard

Issue with logs pages - t.match is not a function

Open
#1,459 9 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:bug
Dominant language
JavaScript
Stars
3.8k
Forks
1.4k
PR merge metrics
No merged PRs in 30d

Description

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!

  • You're running version >=1.0.23 of Parse Dashboard.

  • You're running version >=2.3.2 of Parse Server.

  • You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

Running Locally

parse-dashboard: 2.0.5
parse-server: 3.10.0
express: 4.17.1
Steps to reproduce

Similar to #1112
Open up dashboard and navigate to logs page
Sometimes works but mostly of the time it crash

Logs/Trace
Uncaught (in promise) TypeError: t.match is not a function
    at Yf (dashboard.bundle.js:95)
    at oa (dashboard.bundle.js:45)
    at eu (dashboard.bundle.js:45)
    at xu (dashboard.bundle.js:45)
    at yu (dashboard.bundle.js:45)
    at su (dashboard.bundle.js:45)
    at dashboard.bundle.js:45
    at t.unstable_runWithPriority (dashboard.bundle.js:53)
    at qi (dashboard.bundle.js:45)
    at Gi (dashboard.bundle.js:45)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the crash on the dashboard logs page using the reported Parse Dashboard and Parse Server versions, then inspect the stack trace location at dashboard.bundle.js:95 and trace it back to the source. Done means the logs page loads reliably without the t.match TypeError; no source file or regression test is identified in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, observability
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.