Closed M-Bab closed 1 year ago
@M-Bab Thank you for opening the issue, it was caused by a mistake in DNS configuration, It should be fixed now.
$ nslookup api.components.espressif.com
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: api.components.espressif.com
Address: 18.166.114.217
Name: api.components.espressif.com
Address: 16.162.213.162
Thanks for the fast reaction! Works well again.
Answers checklist.
IDF version.
v4.4.4
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
What is the expected behavior?
I expected to be able to build an idf project with idf.py and added managed components.
What is the actual behavior?
On some systems the build fails because the domain name of
api.components.espressif.com
cannot be resolved. I have actually no idea why this only fails on our CI machines (see log below) because the address can not be resolved anywhere:Unlike
api.components.espressif.com
the parent addresscomponents.espressif.com
can be resolved.Our CI docker works with ESP-IDF version v4.4.3 locally I work with v4.4.4 and I am aware that v4.4.5 is available. But neither should this have a large impact on the managed components nor did I find any note about changes there in the release notes.
Steps to reproduce.
Build or installation Logs.
More Information.
No response