Repository navigation
Conversation
|
Hi there @taldcroft 👋 - thanks for the pull request! I'm just a friendly 🤖 that checks for issues related to the changelog and making sure that this pull request is milestoned and labeled correctly. This is mainly intended for the maintainers, so if you are not a maintainer you can ignore this, and a maintainer will let you know if any action is required on your part 😃. I noticed the following issue with this pull request:
Would it be possible to fix this? Thanks! If there are any issues with this message, please report them here. |
|
Ugh, nothing is ever easy... |
|
I don't know what is the right shouting and swearing emoji, but I give up. Now there is some weird (probably intermittent) recursive problem from the same place! |
|
See #6291 (comment) before proceeding - the weakref was definitely not the issue. |
|
FWIW I restarted the one failing job and it passed. |
|
@taldcroft - And would you like to get this in to 2.0.0, not that @astrofrog found out this wasn't the cause for the issues we saw? (I'm waiting for one more appveyor at the moment, so could merge this in, too, and then start the release procedure again). |
|
@taldcroft - Could you rebase? I've remilestoned this to the next bugfix, but if it gets an approval very soon, I'm happy to include it in 2.0.3 |
|
Hi humans 👋 - this pull request hasn't had any new commits for approximately 5 months. I plan to close this in a month if the pull request doesn't have any new commits by then. In lieu of a stalled pull request, please consider closing this and open an issue instead if a reminder is needed to revisit in the future. Maintainers may also choose to add If this PR still needs to be reviewed, as an author, you can rebase it to reset the clock. You may also consider sending a reminder e-mail about it to the astropy-dev mailing list. If you believe I commented on this pull request incorrectly, please report this here. |
|
@taldcroft - I actually do not remember what the status of this problem is... |
|
I don't recall precisely either, but I think the comment above is where things left off: "I don't know what is the right shouting and swearing emoji, but I give up. Now there is some weird (probably intermittent) recursive problem from the same place!" |
|
⏰ Time's up! ⏰ I'm going to close this pull request as per my previous message. If you think what is being added/fixed here is still important, please remember to open an issue to keep track of it. Thanks! If this is the first time I am commenting on this issue, or if you believe I closed this issue incorrectly, please report this here. |
@saimn @eteq @bsipocz @mhvk @astrofrog - this may be the ticket on the Table reference cycle problem. Basically just breaking the reference cycles when the internal TableColumn object is being deleted. In my testing this did the trick and I could do the following with no increment of memory:
Fixes #6276