[issue30828] Out of bounds write in _asyncio_Future_remove_done_callback

2017-09-03 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___

[issue30828] Out of bounds write in _asyncio_Future_remove_done_callback

2017-07-05 Thread Yury Selivanov
Yury Selivanov added the comment: New changeset aaa4f991518611d101fba1ef3ecb18d7b385ad5b by Yury Selivanov in branch '3.6': [3.6] bpo-30828: Fix out of bounds write in `asyncio.CFuture.remove_done_callback() (GH-2569) (#2590)

[issue30828] Out of bounds write in _asyncio_Future_remove_done_callback

2017-07-05 Thread Yury Selivanov
Changes by Yury Selivanov : -- pull_requests: +2660 ___ Python tracker ___ ___

[issue30828] Out of bounds write in _asyncio_Future_remove_done_callback

2017-07-05 Thread Yury Selivanov
Yury Selivanov added the comment: New changeset 833a3b0d3707200daeaccdd218e8f18a190284aa by Yury Selivanov in branch 'master': bpo-30828: Fix out of bounds write in `asyncio.CFuture.remove_done_callback() (#2569)

[issue30828] Out of bounds write in _asyncio_Future_remove_done_callback

2017-07-04 Thread Yury Selivanov
Changes by Yury Selivanov : -- pull_requests: +2640 ___ Python tracker ___ ___

[issue30828] Out of bounds write in _asyncio_Future_remove_done_callback

2017-07-02 Thread Ned Williamson
New submission from Ned Williamson: This is very similar to the issue reported in https://bugs.python.org/issue28963 - this function is still buggy when items are pushed onto the done callbacks, as the new list is assumed to be large enough. The issue was pointed out on the code review page