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

[bug] [question] apt reports changed origin to 'Pulp 3' ? at htttp://packages.microsoft.com/repos/code #96

Closed
razielanarki opened this issue Nov 20, 2023 · 34 comments
Labels
bug Something isn't working

Comments

@razielanarki
Copy link

razielanarki commented Nov 20, 2023

Describe the issue

i may have missed an announcement?

$ sud oapt-get upatte
E: Repository 'http://packages.microsoft.com/repos/code stable InRelease' changed its 'Origin' value from 'code stable' to 'Pulp 3'
E: Repository 'http://packages.microsoft.com/repos/code stable InRelease' changed its 'Label' value from 'code stable' to ''

When did the issue occur?
just now

If applicable, what package did you attempt to install, and from which repo?

Steps to Reproduce
sudo apt-get update

Actual Result
warning

Expected Result
code-insiders updated

Additional context
i am running code-insiders on ubuntu-mantic+proposed w mainline kernel 6.7.0-rc2 (self-signed)

@razielanarki razielanarki added the bug Something isn't working label Nov 20, 2023
@razielanarki razielanarki changed the title apt reports changed orogin 'Pulp 3' ? at htttp://packages.microsoft.com/repos/code apt reports changed origin to 'Pulp 3' ? at htttp://packages.microsoft.com/repos/code Nov 20, 2023
@razielanarki razielanarki changed the title apt reports changed origin to 'Pulp 3' ? at htttp://packages.microsoft.com/repos/code [bug] [questin] apt reports changed origin to 'Pulp 3' ? at htttp://packages.microsoft.com/repos/code Nov 20, 2023
@razielanarki razielanarki changed the title [bug] [questin] apt reports changed origin to 'Pulp 3' ? at htttp://packages.microsoft.com/repos/code [bug] [question] apt reports changed origin to 'Pulp 3' ? at htttp://packages.microsoft.com/repos/code Nov 20, 2023
@daviddavis
Copy link
Member

@razielanarki thanks for the bug report. Looks like this is a bug and we should have a fix out shortly. Apologies.

@Teo80
Copy link

Teo80 commented Nov 20, 2023

@razielanarki thanks for the bug report. Looks like this is a bug and we should have a fix out shortly. Apologies.

On my PC with Ubuntu I unfortunately accepted the change proposed by APT: is there any security implications? Can I rest assured?
Thank you

@mbearup
Copy link
Collaborator

mbearup commented Nov 20, 2023

