unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Thomas Hisch <thomas.hisch@ims.co.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34855@debbugs.gnu.org
Subject: bug#34855: 27.0.50; url-retrieve-synchronously Bad request Error every 2nd call
Date: Thu, 14 Mar 2019 17:48:24 +0100	[thread overview]
Message-ID: <9d877dcf-d29d-1bb4-1c66-e4b72e767d94@ims.co.at> (raw)
In-Reply-To: <8336np3a1w.fsf@gnu.org>

On 3/14/19 1:38 PM, Eli Zaretskii wrote:
>> From: Thomas Hisch <thomas.hisch@ims.co.at>
>> Date: Thu, 14 Mar 2019 12:01:54 +0100
>>
>> The emacs 27.0 build, where the test fails,  was build be me locally.
>> Could it be that something between emacs 26.1 and the HEAD of master
>> broke sth?
> 
> Please see if it weren't my recent changes in commit 9486d87cfe that
> broke this.

Thx for the fast answer.

Your  commit 9486d did not break this issue.

The commit that broke it is

84613dae5c34ea742dd9a3e56f5acb55f604b483

Reverting it locally fixed the issue for me.

Sry that that recipe was a bit too long.
Do you still want me to shrink the recipe?

Regards
Thomas

> 
> If my changes are not the reason, I'd appreciate if you could bisect
> to find the commit which broke this, since the reproduction recipe you
> provided is quite complex.  Alternatively, a simpler reproducer
> starting from "emacs -Q" would be welcome.
> 
> Thanks.
> 
---------------------------------------------------------------------


Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte 
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese 
E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den 
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie 
die unbefugte Weitergabe dieser Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail 
in error) please notify the sender immediately and destroy this e-mail. 
Any unauthorized copying, disclosure or distribution of the material 
in this e-mail is strictly prohibited

IMS Nanofabrication GmbH
FN: 208021 p, FB-Gericht: Wien;
Sitz: Schreygasse 3, 1020, Vienna (Austria),Tel. +43 1 214 48 94; 
E-Mail: imsoffice@ims.co.at; DVR-Nr: 0374369; www.ims.co.at






  reply	other threads:[~2019-03-14 16:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 11:01 bug#34855: 27.0.50; url-retrieve-synchronously Bad request Error every 2nd call Thomas Hisch
2019-03-14 12:38 ` Eli Zaretskii
2019-03-14 16:48   ` Thomas Hisch [this message]
2019-03-14 18:06     ` Eli Zaretskii
2019-03-18 21:43       ` Andreas Schwab
2019-03-22 20:13         ` Thomas Hisch
2019-03-22 21:00           ` Eli Zaretskii
2019-03-22 22:42             ` Thomas Hisch
2019-03-23  6:39               ` Eli Zaretskii

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=9d877dcf-d29d-1bb4-1c66-e4b72e767d94@ims.co.at \
    --to=thomas.hisch@ims.co.at \
    --cc=34855@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).