parse-community / parse-community/parse-server

Dashboard data browser not loading _User if a user with Twitter authdata exists

Open
#9,885 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:bug
Dominant language
JavaScript
Stars
21.4k
Forks
4.8k
Avg merge
7h 45m
Merged PRs (30d)
11

Description

Issue Description

_User doesnt show data if a row exists with twitter auth data.
I have a very old row with twitter auth data. Data browser not loading with data after i upgraded from v7.3.0 t0 8.2.5.
Resolves if i delete the row.
No issues in queries from client code.

Server

  • Parse Server version: 8.2.5
  • Operating system: macOS/Linux Docker
  • Local and or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Local and Digital ocean

Database

  • System (MongoDB or Postgres): MongoDB
  • Database version: 8.0.15
  • Local (Community edition) and Atlas

Client
Not applicable for the issue

Logs

Common on local and Digital Ocean,MongoDB Atlas

at TwitterAuthAdapter.validateOptions (/parse/node_modules/parse-server/lib/Adapters/Auth/twitter.js:81:13)
at loadAuthAdapter (/parse/node_modules/parse-server/lib/Adapters/Auth/index.js:162:13)
at getValidatorForProvider (/parse/node_modules/parse-server/lib/Adapters/Auth/index.js:182:25)
at /parse/node_modules/parse-server/lib/Adapters/Auth/index.js:202:27
at Array.map (<anonymous>)
at Object.runAfterFind (/parse/node_modules/parse-server/lib/Adapters/Auth/index.js:201:32)
at /parse/node_modules/parse-server/lib/RestQuery.js:788:85
at Array.map (<anonymous>)
at _UnsafeRestQuery.handleAuthAdapters (/parse/node_modules/parse-server/lib/RestQuery.js:788:43)
at /parse/node_modules/parse-server/lib/RestQuery.js:259:17

Only on Digital ocean (Observed only once)
error: bad regex: [object Object] {"code":107,"stack":"Error: bad regex: [object Object]\n at transformConstraint (/parse/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoTransform.js:787:17)\n at transformQueryKeyValue (/parse/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoTransform.js:351:33)\n at transformWhere (/parse/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoTransform.js:399:17)\n at MongoStorageAdapter.find (/parse/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoStorageAdapter.js:477:59)\n at /parse/node_modules/parse-server/lib/Controllers/DatabaseController.js:1050:33\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async _UnsafeRestQuery.runFind (/parse/node_modules/parse-server/lib/RestQuery.js:647:19)"}

package.json

{
	"name": "lendable",
	"version": "2.0.0",
	"main": "index.js",
	"repository": {
		"type": "git",
		"url": "https://github.com/ashish-naik/abc.git"
	},
	"license": "MIT",
	"dependencies": {
		"cors": "*",
		"cryptoutils": "*",
		"dotenv": "16.3.0",
		"form-data": "^4.0.0",
		"google-auth-library": "9.6.2",
		"jsonwebtoken": "*",
		"node-schedule": "latest",
		"parse-dashboard": "7.5.0",
		"parse-server": "8.2.5",
		"parse-server-api-mail-adapter": "4.1.0",
		"path": "*",
		"socket.io-client": "4.8.1",
		"underscore": "*",
		"zeptomail": "6.0.0"
	},
	"scripts": {
		"start": "node index.js"
	},
	"engines": {
		"node": "22.21.0",
		"npm": "11.6.2"
	}
}

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

Reproduce the dashboard data-browser failure with a legacy _User row containing Twitter auth data, using the versions and MongoDB environments listed. Start with Adapters/Auth/twitter.js, Adapters/Auth/index.js, and RestQuery.js; also inspect MongoTransform.js for the separate regex error. Done means the _User data loads without the reported errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, mongodb, nodejs
Domain
authentication, backend, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.