@Teo80 there's not a security implication per se, the repo signatures are your safeguard against that. But you'll have to accept the change again when the fields go back to their expected value (which we're actively working to fix).

@mbearup
Copy link
Collaborator

mbearup commented Nov 20, 2023

The fix has been implemented, and all affected repos have been re-published to correct the Origin and Label fields.
Any users who accepted the change (from code stable to Pulp) will be prompted again to accept the change back to code stable.
This should now be resolved for all repos/users.

@mbearup mbearup closed this as completed Nov 20, 2023
@chr1s-code
Copy link

chr1s-code commented Nov 20, 2023

I'm still experiencing this issue on Ubuntu 22.04.3 LTS. When downloading the InRelease file manually it still says:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Origin: Pulp 3
Suite: stable
Codename: stable
Date: Mon, 20 Nov 2023 10:14:43 +0000
Architectures: amd64 arm64 armhf all
Components: main
Acquire-By-Hash: no
SHA256: ...

@helge000
Copy link

Also still have the issue, Debian Bullseye (cleaned all metadata)

@helge000
Copy link

@mbearup - right, it is correct now; maybe just some CDN/caching issues.

@mbearup
Copy link
Collaborator

mbearup commented Nov 20, 2023

Could you confirm which repos you're trying to sync? I tried our Ubuntu 22.04, Debian 11, and code repos, and I see the correct origin/label reflected in each

$ curl -s https://packages.microsoft.com/ubuntu/22.04/prod/dists/jammy/InRelease | head -n 10
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Origin: microsoft-ubuntu-jammy-prod jammy
Label: microsoft-ubuntu-jammy-prod jammy
Suite: jammy
Codename: jammy
Date: Fri, 17 Nov 2023 23:17:41 +0000
Architectures: amd64 arm64 armhf all
Components: main
$ curl -s https://packages.microsoft.com/debian/11/prod/dists/bullseye/InRelease | head -n 10
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Origin: microsoft-debian-bullseye-prod bullseye
Label: microsoft-debian-bullseye-prod bullseye
Suite: bullseye
Codename: bullseye
Date: Sat, 18 Nov 2023 09:07:19 +0000
Architectures: amd64 arm64 armhf all
Components: main
$ curl -s https://packages.microsoft.com/repos/code/dists/stable/InRelease | head -n 10
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Origin: code stable
Label: code stable
Suite: stable
Codename: stable
Date: Fri, 17 Nov 2023 14:14:32 +0000
Architectures: amd64 arm64 armhf all
Components: main

@julian-klode
Copy link

julian-klode commented Nov 20, 2023

I saw the same issue just now, but a 2nd run worked so some CDN wonkyness still.

that was http://packages.microsoft.com/repos/code/dists/stable/InRelease

@Silvergti
Copy link

Silvergti commented Nov 20, 2023

I am having the same issue still:

Get:19 https://packages.microsoft.com/repos/ms-teams stable InRelease [5931 B]
E: Repository 'http://packages.microsoft.com/repos/code stable InRelease' changed its 'Origin' value from 'code stable' to 'Pulp 3'
E: Repository 'http://packages.microsoft.com/repos/code stable InRelease' changed its 'Label' value from 'code stable' to ''
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] 
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.3 LTS
Release:	22.04
Codename:	jammy
deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main

@mbearup
Copy link
Collaborator

mbearup commented Nov 20, 2023

@Silvergti could you confirm which IP you're hitting for packages.microsoft.com? I no longer see the issue repro'ing, but I can check if there's an issue with an individual mirror.

@Silvergti
Copy link

@mbearup:

host packages.microsoft.com
packages.microsoft.com is an alias for apt-geofence-parent.trafficmanager.net.
apt-geofence-parent.trafficmanager.net is an alias for csd-apt-neu-d-4.northeurope.cloudapp.azure.com.
csd-apt-neu-d-4.northeurope.cloudapp.azure.com has address 137.135.134.16

@mbearup
Copy link
Collaborator

mbearup commented Nov 20, 2023

@Silvergti when I pull the metadata from that mirror, I see the correct values. If you're still seeing the issue, it may be due to layers of caching along your network path.

$ curl -s http://csd-apt-neu-d-4.northeurope.cloudapp.azure.com/repos/code/dists/stable/InRelease | head -n 10
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Origin: code stable
Label: code stable
Suite: stable
Codename: stable
Date: Wed, 15 Nov 2023 11:13:39 +0000
Architectures: amd64 arm64 armhf all
Components: main

@Silvergti
Copy link

Silvergti commented Nov 20, 2023

Hello @mbearup

That might have been the case, indeed.

