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

WIP: initial migration to trust-dns 0.19 #17

Closed
wants to merge 1 commit into from

Conversation

drahnr
Copy link

@drahnr drahnr commented May 13, 2020

Since it's quite a pain having to have a certain version of a nightly toolchain making edits harder than necessary, an attempt to remedy this by upgrading to turst-dns*>= 0.19 and stabilized futures.

Ref #5

@valeriansaliou
Copy link
Owner

Thanks @drahnr ; this was on my ToDo, but you did it! I'll review the code & test it, then merge it over the evening.

@drahnr
Copy link
Author

drahnr commented May 14, 2020

Slow down, things are really very much in progress and this doesn't even compile just yet (hence the draft state of this PR), this will be a slow step by step progress :) feel free to chime in.

First I wanted to move things to be compiling, possibly leaving a few // TODO FIXME XXX comments where more work is needed.

Once it compiles, it might make sense to consider moving away from rocket towards something that is entirely futures based to avoid the mixins and the ever-chaning nightly requirement - but that is to be discussed after this migration is complete.

@valeriansaliou
Copy link
Owner

Oh, okay, sorry, I didn't test the code, just quick read changes, so my guess was it was ready to review :)

Let me know then when you feel that it's ready to merge. Thanks again.

@valeriansaliou
Copy link
Owner

References #19 as well, addresses main thread blocking DOS attacks we experienced at Crisp. For now, main thread blocking issue addressed in #20 though this MR will properly fix it for good.

@paulocoghi
Copy link

Considering that this PR is still in draft, what do you think about updating it with trust-dns (now hickory-dns) to its latest version 0.24.1?

@drahnr
Copy link
Author

drahnr commented Jul 11, 2024

Considering that this PR is still in draft, what do you think about updating it with trust-dns (now hickory-dns) to its latest version 0.24.1?

It's been way too long and I won't have time in the foreseeable to work on it. Feel free to pick it up :)

Closing

@drahnr drahnr closed this Jul 11, 2024
@paulocoghi
Copy link

paulocoghi commented Jul 14, 2024

@drahnr that's sad, but thanks anyway for the feedback 😄

@valeriansaliou
Copy link
Owner

I've started migration work to trust-dns 0.23 (then, I'll move it to the rebranded package), tracked in PR #27

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