{"action":"closed","issue":{"url":"https://api.github.com/repos/knockout/knockout/issues/2108","repository_url":"https://api.github.com/repos/knockout/knockout","labels_url":"https://api.github.com/repos/knockout/knockout/issues/2108/labels{/name}","comments_url":"https://api.github.com/repos/knockout/knockout/issues/2108/comments","events_url":"https://api.github.com/repos/knockout/knockout/issues/2108/events","html_url":"https://github.com/knockout/knockout/issues/2108","id":168596189,"number":2108,"title":"Examining call stack when using deferred updates","user":{"login":"cervengoc","id":6099330,"avatar_url":"https://avatars.githubusercontent.com/u/6099330?v=3","gravatar_id":"","url":"https://api.github.com/users/cervengoc","html_url":"https://github.com/cervengoc","followers_url":"https://api.github.com/users/cervengoc/followers","following_url":"https://api.github.com/users/cervengoc/following{/other_user}","gists_url":"https://api.github.com/users/cervengoc/gists{/gist_id}","starred_url":"https://api.github.com/users/cervengoc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cervengoc/subscriptions","organizations_url":"https://api.github.com/users/cervengoc/orgs","repos_url":"https://api.github.com/users/cervengoc/repos","events_url":"https://api.github.com/users/cervengoc/events{/privacy}","received_events_url":"https://api.github.com/users/cervengoc/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-08-01T08:47:03Z","updated_at":"2016-08-01T22:57:05Z","closed_at":"2016-08-01T22:57:05Z","body":"One major negative in using deferred updates for me is that when I'm debugging, I'm unable to find out what actually caused an update, or reevaluation of a computed, etc. \r\n\r\nThis is because deferred updates process tasks asynchronously, so the update tasks are lifted out from code flow, so no call stack can be examined at runtime, because the bottom-most entry is always `processTasks`.\r\n\r\nIs there any workaround for it, or any way Knockout could handle it somehow? I mean some way to keep the call stack, or emulate it somehow, or anything...\r\n\r\nSwitching back to \"normal\" updates is not a good solution because the two modes can have huge execution differences."}}
{"actor":{"display_login":"brianmhunt"}}