-
Notifications
You must be signed in to change notification settings - Fork 7
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
segway on SGE does not submit job arguments longer than 1024 chars #72
Comments
Original comment by Rachel Chan (Bitbucket: rcwchan). This bug also occurs on h4h (PBS Torque system). I've emailed the issue to the support email for pbs-drmaa. |
Original comment by Eric Roberts (Bitbucket: ericr86, GitHub: ericr86).
Resolved in Pull Request #55 The DRMAA issues themselves are still outstanding but this is a suitable workaround that should completely ignore this corner case. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Original report (BitBucket issue) by Rachel Chan (Bitbucket: rcwchan).
This is a DRMAA issue that segway is impacted by. Upon calling
__set__
fromdrmaa/helpers.py
is called, and does the following:string_vector(value)
has no truncating effect on the passed arguments. It isdrmaa_set_vector_attribute
that appears to have a buffer overflow of some sort and caps all arguments at 1024 chars.This seems like a pre-existing issue that was only more easily isolated with minibatch (presumably because the list of windows was random in length, and you were unlikely (rather than likely) to hit a partial window that already existed (for example: cutting the window number '1000' in half, without minibatch, 10 would likely be a valid window, and so ending the argument there would throw no error, but with minibatch, 10 is unlikely to be a valid window due to its random nature).
The bug can be easily recreated and shown with pdb with the following simple test:
shows clearly that
job_template.args
is truncated byset_vector_attribute
. It can also be speculated that the unicode memory issue in issue 60 (#60) could be caused by this buffer overflow as well.The text was updated successfully, but these errors were encountered: