Fatal (but not actually fatal) Login Errror for SMP Logins
Open
Nobody has claimed this yet.
bug
good first issue
- Dominant language
- Go
- Stars
- 25
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
It seems when a customer is in an airgap the cli will still successfully log into their SMP environment but will provide a FATAL error message. Maybe we hide this message if they have a flag like --smp true?
Login successfully done. Yay!
FATA[2024-08-01T09:40:21-04:00] Post [https://stats.drone.ci/api/v1/harnesscli](https://url.us.m.mimecastprotect.com/s/G9NuC5y42LuwEOyVtzfMukmy10?domain=stats.drone.ci): read tcp 10.xxx.xx.xx:50313->[35.210.215.84:443](https://url.us.m.mimecastprotect.com/s/By1VC68N39UZzxRnF6hPu5G4Zc?domain=35.210.215.84) read: connection reset by peer
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CLI login flow and the handling of the --smp option, then reproduce an air-gapped SMP login to observe the telemetry request to stats.drone.ci. Trace why a failed stats connection is emitted as a fatal error after successful login; done means the login remains successful without the misleading fatal message in this scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100