{"action":"created","issue":{"url":"https://api.github.com/repos/TissueMAPS/TissueMAPS/issues/123","repository_url":"https://api.github.com/repos/TissueMAPS/TissueMAPS","labels_url":"https://api.github.com/repos/TissueMAPS/TissueMAPS/issues/123/labels{/name}","comments_url":"https://api.github.com/repos/TissueMAPS/TissueMAPS/issues/123/comments","events_url":"https://api.github.com/repos/TissueMAPS/TissueMAPS/issues/123/events","html_url":"https://github.com/TissueMAPS/TissueMAPS/issues/123","id":350836726,"node_id":"MDU6SXNzdWUzNTA4MzY3MjY=","number":123,"title":"Delay in propagating the \"TERMINATED\" state in GC3Pie","user":{"login":"riccardomurri","id":447228,"node_id":"MDQ6VXNlcjQ0NzIyOA==","avatar_url":"https://avatars3.githubusercontent.com/u/447228?v=4","gravatar_id":"","url":"https://api.github.com/users/riccardomurri","html_url":"https://github.com/riccardomurri","followers_url":"https://api.github.com/users/riccardomurri/followers","following_url":"https://api.github.com/users/riccardomurri/following{/other_user}","gists_url":"https://api.github.com/users/riccardomurri/gists{/gist_id}","starred_url":"https://api.github.com/users/riccardomurri/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/riccardomurri/subscriptions","organizations_url":"https://api.github.com/users/riccardomurri/orgs","repos_url":"https://api.github.com/users/riccardomurri/repos","events_url":"https://api.github.com/users/riccardomurri/events{/privacy}","received_events_url":"https://api.github.com/users/riccardomurri/received_events","type":"User","site_admin":false},"labels":[{"id":483547533,"node_id":"MDU6TGFiZWw0ODM1NDc1MzM=","url":"https://api.github.com/repos/TissueMAPS/TissueMAPS/labels/discussion","name":"discussion","color":"d4c5f9","default":false},{"id":458187715,"node_id":"MDU6TGFiZWw0NTgxODc3MTU=","url":"https://api.github.com/repos/TissueMAPS/TissueMAPS/labels/enhancement","name":"enhancement","color":"84b6eb","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-08-15T14:44:15Z","updated_at":"2018-08-15T14:44:16Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"_From @riccardomurri on February 29, 2016 20:50_\n\nReported originally in issue #21:\n\n> There seems to be a general delay in updating parent tasks via\n> GC3Pie (on localhost as well as on the cluster). In case of a\n> sequential task collection, the state and exitcode of the parent\n> collection is not updated within one progress() engine iteration\n> once the last children task is TERMINATED\n\nThis depends on the level of nesting: as a general rule, you need one\nmore `Engine.progress()` _per nesting level_.  In other words, for a\nworkflow structure like the following:\n\n  SequentialTaskCollection\n    ParallelTaskCollection (1)\n      Application (1..N)\n\nwhen all the `Application`s have turned to TERMINATED, the\n`ParallelTaskCollection` will turn to TERMINATED (within 1\n`Engine.progress()`) and _only then_ will the\n`SequentialTaskCollection` turn to TERMINATED (again within 1\n`Engine.progress()`).\n\nHowever:\n\n1) The GC3Pie API makes no guarantee that the `TERMINATED` state will\nbe propagated upwards within 1 `progress()` cycle (and indeed I am not\nsure this is true in all cases).  What is guaranteed is that it will\nhappen _eventually_.\n\n2) I do not understand why this is a concern at all.  Your monitoring\nloop should exit based on the status of the outer task (e.g., the\n`SequentialTaskCollection` in the example above) and not care about\nthe status of the included tasks.  That's the whole point of having\ntask collection objects...\n\n\n_Copied from original issue: TissueMAPS/TmLibrary#22_"},"comment":{"url":"https://api.github.com/repos/TissueMAPS/TissueMAPS/issues/comments/413220042","html_url":"https://github.com/TissueMAPS/TissueMAPS/issues/123#issuecomment-413220042","issue_url":"https://api.github.com/repos/TissueMAPS/TissueMAPS/issues/123","id":413220042,"node_id":"MDEyOklzc3VlQ29tbWVudDQxMzIyMDA0Mg==","user":{"login":"riccardomurri","id":447228,"node_id":"MDQ6VXNlcjQ0NzIyOA==","avatar_url":"https://avatars3.githubusercontent.com/u/447228?v=4","gravatar_id":"","url":"https://api.github.com/users/riccardomurri","html_url":"https://github.com/riccardomurri","followers_url":"https://api.github.com/users/riccardomurri/followers","following_url":"https://api.github.com/users/riccardomurri/following{/other_user}","gists_url":"https://api.github.com/users/riccardomurri/gists{/gist_id}","starred_url":"https://api.github.com/users/riccardomurri/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/riccardomurri/subscriptions","organizations_url":"https://api.github.com/users/riccardomurri/orgs","repos_url":"https://api.github.com/users/riccardomurri/repos","events_url":"https://api.github.com/users/riccardomurri/events{/privacy}","received_events_url":"https://api.github.com/users/riccardomurri/received_events","type":"User","site_admin":false},"created_at":"2018-08-15T14:44:16Z","updated_at":"2018-08-15T14:44:16Z","author_association":"CONTRIBUTOR","body":"> It seems I have to implement it in such a way that next() can be\n> called repeatedly until the TERMINATED state is reached without\n> actually progressing to the next \"stage\", i.e. building the next\n> task.\n\nThis shouldn't happen, i.e., `next()` should only be called when a\ntask is done and the next one needs to be prepared (or the whole\nsequence halted).\n\nCare to elaborate or to provide a test case?\n"}}
{"actor":{"display_login":"riccardomurri"}}