sfirke opened a new issue, #36910:
URL: https://github.com/apache/superset/issues/36910

   ### Bug description
   
   Upon upgrading to 6.0.0, I see a few instances of this at first startup:
   ```
   superset_worker_beat  | 2026-01-06 04:10:45,663:ERROR:superset.app:Failed to 
create app
   superset_worker_beat  | Traceback (most recent call last):
   superset_worker_beat  |   File 
"/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1910, 
in _execute_context
   superset_worker_beat  |     self.dialect.do_execute(
   superset_worker_beat  |   File 
"/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", line 
736, in do_execute
   superset_worker_beat  |     cursor.execute(statement, parameters)
   superset_worker_beat  | psycopg2.errors.UniqueViolation: duplicate key value 
violates unique constraint "pg_class_relname_nsp_index"
   superset_worker_beat  | DETAIL:  Key (relname, 
relnamespace)=(ab_group_id_seq, 2200) already exists.
   ```
   Superset then seems to work normally, though I haven't tried out the group 
functionality so it's possible this indicates a problem there.
   
   Doesn't seem to be causing me a problem but I wanted to open this issue in 
case others have this experience too. If it goes stale, we can convert to 
discussion.
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   6.0.0
   
   ### Python version
   
   I don't know
   
   ### Node version
   
   I don't know
   
   ### Browser
   
   Not applicable
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [x] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [x] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [x] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to