unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Visuwesh <visuweshm@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 58520@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: bug#58520: Persistent failure to DNS-lookup hostname
Date: Mon, 11 Dec 2023 17:24:24 +0530	[thread overview]
Message-ID: <87fs09uf7z.fsf@gmail.com> (raw)
In-Reply-To: <87edh6fdvo.fsf@gmail.com> (Visuwesh's message of "Sat, 04 Nov 2023 08:01:23 +0530")

[சனி நவம்பர் 04, 2023] Visuwesh wrote:

> [வெள்ளி நவம்பர் 03, 2023] Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" wrote:
>
>>>      3 Contacting host: search.brave.com:443
>>>      4 search.brave.com/0 Temporary failure in name resolution
>>>      5 cdn.search.brave.com/0 Temporary failure in name resolution
>>>      6 cdn.search.brave.com/0 Temporary failure in name resolution
>> [...]
>>>     11 Contacting host: search.brave.com:443
>>>     12 cdn.search.brave.com/0 Temporary failure in name resolution
>>
>>> Line nos. 1 and 2 are from url.el requests.  3--6 and 11--12 is from(
>>> connection to search.brave.com from eww for an internet search.
>>
>> Seems like the accesses failed just as well, so my guess is that the
>> only thing different with EWW is that it falls back on a cache or
>> something like that.
>
> You might be right actually.  If I face this next time, I should search
> something other than "asd."  If only eww recorded the time at which the
> request was made...

And that fateful day arrived again.  AFAICT, eww does not seem to hold
any cache (at least that's what searching for the word "cache" leads me
to believe) but url.el does seem to have some caching mechanism.  I
evaluated the sexp

    (let ((url-cache-expire-time 0)) (url-cache-prune-cache))

and tried searching in eww again and it did that weird thing where the
request failed with the same error but still managed to render the page
in the end.

So far, I think that this issue has to do with the DNS changing and
Emacs somehow not being aware of it?  If I can trace the DNS server
being used in the end by Emacs that would help confirm this.  I will try
asking around to see if I can do this.

P.S. It would be nice to have that patch that you mentioned that added a
     function that fixes the broken requests.





  reply	other threads:[~2023-12-11 11:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 16:20 bug#58520: Persistent failure to DNS-lookup hostname Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 16:55 ` Paul Eggert
2022-10-14 17:17   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-05 17:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-03  7:57   ` Visuwesh
2023-11-03 16:38     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-03 18:46       ` Visuwesh
2023-11-03 21:54         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-04  2:31           ` Visuwesh
2023-12-11 11:54             ` Visuwesh [this message]
2023-12-17 23:27               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-18 17:30                 ` Eli Zaretskii
2023-12-18 17:41                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-18 17:55                     ` Eli Zaretskii
2023-12-18 18:26                       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fs09uf7z.fsf@gmail.com \
    --to=visuweshm@gmail.com \
    --cc=58520@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).