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.

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

undid #740 #767

Merged
merged 1 commit into from
Dec 14, 2022
Merged

undid #740 #767

merged 1 commit into from
Dec 14, 2022

Conversation

comcloudway
Copy link
Contributor

What does this PR do and why is it necessary?

As concluded in #748,
#740 was supposed to be undone.

From what I can tell,
@rocus did not yet file a PR to undo the changes,
so I decided to so in order for the next branch to be working
(See #742).

How was it tested? How can it be tested by the reviewer?

As I no longer have an antenna, I was unable to do real tests.
But given that this commit basically undid #740 (I used the patch file)
it should be working exactly the same as before.

Any background context you want to provide?

I was unable to fix the segfault,
as discussed in #742.
And thus failed to make the feature function properly
(the cli crashed after a client disconnected)

What are the relevant tickets if any?

#740 , #742 , #748 , #738 , #741

Further notes

I did not add the changes proposed by @rocus in #748.
But I thought that undoing my PR,
might make pushing theirs easier.

And I'm not sure if I undid everything – but from what I can tell it was the only merged PR I did.

@AlbrechtL AlbrechtL requested a review from mpbraendli December 14, 2022 17:40
@AlbrechtL
Copy link
Owner

@mpbraendli Can you review this PR, please?

@mpbraendli mpbraendli merged commit 6b69a78 into AlbrechtL:next Dec 14, 2022
@mpbraendli
Copy link
Collaborator

Ok, this initial effort wasn't yet conclusive, but I hope the next one will be!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants