Limit() causing new clients to get blank data? about angularfire

[katowulf]

Submitted via internal ticketing system. I will attempt to get a repro.

[lifeisfoo]

Same to me (from today).

[Edit]
It's my report :)

2013/6/28 katowulf [email protected]

Hi,
I'm reporting unexpected behavior from my application using [redacted]

My "broadcast" messages are pushed correctly, and received by everybody
listening on them. But when a new connected client try to get latest
inserted messages, they aren't received.

I'm using the same code since the end of april and worked

I've debugged my application and found the cause of the problem (I'm using

angularFire):

var fbMessages = fb.child('broadcast');
$scope.messages = angularFireCollection(fbMessages.limit(50));

If I remove the call to the limit function all works fine...

I hope this can help you.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/44
.

[lifeisfoo]

Here is a simplified version of my controller. Original code contains other .child() call to the main fb reference and other angularFireCollection variables.
It worked until today. From this morning it stopped working. As I said before, messages pushed after the application startup are received correctly.

        var fb = new Firebase(Meta.url);
        fb.auth(Meta.token, function(error, result) {
          if(error) {
            console.log("Login Failed!", error);
          } else {
            console.log('Auth ok.');
          }
        });
        var fbMessages = fb.child('broadcast');

        $scope.messages = angularFireCollection(fbMessages.limit(50));

        $scope.addMessage = function() {
              $scope.messages.add({text:$scope.messageText, sender:Meta.username, time: new Date().getTime()});
        };

[lifeisfoo]

Seems to be a data related issue: I have tested against another firebase url and all works correctly.
The firebase that cause this problem is grow a lot in the latest 24 hours.

After the first collection constructor I have another collection:

var fbMessages = fb.child('users');
$scope.users = angularFireCollection(fbUsers);

"users" is the resource that is grow a lot: hundreds of entry with child. I tried to delete all broadcast messages but nothing has changes. Obviously I can't delete users resource.

[katowulf]

@lifeisfoo Do you have any security rules set up on this data? I think that the problem here may be a timing issue in the way you are doing your auth call.

This morning we released some optimizations to the limit() function. So it's much faster now, which is probably why this timing issue never happened before.

Can you try changing your controller code like this, and seeing if it helps?

         var fb = new Firebase(Meta.url);
        fb.auth(Meta.token, function(error, result) {
          if(error) {
            console.log("Login Failed!", error);
          } else {
            console.log('Auth ok.');
             var fbMessages = fb.child('broadcast');

             $scope.messages = angularFireCollection(fbMessages.limit(50));

             $scope.addMessage = function() {
                  $scope.messages.add({text:$scope.messageText, sender:Meta.username, time: new Date().getTime()});
             };
          }
        });

[katowulf]

Scratch that, I just talked this over with Michael Lehenbauer at Firebase and I was incorrect. I don't think that you need to wait for the .auth() call to invoke the callback. Sorry about that.

[lifeisfoo]

On the "broadcast" resource I have only a simple rule:

"broadcast": {
      ".read": "auth != null",
      "$key": {    
        ".write": "!data.exists() && auth != null"
      }
    },

It's the "users" rule that is very big (over 100 lines) with 17 subresources.

[katowulf]

This turned out to be a Firebase related issue and unrelated to angularFire. Closing this ticket. Will track internally.