JanDeDobbeleer / oh-my-posh

The most customisable and low-latency cross platform/shell prompt renderer
https://ohmyposh.dev
MIT License
17.37k stars 2.39k forks source link

oh-my-posh font install failed to get nerd fonts release #3897

Closed maximunited closed 1 year ago

maximunited commented 1 year ago

Code of Conduct

What happened?

Try downloading fonts behind a proxy

Theme

default

What OS are you seeing the problem on?

Windows

Which shell are you using?

cmd

Log output

>oh-my-posh font install

    failed to get nerd fonts release
>oh-my-posh debug --plain

Version: 16.8.0

Shell: oh-my-posh

Segments:

ConsoleTitle(true)                        -   1 ms - oh-my-posh in alter
session(true)                             -   0 ms -  alter
path(true)                                -   1 ms -   ~
git(false)                                -  35 ms -
root(true)                                -   0 ms -  
exit(true)                                -   0 ms -  
node(false)                               -   0 ms -
go(false)                                 -   0 ms -
python(false)                             -   0 ms -
shell(true)                               -   0 ms - in oh-my-posh
time(true)                                -   0 ms - at 16:08:42

Run duration: 57.4257ms
JanDeDobbeleer commented 1 year ago

@maximunited are you able to reach GitHub from the proxy? It tries to call the following endpoint https://api.github.com/repos/ryanoasis/nerd-fonts/releases/latest

maximunited commented 1 year ago

Yes I can. For example, I'm using scoop, and I had to manually configure it to use proxy to make it work.

JanDeDobbeleer commented 1 year ago

@maximunited unfortunately we have no way to configure a proxy, and I'm pretty sure this breaks segments as well. Will give it a thought, but it's going to be a though nut if we can't simply bypass it.

github-actions[bot] commented 11 months ago

This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a discussion first, complete the body with all the details necessary to reproduce, and mention this issue as reference.