parse-community / parse-community/parse-server
Count Objects not working in some classes
Open
Nobody has claimed this yet.
state:released
state:released-alpha
state:released-beta
type:bug
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.
Issue Description
Dashboard doesn't count object in most of the classes
Steps to reproduce
Since the first installation I always had this issue...
Actual Outcome
Only showing '2' in the _Session class, the other classes show '0'
Expected Outcome
To show the total of objects in each class
Environment
Parse dashboard hosted on AWS Ubuntu EC2
Dashboard
- Parse Dashboard
version: 4.1.1 - Browser:
Safari, Safari Technology Preview Release, Firefox, Chrome - Browser version:
Safari 15.5, Safari Technology Preview Release 146, Firefox 100.0.2, Chrome 102.0.5005.61.
Server
- Parse Server version:
5.2.1 - Operating system:
macOS Monterrey - Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc):
AWS Ubuntu EC2
Database
- System (MongoDB or Postgres):
Postgres - Database version:
14.2 - Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc):
AWS
Logs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the count behavior with Parse Dashboard 4.1.1, Parse Server 5.2.1, and Postgres 14.2 on the reported AWS setup, comparing _Session with the other classes. Trace the object-count request and verify that each class reports its total rather than zero.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript, postgres
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100