question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Firestore requests tab is unordered making it mostly unusable

See original GitHub issue

The requests list at /firestore/requests is unordered. This makes it mostly unusable as it’s very hard to find new requests as they happen. The page should be ordered by timestamp.

firebase-tools: 9.16.6 platform: MacOS arm64 (M1) 11.5.2 browser: Firefox 92.0b6

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
yuchenshicommented, Sep 7, 2021

Thanks for looking into this, @cristianberroeta! There are two separate issues here. First, as you’ve observed, the top-level time field should be used. This should fix the display on the list view discovered by OP @AndrewMorsillo.

There’s still an underlying issue as to why rulesContext.time is in the past for the third request, which we’re looking into right now internally. That part is within the Firestore Emulator, which is not open source.

0reactions
cristianberroetacommented, Sep 7, 2021

no problem @yuchenshi.

I also noticed that if you follow these steps:

  1. press the button “Start listening for document changes”,
  2. refresh the page, without pressing “Stop listening for document changes” before (or you can even close the page, and then reopen it in another browser tab),
  3. press the button “Update document”,

then these are the logged requests: image

I’m not sure if that is the expected behavior, but if you have a website in which you don’t clean the listeners and your page is reloaded multiple times, then you can apparently end up with multiple GET requests being sent after an UPDATE, like this: image

In this case, I did the “start listening - refresh” sequence 8 times, and then pressed the button to update, which generated an UPDATE request, followed by 8 GET requests.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Best practices for Cloud Firestore - Firebase
The following best practices describe how to avoid situations that create contention issues. Updates to a single document. As you design your app,...
Read more >
Why is "Content Downloaded" in the network tab over a ...
1 Answer. Save this answer. Show activity on this post. The Firestore JavaScript SDK uses web channel as its protocol for talking to...
Read more >
How to fix Firestore Error: PERMISSION_DENIED - Medium
A simple solution for handling Firestore error. That's by far the most common and annoying error that you can get when you try...
Read more >
Error: Firestore: The service is currently unavailable ... - GitHub
It's strange because its not reproducible when the app lost the connection. But suddenly it comes online again. In the most case after...
Read more >
Firestore Security Rules - How to Hack a Firebase App
Learn how to hack a Firebase app, then configure solid Firestore Database security rules to ensure data integrity.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found