I am getting the same as you (never ran this when it wasn't working):

$ curl -s http://csd-apt-neu-d-4.northeurope.cloudapp.azure.com/repos/code/dists/stable/InRelease | head -n 10
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Origin: code stable
Label: code stable
Suite: stable
Codename: stable
Date: Wed, 15 Nov 2023 11:13:39 +0000
Architectures: amd64 arm64 armhf all
Components: main

Re-tried again and it is working now.

Thanks!

@chr1s-code
Copy link

chr1s-code commented Nov 20, 2023

This is the resource apt tries to load

$ curl -s https://packages.microsoft.com/repos/code/dists/stable/InRelease | head -n 10
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Origin: Pulp 3
Suite: stable
Codename: stable
Date: Mon, 20 Nov 2023 10:14:43 +0000
Architectures: amd64 arm64 armhf all
Components: main
Acquire-By-Hash: no

Clearing the apt cache worked.

Thanks!

@mbearup
Copy link
Collaborator

mbearup commented Nov 20, 2023

@chr1s-code can you confirm which IP address you're hitting? I can no longer repro, but glad to check an individual mirror if you still see the issue.

@yaroslavrick
Copy link

yaroslavrick commented Nov 20, 2023

This command solves the problem on local machine:

sudo apt-get clean

@romansh
Copy link

romansh commented Nov 20, 2023

Just run into the bug.

sudo apt-get clean didn't help.

@jasonzio
Copy link

@romansh can you tell us what repo you're attempting to use and what IP address your system resolves to for packages.microsoft.com? It's possible we have an edge node that didn't get an update.

@Janvanoorschot
Copy link

Same here. Debian. Messages are

❯ sudo apt update
Get:1 http://packages.microsoft.com/repos/code stable InRelease [3,533 B]
Hit:2 https://deb.debian.org/debian bookworm InRelease                                                                                                                      
Hit:3 https://download.docker.com/linux/debian bookworm InRelease                                                                                        
E: Repository 'http://packages.microsoft.com/repos/code stable InRelease' changed its 'Origin' value from 'code stable' to 'Pulp 3'
E: Repository 'http://packages.microsoft.com/repos/code stable InRelease' changed its 'Label' value from 'code stable' to ''
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] ^C

@jasonzio
Copy link

@Janvanoorschot can you tell us what IP address packages.microsoft.com resolves to on the system with the problem?

@romansh
Copy link

romansh commented Nov 20, 2023

@romansh can you tell us what repo you're attempting to use and what IP address your system resolves to for packages.microsoft.com? It's possible we have an edge node that didn't get an update.

deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main

ping packages.microsoft.com
PING csd-apt-weu-d-2.westeurope.cloudapp.azure.com (104.214.230.139) 56(84) bytes of data.

@Janvanoorschot
Copy link

@jasonzio

 dig packages.microsoft.com

; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> packages.microsoft.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32646
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;packages.microsoft.com.		IN	A

;; ANSWER SECTION:
packages.microsoft.com.	2840	IN	CNAME	apt-geofence-parent.trafficmanager.net.
apt-geofence-parent.trafficmanager.net.	2840 IN	CNAME csd-apt-weu-d-3.westeurope.cloudapp.azure.com.
csd-apt-weu-d-3.westeurope.cloudapp.azure.com. 2840 IN A 40.114.136.21

;; Query time: 12 msec
;; SERVER: 192.168.2.1#53(192.168.2.1) (UDP)
;; WHEN: Mon Nov 20 19:30:11 CET 2023
;; MSG SIZE  rcvd: 175

@romansh
Copy link

romansh commented Nov 20, 2023

sudo apt-get clean
sudo apt-get update.

Everything is working as expected now.

@Foorack
Copy link

Foorack commented Nov 20, 2023

There seems to be some CDN caching issues. Curl'ing the Release file twice gives different results, once valid and once invalid.

root@myhostname:/root# curl https://packages.microsoft.com/repos/vscode/dists/stable/Release
Origin: vscode stable
Label: vscode stable
Suite: stable
Codename: stable
Date: Fri, 17 Nov 2023 14:10:38 +0000

<snip>

root@myhostname:/root# curl https://packages.microsoft.com/repos/vscode/dists/stable/Release
Origin: Pulp 3
Suite: stable
Codename: stable
Date: Mon, 20 Nov 2023 10:12:25 +0000

<snip>

@jasonzio
Copy link

jasonzio commented Nov 20, 2023

@Foorack @romansh @Janvanoorschot

I think I have this beaten into submission for now. Starting to deploy a fix to ensure this particular CDN caching issue doesn't repeat. Thanks for your patience and for giving us the info we needed to find the issue.

