Lost connection after exiting suspend mode.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- arch-linux, firebase, node.js
- Domain
- database, operating-systems
Research direction
Reproduce the suspend/resume case described for Arch Linux, pm2, Node.js 22.11.0, Firebase SDK 13.22.0, and the firebase-admin realtime database call at firebase.database().ref('data').once(...). Start by tracing the realtime database connection lifecycle across suspend and resume; done means the request completes or reports an error after resume without restarting the application.
Written by the indexing model from the issue text.
Description
- Operating System version: Arch Linux
- Firebase SDK version: 13.22.0
- Firebase Product: database
- Node.js version: 22.11.0
- NPM version: 10.9.0
On my laptop, using pm2, the NodeJS application is running and constantly working, which periodically successfully accesses the real-time database using the firebase-admin module. However, when I put the computer into suspend mode and then turn it on again, and activate the function of accessing the database, it freezes. The console shows that the application is running, all functions are executed, except for the one that makes a request to the database. Without the content inside, it looks like this:
firebase.database().ref('data').once('value', (s) => {
console.log('output 1');
}, (error) => {
console.log('output 2');
});
Not 1 and not even 2 output to the console do not work.
At the same time, all requests to other data sources made using fetch work. After restarting the application, the database is accessed as expected.
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 419
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 16
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.
More from firebase/firebase-admin-node
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
firebase/firebase-admin-node#3234 ·
-
firebase/firebase-admin-node#3221 · 3 comments · 1 assignee ·
-
api: messaging
Difficulty 3/5 1-2 days Newbie friendliness 70/100
firebase/firebase-admin-node#3215 ·
-
api: messaging
Difficulty 5/5 Over a week Newbie friendliness 28/100
firebase/firebase-admin-node#3214 ·
-
api: firestore type: feature request
firebase/firebase-admin-node#3183 · 1 comment · 1 assignee ·
All issues in firebase/firebase-admin-node
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
vercel-labs/just-bash#464 ·
-
looksLikeSlug() is ASCII-only, so non-Latin entity slugs (e.g. Korean) skip exact match and collapse Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
TanStack/tanstack.com#1293 ·