blinksh / blinksh/blink

Bugs in build after hours using and configuration

Open
#2,132 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Swift
Stars
6.9k
Forks
746
PR merge metrics
No merged PRs in 30d

Description

### Checklist

- [x] Using latest version on the [App Store](http://itunes.apple.com/app/id1156707581)
- [x] Read the [docs](http://blink.sh/docs/)
- [x] Searched for [existing GitHub issues](https://github.com/blinksh/blink/issues)

### Configuration

### Describe the bug

* When accessing Build after a few hours away, I have to install tools that I already installed before

* following the same line of accessing the build after a few hours configurations, like apt update it gives conflict in keys:

> Err:4 https://packages.sury.org/php bookworm InRelease
The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key
Err:5 https://cli.github.com/packages stable InRelease
The following signatures were invalid: EXPKEYSIG 23F3D4EA75716059 GitHub CLI

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the Build access after several hours away, then inspect how installed tools and configuration persist. Check the reported apt update failures for the packages.sury.org/php and cli.github.com sources. Done means previously installed tools remain available and apt update completes without the reported signature conflicts.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, php, shell
Domain
build-system, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.