load header with engine id when engine dies in TaskScheduler #1369

Merged
merged 1 commit into from Feb 8, 2012

Conversation

Projects
None yet
1 participant
Owner

minrk commented Feb 2, 2012

This ensures that the metadata dict on the Client has the engine_uuid of the engine on which the task failed. Previously, this entry would remain empty.

It is identical to code elsewhere (Hub, Client) for constructing the dummy reply when engines die.

load header with engine id when engine dies in TaskScheduler
This ensures that the metadata dict on the *Client* has the engine_uuid of the engine on which the task failed.  It is identical to code elsewhere (Hub, Client) for identifying when engines die.

minrk added a commit that referenced this pull request Feb 8, 2012

Merge pull request #1369 from minrk/EngineError
load header with engine id when engine dies in TaskScheduler

This ensures that the metadata dict on the Client has the engine_uuid of the engine on which the task failed. Previously, this entry would remain empty.

It is identical to code elsewhere (Hub, Client) for constructing the dummy reply when engines die.

@minrk minrk merged commit 0291d61 into ipython:master Feb 8, 2012

mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this pull request Nov 3, 2014

Merge pull request #1369 from minrk/EngineError
load header with engine id when engine dies in TaskScheduler

This ensures that the metadata dict on the Client has the engine_uuid of the engine on which the task failed. Previously, this entry would remain empty.

It is identical to code elsewhere (Hub, Client) for constructing the dummy reply when engines die.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment