Spotify auth url cut
Maintainers usually reply within 6 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- go
- Domain
- authentication, cli
Research direction
Start by finding the Spotify authentication flow and the step that displays the browser URL, then reproduce it in an SSH session without a monitor. Check how the URL is presented and copied in the terminal; done means the complete authentication URL can be copied and opened. The issue does not name a file or test, so trace the flow from the Spotify provider entry point.
Written by the indexing model from the issue text.
Description
What happened
When configuring spotify on a remote machine via SSH (without monitor), on the step with opening a browser, the url to be copy pasted to the browser is cut and cannot be fully copied.
Screenshots / video
Environment
- cliamp version (
cliamp --version): v1.63.2 - OS: ubuntu server
- Audio backend (PipeWire / PulseAudio / ALSA):
- Provider(s) involved: spotify
- Dominant language
- Go
- Stars
- 4.4k
- Forks
- 307
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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.
More from bjarneo/cliamp
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 6 days
-
Show the Podcast episodes in newest first orderPossibly taken @lchojnack claimed this 14 days ago. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 6 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 6 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bjarneo/cliamp#520 · 2 reactions ·
Maintainers usually reply within 6 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 6 days
Similar issues
-
fix(scan): validate and normalize output format in validate-contractPossibly taken @WKr1shna claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Won't Fix
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoft/TypeScript#65107 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
argoproj/argo-workflows#17397 ·
Maintainers usually reply within 1 day