Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Feature Request: Enable ability for downstreams to disable upgrade checking.

See original GitHub issue

The Issue

As a package maintainer for a downstream Linux operating system (Solus), I’d prefer to directly provide users with an upgraded package which respects our routine syncs to our stable repo, ensures that such app upgrades won’t negatively impact users, and alleviates any concerns on my part about unexpected behavior being reported to us for changes that may occur (such as a gained dependency that isn’t installed on the user’s system).

Currently, the LBRY app runs a check in src/renderer/redux/actions/app.js to see if an upgrade is available and subscribes to checks, however this is limited to a user-set disabling to skip an upgrade.

Ideally, I’d like an option as a downstream to disable upgrade checking entirely, even if it’s via an option with yarn. Currently I’ve opted to just patch out (with some overkill) update checking but would obviously like a more official solution.

Acceptance Criteria

Definition of Done

  • Tested against acceptance criteria
  • Tested against the assumptions of the user story
  • The project builds without errors
  • Unit tests are written and passing
  • Tests on devices/browsers listed in the issue have passed
  • QA performed & issues resolved
  • Refactoring completed
  • Any configuration or build changes documented
  • Documentation updated
  • Peer Code Review performed

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:11 (10 by maintainers)

github_iconTop GitHub Comments

kauffjcommented, Dec 13, 2017

Thanks @JoshStrobl! I strongly suspect we can accommodate this. Maybe one for @IGassmann?

kauffjcommented, Oct 16, 2019

@JoshStrobl hard-checking for a file on disk is a viable solution with a low time cost. I don’t see why we couldn’t do that. We’ve got to get through this upcoming release + release (which are basically the same release), but I’ll see if we can get this in in the release behind that one.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Feature Request: Ability to disable single default features #3126
Feature Request : Ability to disable single default features #3126 ... I need to check if defaults where added which I might want...
Read more >
Customize pipeline configuration - GitLab Docs
Go to your project and select Settings > Merge requests. Under Merge request approvals, select Enable next to the Coverage-Check approval rule. Select...
Read more >
Configure a software update point to use TLS/SSL with a PKI ...
Configure the software update point to require SSL communication to the WSUS server; Verify functionality with Configuration Manager ...
Read more >
1406814 – [RFE] Add ability to disable automatic checks for ...
This RFE just allows to disable automatic regular check for upgrades on hosts, which is enabled by default, but it's useless for users...
Read more >
New features and products in Tokyo
Manage vulnerability exception requests for configuration issues using either Vulnerability Response or GRC: Policy and Compliance Management integration. Based ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found