Files
supabase/apps/studio/components/interfaces/Database/Replication/ErroredTableDetails.tsx
oniani1 1f862ad9a4 fix(studio): encode state.reason in replication error support URL (#45185)
Closes #45184.

## Summary

`ErroredTableDetails.tsx` links the `no_retry` branch to the support
form with the Postgres error message (`state.reason`) dropped into the
`error` query parameter raw:

```tsx
href={`/support?projectRef=${projectRef}&category=dashboard_bug&subject=Database%20replication%20error&error=${state.reason}`}
```

Error strings routinely contain `&`, `#`, `=`, or newlines. Any of these
break the URL and leave the support form with a truncated or
misattributed value. Wrap with `encodeURIComponent`, matching the
pattern already used in `PipelineStatus.tsx:39-42` for the
replication-logs URL. Null-coalesce to `''` so the link is still
well-formed if `state.reason` is absent.

## Test plan

- [ ] Trigger a replication error whose message contains `&` / `#` /
newlines, open the support link, verify the full error text reaches the
form.
- [ ] Normal error string. URL is unchanged beyond standard URL
encoding.

Co-authored-by: Ali Waseem <waseema393@gmail.com>
2026-04-24 13:55:21 +00:00

79 lines
3.2 KiB
TypeScript

import { useParams } from 'common'
import { CriticalIcon } from 'ui'
import { isValidRetryPolicy } from './ReplicationPipelineStatus/ReplicationPipelineStatus.utils'
import { RetryCountdown } from './RetryCountdown'
import { InlineLink } from '@/components/ui/InlineLink'
import { ReplicationPipelineTableStatus } from '@/data/replication/pipeline-replication-status-query'
interface ErroredTableDetailsProps {
table: ReplicationPipelineTableStatus
}
export const ErroredTableDetails = ({ table }: ErroredTableDetailsProps) => {
const { ref: projectRef } = useParams()
const state = table.state as Extract<ReplicationPipelineTableStatus['state'], { name: 'error' }>
const tableName = table.table_name
const retryPolicy = state.retry_policy.policy
if (!isValidRetryPolicy(state.retry_policy)) {
return (
<div
role="region"
className="flex flex-col gap-y-3"
aria-label={`Error details for table ${tableName}`}
>
{state.solution && <div className="text-xs text-foreground-light">{state.solution}</div>}
<div className="text-xs text-foreground-lighter">Invalid retry policy configuration</div>
</div>
)
}
return (
<div role="region" aria-label={`Error details for table ${tableName}`}>
{retryPolicy === 'no_retry' ? (
<div className="flex flex-col gap-y-3">
<p className="text-xs text-foreground-lighter">
This error requires manual intervention from our{' '}
<InlineLink
className="text-foreground-lighter hover:text-foreground"
href={`/support?projectRef=${projectRef}&category=dashboard_bug&subject=Database%20replication%20error&error=${encodeURIComponent(state.reason ?? '')}`}
>
support
</InlineLink>
. Alternatively, you may also recreate the pipeline. Use the table actions menu on the
right to view the full error details.
</p>
</div>
) : retryPolicy === 'manual_retry' ? (
<div className="flex flex-col gap-y-3">
<div className="rounded-md border border-destructive-400 bg-destructive-100 px-3 py-3 space-y-2">
<div className="flex items-start gap-x-2">
<CriticalIcon />
<div className="flex-1 text-xs text-destructive-900">
<p className="font-semibold mb-1">Action required to continue replication</p>
<p className="text-foreground-light">
{state.solution}
{state.solution && !/[.!?]$/.test(state.solution.trim()) && '.'}
</p>
<p className="text-foreground-light mt-2">
Restart table replication from the table actions menu on the right. The pipeline
will restart automatically.
</p>
</div>
</div>
</div>
</div>
) : retryPolicy === 'timed_retry' ? (
<div className="flex flex-col text-foreground-lighter gap-y-3">
<p className="text-xs">
Replication will retry automatically. The pipeline will restart to apply the retry.
</p>
<RetryCountdown nextRetryTime={state.retry_policy.next_retry} />
</div>
) : null}
</div>
)
}