Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 1 commit into from Feb 8, 2012

Conversation

minrk
Copy link
Member

@minrk 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.

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
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
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant