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
resubmitted tasks doesn't have same session name #1834
Comments
The new session is not random, it's that of the Hub, the submitter of the new task. But I think you are right, it should start with the same header, and replace only the msg_id and timestamps. |
Yes, that would be cool. |
try: #1836 |
OK, seems to work. The resubmitted tasks now have the same session name. |
Reopening until the actual PR is merged. I'll have a look now. |
Carreau
pushed a commit
to Carreau/ipython
that referenced
this issue
Jun 3, 2012
Preserve header for resubmitted tasks (aside from new msg_id and timestamp). Also fixes a DictDB clobbering bug. Closes ipython#1834.
mattvonrocketstein
pushed a commit
to mattvonrocketstein/ipython
that referenced
this issue
Nov 3, 2014
header should be unchanged, aside from the msg_id and timestamp closes ipython#1834
mattvonrocketstein
pushed a commit
to mattvonrocketstein/ipython
that referenced
this issue
Nov 3, 2014
Preserve header for resubmitted tasks (aside from new msg_id and timestamp). Also fixes a DictDB clobbering bug. Closes ipython#1834.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I understand correctly, a task gets a new msg_id when you call client.resubmit(msg_id). I noticed that the 'cloned' task seems to have a random session name. I would suggest to take over all cutomizable attributes: session, username, retries, after, ... in order to let the resubmitted task behave like the original one.
One side effect for me would be to delete the original task after the resubmitted one took it's place.
The text was updated successfully, but these errors were encountered: