fix: initial api key load #1672
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kujtimiihoxha
requested review from
andreynering and
tauraamui
and removed request for
a team
caarlos0
approved these changes
Dec 19, 2025
caarlos0
reviewed
Dec 19, 2025
|
|
||
| switch providerID { | ||
| case string(catwalk.InferenceProviderAnthropic): | ||
| providerConfig.APIKey = fmt.Sprintf("Bearer %s", newToken.AccessToken) |
Member
There was a problem hiding this comment.
if we move this before the switch and remove it from line 559, we can close #1677
caarlos0
approved these changes
Dec 19, 2025
mengwong
pushed a commit
to mengwong/crush
that referenced
this pull request
Dec 24, 2025
M1n9X
pushed a commit
to M1n9X/crush
that referenced
this pull request
Jan 4, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was having issues where every time I loaded crush with an oauth provider it was refreshing the token on the first call.
The issue was caused by the API key not having the bearer prefix on initial load.
I refactored the implementation to not rely on the prefix but use the config.