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.

Sign up for GitHub

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

Jump to bottom

Fix 'FutureWarning: Possible nested set at position 329' #381

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix 'FutureWarning: Possible nested set at position 329' #381

wants to merge 1 commit into from
+1 −1

Conversation

jmduke
Copy link

@jmduke jmduke commented Jun 22, 2019

No description provided.

@jmduke jmduke mentioned this pull request Jun 22, 2019
Closed
@coveralls
Copy link

coveralls commented Jun 22, 2019 •
edited
Loading

Coverage Status

Coverage remained the same at 66.9% when pulling 47c048e on buttondown-email:fix-nested-set-warning into fb32b31 on Kronuz:master.

@olorton
Copy link

olorton commented May 1, 2020 •
edited
Loading

I too encountered this issue. What is holding up this PR?

@chrisjsewell chrisjsewell mentioned this pull request Sep 3, 2020
Open
@amotoki
Copy link
Contributor

amotoki commented Jan 21, 2021

It looks like the issue was fixed by PR #403. I don't know why PR proposed later was merged but anyway this is no longer needed.

@christopherpickering
Copy link

#403 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
5 participants
@jmduke @coveralls @olorton @amotoki @christopherpickering