You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the upgrade check fails (due to a network issue or VPN), oh-my-posh retries the check every time a terminal is opened, ignoring configuration options intended to limit these checks.
For instance:
Upgrade checks are performed despite auto_upgrade being set to false and interval being specified.
The only upgrade-related configuration that appears to be respected is the source parameter.
Documentation for oh-my-posh seems outdated, as it doesn't mention newer options such as disable_notice and auto_upgrade.
A VPN (e.g., ExpressVPN) is one scenario that can cause these failures consistently. In fact, I am able to resolve the domain name and get a response from the version URLs that omp uses with cURL but omp fails for some reason. I even tried to isolate the download functionality and compile a simple program in Go that relies on net/http to test and it worked just fine.
Steps to Reproduce
Simulate conditions where the upgrade check might fail.
Set any configuration option related to upgrades other than source (auto, notice, etc.).
Observe:
Long delays occur due to timeouts while attempting to fetch the version from the CDN.
Upgrade checks are triggered every time the terminal is opened, regardless of the configuration settings.
Expected Behavior
Upgrade checks should respect the interval configuration, even if previous fetch attempts failed.
Options like auto_upgrade: false and disable_notice: true should be respected.
Relevant Code Reference
The issue is most likely due to the lack of caching when the upgrade check fails, leading to the interval setting being ignored.
Code of Conduct
What happened?
Description
When the upgrade check fails (due to a network issue or VPN),
oh-my-posh
retries the check every time a terminal is opened, ignoring configuration options intended to limit these checks.For instance:
auto_upgrade
being set tofalse
andinterval
being specified.source
parameter.oh-my-posh
seems outdated, as it doesn't mention newer options such asdisable_notice
andauto_upgrade
.A VPN (e.g., ExpressVPN) is one scenario that can cause these failures consistently. In fact, I am able to resolve the domain name and get a response from the version URLs that
omp
uses with cURL butomp
fails for some reason. I even tried to isolate the download functionality and compile a simple program in Go that relies onnet/http
to test and it worked just fine.Steps to Reproduce
source
(auto
,notice
, etc.).Expected Behavior
interval
configuration, even if previous fetch attempts failed.auto_upgrade: false
anddisable_notice: true
should be respected.Relevant Code Reference
The issue is most likely due to the lack of caching when the upgrade check fails, leading to the
interval
setting being ignored.oh-my-posh/src/segments/upgrade.go
Lines 74 to 87 in b1694b5
Theme
What OS are you seeing the problem on?
Windows
Which shell are you using?
powershell
Log output
The text was updated successfully, but these errors were encountered: