fix(billing): Avoid 500s through uninitialized stripe client in dev environment #9276
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.
Important
Fix 500 errors in dev by returning null when Stripe client is uninitialized in
BillingUsageChart.tsx
andcloudBillingRouter.ts
.BillingUsageChart.tsx
, returnnull
ifusage.data
isnull
to avoid errors whenSTRIPE_SECRET_KEY
is not set in dev mode.cloudBillingRouter.ts
, log a warning and returnnull
ingetUsage
ifSTRIPE_SECRET_KEY
is not set andNEXT_PUBLIC_LANGFUSE_CLOUD_REGION
is "DEV".cloudBillingRouter.ts
whenSTRIPE_SECRET_KEY
is not set in dev environment.This description was created by
for 9d09f4e. You can customize this summary. It will automatically update as commits are pushed.