br: restore safety check on dup upstream table id
Open
type/enhancement
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
## Enhancement
We noticed in one of envs there are two identical tables/views from the upstream, and restore panicked since we don't expect something like that. We probably can do a safety check on that and throw warnings instead of panicking
Contributor guide
Assessment
This issue has not been assessed yet.