SQL Lab : getting a "Authentification required" when running query

I'm not sure this is a bug, but at least I need help troubleshooting. The error is as below

Pod's superset container's log
superset-7594948b84-r6mpw superset Triggering query_id: 43
superset-7594948b84-r6mpw superset 2023-01-18 11:24:41,138:INFO:superset.sqllab.command:Triggering query_id: 43
superset-7594948b84-r6mpw superset Query 43: Executing 1 statement(s)
superset-7594948b84-r6mpw superset 2023-01-18 11:24:41,182:INFO:superset.sql_lab:Query 43: Executing 1 statement(s)
superset-7594948b84-r6mpw superset Query 43: Set query to 'running'
superset-7594948b84-r6mpw superset 2023-01-18 11:24:41,183:INFO:superset.sql_lab:Query 43: Set query to 'running'
superset-7594948b84-r6mpw superset Query 43: Running statement 1 out of 1
superset-7594948b84-r6mpw superset 2023-01-18 11:24:41,238:INFO:superset.sql_lab:Query 43: Running statement 1 out of 1
superset-7594948b84-r6mpw superset Query 43: Storing results in results backend, key: 97ef1791-72ab-4f4d-8568-74736b0c42e3
superset-7594948b84-r6mpw superset 2023-01-18 11:24:41,290:INFO:superset.sql_lab:Query 43: Storing results in results backend, key: 97ef1791-72ab-4f4d-8568-74736b0c42e3
superset-7594948b84-r6mpw superset [SupersetError(message='Authentication required.', error_type=<SupersetErrorType.GENERIC_DB_ENGINE_ERROR: 'GENERIC_DB_ENGINE_ERROR'>, level=<ErrorLevel.ERROR: 'error'>, extra={'engine_name': 'PostgreSQL', 'issue_codes': [{'code': 1002, 'message': 'Issue 1002 - The database returned an unexpected error.'}]})]
superset-7594948b84-r6mpw superset Traceback (most recent call last):
superset-7594948b84-r6mpw superset   File "/app/superset/views/base.py", line 210, in wraps
superset-7594948b84-r6mpw superset     return f(self, *args, **kwargs)
superset-7594948b84-r6mpw superset   File "/app/superset/utils/log.py", line 245, in wrapper
superset-7594948b84-r6mpw superset     value = f(*args, **kwargs)
superset-7594948b84-r6mpw superset   File "/app/superset/views/core.py", line 2407, in sql_json
superset-7594948b84-r6mpw superset     command_result: CommandResult = command.run()
superset-7594948b84-r6mpw superset   File "/app/superset/sqllab/command.py", line 114, in run
superset-7594948b84-r6mpw superset     raise ex
superset-7594948b84-r6mpw superset   File "/app/superset/sqllab/command.py", line 98, in run
superset-7594948b84-r6mpw superset     status = self._run_sql_json_exec_from_scratch()
superset-7594948b84-r6mpw superset   File "/app/superset/sqllab/command.py", line 151, in _run_sql_json_exec_from_scratch
superset-7594948b84-r6mpw superset     raise ex
superset-7594948b84-r6mpw superset   File "/app/superset/sqllab/command.py", line 146, in _run_sql_json_exec_from_scratch
superset-7594948b84-r6mpw superset     return self._sql_json_executor.execute(
superset-7594948b84-r6mpw superset   File "/app/superset/sqllab/sql_json_executer.py", line 111, in execute
superset-7594948b84-r6mpw superset     raise SupersetErrorsException(
superset-7594948b84-r6mpw superset superset.exceptions.SupersetErrorsException: [SupersetError(message='Authentication required.', error_type=<SupersetErrorType.GENERIC_DB_ENGINE_ERROR: 'GENERIC_DB_ENGINE_ERROR'>, level=<ErrorLevel.ERROR: 'error'>, extra={'engine_name': 'PostgreSQL', 'issue_codes': [{'code': 1002, 'message': 'Issue 1002 - The database returned an unexpected error.'}]})]
superset-7594948b84-r6mpw superset 2023-01-18 11:24:41,331:WARNING:superset.views.base:[SupersetError(message='Authentication required.', error_type=<SupersetErrorType.GENERIC_DB_ENGINE_ERROR: 'GENERIC_DB_ENGINE_ERROR'>, level=<ErrorLevel.ERROR: 'error'>, extra={'engine_name': 'PostgreSQL', 'issue_codes': [{'code': 1002, 'message': 'Issue 1002 - The database returned an unexpected error.'}]})]
superset-7594948b84-r6mpw superset Traceback (most recent call last):
superset-7594948b84-r6mpw superset   File "/app/superset/views/base.py", line 210, in wraps
superset-7594948b84-r6mpw superset     return f(self, *args, **kwargs)
superset-7594948b84-r6mpw superset   File "/app/superset/utils/log.py", line 245, in wrapper
superset-7594948b84-r6mpw superset     value = f(*args, **kwargs)
superset-7594948b84-r6mpw superset   File "/app/superset/views/core.py", line 2407, in sql_json
superset-7594948b84-r6mpw superset     command_result: CommandResult = command.run()
superset-7594948b84-r6mpw superset   File "/app/superset/sqllab/command.py", line 114, in run
superset-7594948b84-r6mpw superset     raise ex
superset-7594948b84-r6mpw superset   File "/app/superset/sqllab/command.py", line 98, in run
superset-7594948b84-r6mpw superset     status = self._run_sql_json_exec_from_scratch()
superset-7594948b84-r6mpw superset   File "/app/superset/sqllab/command.py", line 151, in _run_sql_json_exec_from_scratch
superset-7594948b84-r6mpw superset     raise ex
superset-7594948b84-r6mpw superset   File "/app/superset/sqllab/command.py", line 146, in _run_sql_json_exec_from_scratch
superset-7594948b84-r6mpw superset     return self._sql_json_executor.execute(
superset-7594948b84-r6mpw superset   File "/app/superset/sqllab/sql_json_executer.py", line 111, in execute
superset-7594948b84-r6mpw superset     raise SupersetErrorsException(
superset-7594948b84-r6mpw superset superset.exceptions.SupersetErrorsException: [SupersetError(message='Authentication required.', error_type=<SupersetErrorType.GENERIC_DB_ENGINE_ERROR: 'GENERIC_DB_ENGINE_ERROR'>, level=<ErrorLevel.ERROR: 'error'>, extra={'engine_name': 'PostgreSQL', 'issue_codes': [{'code': 1002, 'message': 'Issue 1002 - The database returned an unexpected error.'}]})]
superset-7594948b84-r6mpw superset <IP_ADDRESS> - - [18/Jan/2023:11:24:41 +0000] "POST /superset/sql_json/ HTTP/1.1" 500 255 "https://superset.dev.data.frankfurt.gostudent.cloud/superset/sqllab/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"
superset-7594948b84-r6mpw superset <IP_ADDRESS> - - [18/Jan/2023:11:24:43 +0000] "PUT /tabstateview/3 HTTP/1.1" 200 1 "https://superset.dev.data.frankfurt.gostudent.cloud/superset/sqllab/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"
superset-7594948b84-r6mpw superset <IP_ADDRESS> - - [18/Jan/2023:11:24:43 +0000] "GET /superset/queries/1674040593720 HTTP/1.1" 200 657 "https://superset.dev.data.frankfurt.gostudent.cloud/superset/sqllab/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"

Yes, I made very very very sure I c/c'ed the proper password. I tried the said passwords running some python psycopg2 directly in the superset pod, it worked.
How to reproduce the bug

Configure Superset own database or a Redshift database in the "Databases" tab
Go to SQL Query
Exploring the database works (up to displaying the column of a given table like superset's ab_role
Running query get a "Authentication required"

Expected results
A successful query
Actual results
A red banner "Authentication required"
Screenshots
Pasted one above, not really helpful
Environment

browser type and version: latest stable Firefox 109.0 and Chromium 108.0.5359.124 snap (64 bits)

superset  version: tried with 2.0.0 & 2.0.1, official container as the helm chart get it

python version: Python 3.8.12

node.js version: command not found

any feature flags active: none

Superset own database is running on AWS RDS Aurora Postgresql serverless v2 with postgres engine, tried v13.6 & v14.5 versions

AWS Redshift up to date (they're dealing with the version themselves)

psycopg2, tried  v2.9.1, v2.9.4, v2.9.5

sqlalchemy-redshift 0.8.3, same error as "raw" psycopg above

I tried in both our dev & production environment (meaning VPC + Redshift + EKS where Superset is deployed)

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Charts are working
It used to work with a docker-compose based setup, and broke when migrated on Kubernetes. A data engineer workin with me told me he checked SQL Lab previously and it was ok. But I did reverted our (git based) settings, no luck.
I already spent a day understanding a first cryptic "bulk" error that was just me using a human friendly DNS CNAME instead of AWS technical hostname hence a SSL verification issue. But now I'm at a loss.
Can someone at least can tell me how to have more detailed logs ?

I encountered the same problem yesterday. I solved it by uncomment this line in the values.yaml. The authentication error had something to do with the Redis and the missing password for it.

I hope the solution above helped, and we could call this case closed based on that... but even if not I'm willing to close this as stale since it's been silent for so long, and we're trying to steer toward a more actionable Issues backlog. If people are still encountering this in current versions (currently 3.x) please re-open this issue, open a new Issue with updated context, or raise a PR to address the problem. Thanks!


Document how to schedule driftctl on kubernetes

A commonly reported use case for driftctl is to schedule an hourly cron job in Kubernetes.
Let's give an example in the documentation!
Source k8s documentation: https://kubernetes.io/docs/tasks/job/automated-tasks-with-cron-jobs/

Started working on this at https://github.com/cloudskiff/helm but may be we should create a page in the docs about k8s without helm, then later create a chart when driftctl will become more stable. Also a chart would not be compatible with all k8s versions since CronJob definition became stable only at v1.20. Let me known what do you think about it!


Action subfolder composite

Alternative approach to https://github.com/nf-core/setup-nextflow/pull/174 where I've moved the node action into a subdirectory.
This almost certainly isn't going to work, just taking a punt.

Testing here: https://github.com/ewels/nf-core-rnaseq/pull/36

ok, this has been an epic all-day rabbit hole.
Nearly there now I think. To do:

[ ] Strip out JasonEtco/build-and-tag-action from the publish.yml action and replicate the steps manually, using the composite action structure

I did this in the action-subfolder-composite-dist branch manually for reference

[ ] Probably eviscerate / delete example.yml workflow as I can't think how to get that to work on a relative path build
[ ] Try releasing on a fork of this repo for testing purposes
[ ] Release and hope it all works 🤞🏻

Test with the manual action-subfolder-composite-dist branch seems to be working here: https://github.com/ewels/nf-core-rnaseq/pull/36 (there's a CI failure from nf-core lint but this is unrelated).

ok, this has been an epic all-day rabbit hole.
Nearly there now I think. To do:
* [ ]  Strip out [`JasonEtco/build-and-tag-action`](https://github.com/JasonEtco/build-and-tag-action) from the `publish.yml` action and replicate the steps manually, using the composite action structure

:sweat_smile: Oh, yeah, the build and tag action has been broken for some time. It didn't like the change in output directory that Typescript brought. To test yourself, you will need to have a branch where you commit the dist directory (that mean going against gitignore, btw), and then you can run workflow tests. I just love JavaScript! :cry:

Closing as #177 already took care of this

#177 missed a lot of what I found and fixed in this PR 😢
Mostly: checking out the repo for the composite action. @mashehu now fighting the same problems and trying to hotfix.


Manual Deploy Script could use work

Investigation Needed
This follows PR #33 and its extensive list of known WTFs
Issue 1:  What's wrong with ExtractTextPlugin in webpack.production.config.js?

Original code:

test: /\.css$/,
use: ExtractTextPlugin.extract({
  fallback: 'style-loader',
  loader: 'css-loader',
  options: {
    includePaths: [
      path.resolve(__dirname, 'node_modules/zoo-grommet/dist'),
      path.resolve(__dirname, 'node_modules/zooniverse-react-components/lib')
    ]
  }
}),

PR 33 removed ExtractTextPlugin to dodge an error. Is there a better way to solve this?

Issue 2: 💀  Why does the built & deployed website ( https://classroom.zooniverse.org ) thinks it's on a staging/development environment?
Issue 3: Why does the script for npm run deploy-production have to be so unnecessarily long and duplicate the script for npm run build?
Issue 4: Is there a better alternative to publisssh?
Status
Open season for investigation. Only Issue 2 is considered a high priority item since it affects our end users.
Tagging @srallen into this; Sarah, I'd appreciate your insights into this when you're back.

ExtractTextPlugin is used to extract the CSS into a css file rather than the default webpack behavior which is to inject it into a style tag in the head of the HTML. There's likely something else wrong, perhaps the configuration rather than the plugin itself. We'll want the plugin to work, so the main.css file builds correctly.
If I get a chance, I'll take a look at your other questions.

Ok, ignore what I'm saying partly. The stylus configuration is handling the extraction, so it probably is correct to remove the plugin from the css loader configuration. I'll double check to confirm.

Closed by #36


Write a Swift program to convert seconds to minutes

Description
Write a Swift program to convert seconds to minutes
1 minute = 60 seconds
Input  : 300
Output : 5

How to contribute

Save the solution in ConvertSecondsToMinutes.swift file
Add ConvertSecondsToMinutes.swift file in convert-seconds-to-minutes folder

!assign


Porcupine SDK for macOS

Porcupine SDK for macOS.
I can find the iOS SDK, and it can realize my keyword wake-up function.
But I need use the SDK in macOS platform, So could you help me to provide an SDK that supports macOS for me to test it? Thanks a lot.

These SDKs can run on macOS: C, NodeJS, .NET, Java, and Python.