@maxvfischer
Copy link

I also got the error a couple of minutes ago, but ran it again now and it's gone. Thanks for fixing it so fast.

@Matthijs9030
Copy link

I have this running for some time, it is a random change in IP address, only 13.81.215.193 is wrong:

I am located the the Netherlands...

$ host packages.microsoft.com
packages.microsoft.com is an alias for apt-geofence-parent.trafficmanager.net.
apt-geofence-parent.trafficmanager.net is an alias for csd-apt-weu-d-4.westeurope.cloudapp.azure.com.
csd-apt-weu-d-4.westeurope.cloudapp.azure.com has address 13.81.215.193
$

$ while true; do date; wget https://packages.microsoft.com/repos/code/dists/stable/InRelease -O - 2>&1 | egrep 'Resolving|Origin:'; sleep 30; done
Mon 20 Nov 21:15:06 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.81.215.193
Origin: Pulp 3
Mon 20 Nov 21:15:37 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 104.214.230.139
Origin: code stable
Mon 20 Nov 21:16:07 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.80.99.124
Origin: code stable
Mon 20 Nov 21:16:37 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 40.114.136.21
Origin: code stable
Mon 20 Nov 21:17:07 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.80.99.124
Origin: code stable
Mon 20 Nov 21:17:37 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.81.215.193
Origin: Pulp 3
Mon 20 Nov 21:18:07 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 104.214.230.139
Origin: code stable
Mon 20 Nov 21:18:37 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.80.99.124
Origin: code stable
Mon 20 Nov 21:19:07 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 40.114.136.21
Origin: code stable
Mon 20 Nov 21:19:37 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.80.99.124
Origin: code stable
Mon 20 Nov 21:20:08 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.81.215.193
Origin: Pulp 3
Mon 20 Nov 21:20:38 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.80.99.124
Origin: code stable
Mon 20 Nov 21:21:08 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 40.114.136.21
Origin: code stable
Mon 20 Nov 21:21:38 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 104.214.230.139
Origin: code stable
Mon 20 Nov 21:22:08 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 104.214.230.139
Origin: code stable
Mon 20 Nov 21:22:38 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 40.114.136.21
Origin: code stable
Mon 20 Nov 21:23:08 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 40.114.136.21
Origin: code stable
Mon 20 Nov 21:23:38 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 40.114.136.21
Origin: code stable
Mon 20 Nov 21:24:08 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 40.114.136.21
Origin: code stable
Mon 20 Nov 21:24:39 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 104.214.230.139
Origin: code stable
Mon 20 Nov 21:25:09 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 40.114.136.21
Origin: code stable
Mon 20 Nov 21:25:39 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 40.114.136.21
Origin: code stable
Mon 20 Nov 21:26:09 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 40.114.136.21
Origin: code stable
Mon 20 Nov 21:26:39 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.81.215.193
Origin: Pulp 3
Mon 20 Nov 21:27:09 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.80.99.124
Origin: code stable
Mon 20 Nov 21:27:39 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 40.114.136.21
Origin: code stable
Mon 20 Nov 21:28:09 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.80.99.124
Origin: code stable
Mon 20 Nov 21:28:39 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 40.114.136.21
Origin: code stable
Mon 20 Nov 21:29:10 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.81.215.193
Origin: Pulp 3
Mon 20 Nov 21:29:40 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.81.215.193
Origin: Pulp 3
Mon 20 Nov 21:30:10 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.80.99.124
Origin: code stable
Mon 20 Nov 21:30:40 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.81.215.193
Origin: Pulp 3
Mon 20 Nov 21:31:10 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.81.215.193
Origin: Pulp 3
Mon 20 Nov 21:31:40 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 104.214.230.139
Origin: code stable
Mon 20 Nov 21:32:10 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 104.214.230.139
Origin: code stable
Mon 20 Nov 21:32:40 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.80.99.124
Origin: code stable
Mon 20 Nov 21:33:10 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 40.114.136.21
Origin: code stable
Mon 20 Nov 21:33:41 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 104.214.230.139
Origin: code stable
Mon 20 Nov 21:34:11 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 40.114.136.21
Origin: code stable
Mon 20 Nov 21:34:41 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 40.114.136.21
Origin: code stable
Mon 20 Nov 21:35:11 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 104.214.230.139
Origin: code stable
Mon 20 Nov 21:35:41 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 40.114.136.21
Origin: code stable
Mon 20 Nov 21:36:11 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.80.99.124
Origin: code stable
Mon 20 Nov 21:36:41 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.80.99.124
Origin: code stable
Mon 20 Nov 21:37:11 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.80.99.124
Origin: code stable
Mon 20 Nov 21:37:42 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.80.99.124
Origin: code stable
Mon 20 Nov 21:38:12 CET 2023
Resolving packages.microsoft.com (packages.microsoft.com)... 13.80.99.124
Origin: code stable

