Sylvain Mina

@SergeAstapov Hi, thank you for taking time to answer. Unless I'm missing something, my use case is different, as I don't use snapshot/restore, but execute/unexecute. That said, I've tried to...

I've quickly read (maybe too quick), but I can't see what happen to the `{ scope: 'controller' }` thing.

@chriskrycho Sorry to bother you about this old one, but do you know what is the status of this ? I mean, I've searched a bit, but I can't find...

@locks Is it good enough now ?

@locks, I'm sorry, I don't understand the `@static`thing here, because this method is not a static one. 😕

Sorry for the noise, I think I've been too much agressive during my housekeeping...

Since the time I use ember-cli, I just always assumed it was "normal" to have to `ember s` again when changing the environnment.js file.

@runspired I'm sorry, I can't see if this issue is supposed to be closed by #8025. I'm on 4.6.1 and still encounter something like https://github.com/machty/ember-concurrency/issues/463, so I guess some cases...

I had to do this change too, but as @runspired advised on discord, it seems like using `remoteState` is the 'right' move. see: https://discord.com/channels/480462759797063690/490216705122107427/970796099432480869

I'm not even sure this is specific to ember-data-tracker. I encounter the same error when using this kind of property in an ember app ``` get notification() { return user.hasMany('fileTransferNotifications').value().firstObject;...