Hope this helps...

@Janvanoorschot
Copy link

@jasonzio problem fixed for me. Thanks!

@jasonzio
Copy link

Thanks to all. A fix has been deployed which should prevent this from recurring. If you see this happen again, please do let us know.

Again, thanks for your patience.

@ps-spb
Copy link

ps-spb commented Nov 21, 2023

Seeing this across our estate this morning, from AWS WorkSpaces Ubuntu instances which we manage with Ansible:

TASK [ubuntu_generic : Ubuntu apt Configuration] *******************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to update apt cache: E:Repository 'http://packages.microsoft.com/repos/code stable InRelease' changed its 'Origin' value from 'Pulp 3' to 'code stable', E:Repository 'http://packages.microsoft.com/repos/code stable InRelease' changed its 'Label' value from '' to 'code stable', W:This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details., W:https://pkg.osquery.io/deb/dists/deb/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details."}

trying to run the fix above doesn't work:

root@U-35ZOJRWXMSS74:/home/psadmin# apt clean
root@U-35ZOJRWXMSS74:/home/psadmin# apt update
Hit:1 http://198.19.64.253/updates/linux/apt jammy InRelease
Get:2 http://packages.microsoft.com/repos/code stable InRelease [3,589 B]
Hit:3 http://eu-west-2.ec2.archive.ubuntu.com/ubuntu jammy InRelease                                                                                                                                                       
Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease                                                                                                                                                           
Hit:5 http://eu-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates InRelease                                                                                                                         
Hit:6 https://download.docker.com/linux/ubuntu jammy InRelease                                                                                                                                       
Hit:7 http://eu-west-2.ec2.archive.ubuntu.com/ubuntu jammy-backports InRelease                                                                                                                                                        
Hit:8 https://dl.google.com/linux/chrome/deb stable InRelease                                                                                                                                                                         
E: Repository 'http://packages.microsoft.com/repos/code stable InRelease' changed its 'Origin' value from 'Pulp 3' to 'code stable'                                                     
E: Repository 'http://packages.microsoft.com/repos/code stable InRelease' changed its 'Label' value from '' to 'code stable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] 

@Foorack
Copy link

Foorack commented Nov 21, 2023

@ps-spb In your case the machine has already accepted the incorrect Origin "Pulp 3", and you therefore has to accept it again to revert it back to "code stable".

You can automate this via ansible with apt-get update --allow-releaseinfo-change

@srelf-eschercloud
Copy link

jasonzio would it be possible share the fix on the pulp side. As I'm having a similar issue internally :D

@sdherr
Copy link
Contributor

sdherr commented Nov 21, 2023

jasonzio would it be possible share the fix on the pulp side. As I'm having a similar issue internally :D

@srelf-eschercloud Try setting publish_upstream_release_fields=True on repositories that existed before the pulp_deb 3.0.0 upgrade.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests