[weird behaviour] Dashboards doesn't work as intended after a opensearch node fails in a cluster

I don't think this is a bug, but something I might being doing wrong or missing that I can't figure it out.
I have docker swarm with 5 nodes running Opensearch on each node. I have followed this guide: https://opensearch.org/docs/latest/install-and-configure/install-opensearch/docker/ . I also ran the securityadmin script with custom changes.
I have a healthy cluster, all nodes are working fine and I have a process indexing data at the rate of 15GB per day across multiple indices. All nodes are joined in the cluster because I checked it with _cat/nodes.
The problem begins when I shut down a node. At that point Dashboards stops working properly and I get kicked to the login page, and it fails to login every time. This is one of the errors Dashboards logs:
Failed to resolve user tenant: Error: Request Timeout after 30000ms | Failed to resolve user tenant: Error: Request Timeout after 30000ms | type=log Failed to resolve user tenant: Error: Request Timeout after 30000ms | Failed to resolve user tenant: Error: Request Timeout after 30000ms | type=log @timestamp=2023-12-27T11:16:18Z Failed to resolve user tenant: Error: Request Timeout after 30000ms | Failed to resolve user tenant: Error: Request Timeout after 30000ms | type=log Failed to resolve user tenant: Error: Request Timeout after 30000ms | Failed to resolve user tenant: Error: Request Timeout after 30000ms | type=log @timestamp=2023-12-27T11:16:18Z tags=error,plugins,securityDashboards Failed to resolve user tenant: Error: Request Timeout after 30000ms | Failed to resolve user tenant: Error: Request Timeout after 30000ms | type=log Failed to resolve user tenant: Error: Request Timeout after 30000ms | Failed to resolve user tenant: Error: Request Timeout after 30000ms | type=log @timestamp=2023-12-27T11:16:18Z Failed to resolve user tenant: Error: Request Timeout after 30000ms | Failed to resolve user tenant: Error: Request Timeout after 30000ms | type=log Failed to resolve user tenant: Error: Request Timeout after 30000ms | Failed to resolve user tenant: Error: Request Timeout after 30000ms | type=log @timestamp=2023-12-27T11:16:18Z tags=error,plugins,securityDashboards pid=1
Error: Request Timeout after 30000ms

at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | type=log Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | type=log @timestamp=2023-12-27T11:16:18Z Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | type=log Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | type=log @timestamp=2023-12-27T11:16:18Z tags=error,http,server,OpenSearchDashboards Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | type=log Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | type=log @timestamp=2023-12-27T11:16:18Z Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | type=log Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | type=log @timestamp=2023-12-27T11:16:18Z tags=error,http,server,OpenSearchDashboards pid=1

Failed to resolve user tenant: Error: Request Timeout after 30000ms | Failed to resolve user tenant: Error: Request Timeout after 30000ms | type=log Failed to resolve user tenant: Error: Request Timeout after 30000ms | Failed to resolve user tenant: Error: Request Timeout after 30000ms | type=log @timestamp=2023-12-27T11:16:18Z Failed to resolve user tenant: Error: Request Timeout after 30000ms | Failed to resolve user tenant: Error: Request Timeout after 30000ms | type=log Failed to resolve user tenant: Error: Request Timeout after 30000ms | Failed to resolve user tenant: Error: Request Timeout after 30000ms | type=log @timestamp=2023-12-27T11:16:18Z tags=error,plugins,securityDashboards Failed to resolve user tenant: Error: Request Timeout after 30000ms | Failed to resolve user tenant: Error: Request Timeout after 30000ms | type=log Failed to resolve user tenant: Error: Request Timeout after 30000ms | Failed to resolve user tenant: Error: Request Timeout after 30000ms | type=log @timestamp=2023-12-27T11:16:18Z Failed to resolve user tenant: Error: Request Timeout after 30000ms | Failed to resolve user tenant: Error: Request Timeout after 30000ms | type=log Failed to resolve user tenant: Error: Request Timeout after 30000ms | Failed to resolve user tenant: Error: Request Timeout after 30000ms | type=log @timestamp=2023-12-27T11:16:18Z tags=error,plugins,securityDashboards pid=1
Error: Request Timeout after 30000ms

at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | type=log Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | type=log @timestamp=2023-12-27T11:16:18Z Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | type=log Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | type=log @timestamp=2023-12-27T11:16:18Z tags=error,http,server,OpenSearchDashboards Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | type=log Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | type=log @timestamp=2023-12-27T11:16:18Z Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | type=log Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | Error: Request Timeout after 30000ms
at SecurityClient.dashboardsinfo (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/backend/opensearch_security_client.ts:130:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at BasicAuthentication.resolveTenant (/usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:249:28)
at /usr/share/opensearch-dashboards/plugins/securityDashboards/server/auth/types/authentication_type.ts:172:24
at Object.interceptAuth [as authenticate] (/usr/share/opensearch-dashboards/src/core/server/http/lifecycle/auth.js:133:22)
at exports.Manager.execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
at module.exports.internals.Auth._authenticate (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/auth.js:273:30)
at Request._lifecycle (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:371:32)
at Request._execute (/usr/share/opensearch-dashboards/node_modules/@hapi/hapi/lib/request.js:281:9) | type=log @timestamp=2023-12-27T11:16:18Z tags=error,http,server,OpenSearchDashboards pid=1
ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error @timestamp=2023-12-27T11:28:02Z ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error @timestamp=2023-12-27T11:28:02Z tags= ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error @timestamp=2023-12-27T11:28:02Z ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error @timestamp=2023-12-27T11:28:02Z tags= pid=1 ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error @timestamp=2023-12-27T11:28:02Z ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error @timestamp=2023-12-27T11:28:02Z tags= ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error @timestamp=2023-12-27T11:28:02Z ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error @timestamp=2023-12-27T11:28:02Z tags= pid=1 error=[object Object] ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error @timestamp=2023-12-27T11:28:02Z ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error @timestamp=2023-12-27T11:28:02Z tags= ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error @timestamp=2023-12-27T11:28:02Z ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error @timestamp=2023-12-27T11:28:02Z tags= pid=1 ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error @timestamp=2023-12-27T11:28:02Z ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error @timestamp=2023-12-27T11:28:02Z tags= ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error @timestamp=2023-12-27T11:28:02Z ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error ERR ERR ERR ERR Internal Server Error | ERR ERR ERR ERR Internal Server Error | type=error @timestamp=2023-12-27T11:28:02Z tags= pid=1 error=[object Object] url=http://XXXXXXXXX/app/home`

The cluster entered in yellow state. I checked through the CLI and waited untill it changed back to green. Then I tried to login again and it still doesn't let me. But I can issue commands through the CLI with no problem and I confirmed that the documents are being inserted into Opensearch.  So I guess the problem is in the Dasboard?
Opensaerch and Opensearch-Dashboards versions:
2.11.1 (I upgraded to the last version because I thought it might be the version)
System:
Docker Swarm across 5 nodes
Client: Docker Engine - Community
Version:           24.0.7
API version:       1.43
Go version:        go1.20.10
Git commit:        afdd53b
Built:             Thu Oct 26 09:07:41 2023
OS/Arch:           linux/amd64
Context:           default
Server: Docker Engine - Community
Engine:
Version:          24.0.7
API version:      1.43 (minimum version 1.12)
Go version:       go1.20.10
Git commit:       311b9ff
Built:            Thu Oct 26 09:07:41 2023
OS/Arch:          linux/amd64
Experimental:     false
containerd:
Version:          1.6.25
GitCommit:        d8f198a4ed8892c764191ef7b3b06d8a2eeb5c7f
runc:
Version:          1.1.10
GitCommit:        v1.1.10-0-g18a0cb0
docker-init:
Version:          0.19.0
GitCommit:        de40ad0
Hosting Operating System:
Ubuntu 22.04.3 LTS with EPYC cpu
Docker Stack config
Every node has the following environment:
  OPENSEARCH_JAVA_OPTS: "-Xms4096m -Xmx4096m" # minimum and maximum Java heap size, recommend setting both to 50% of system RAM
  node.name: opensearch-node05
  discovery.seed_hosts: opensearch-node01,opensearch-node02,opensearch-node03,opensearch-node04,opensearch-node05
  cluster.initial_master_nodes: opensearch-node01,opensearch-node02,opensearch-node03,opensearch-node04,opensearch-node05
  plugins.security.ssl.transport.pemcert_filepath: certs/opensearch-nodeXX/nodeXX.pem
  plugins.security.ssl.transport.pemkey_filepath: certs/opensearch-nodeXX/nodeXX-key.pem
  plugins.security.ssl.http.pemcert_filepath: certs/opensearch-nodeXX/nodeXX.pem
  plugins.security.ssl.http.pemkey_filepath: certs/opensearch-nodeXX/nodeXX-key.pem
  DISABLE_INSTALL_DEMO_CONFIG: "true"
  bootstrap.memory_lock: "true" # along with the memlock settings below, disables swapping

The XX are replaced by the corresponding node number. And all have the same opensearch.yml volume:
/VVVVVVVVVVVVVVVVVVV/opensearch/config/opensearch.yml:/usr/share/opensearch/config/opensearch.yml
opensaerch.yml
network.bind_host: "<IP_ADDRESS>"
network.host: "<IP_ADDRESS>"
plugins.security.ssl.transport.pemtrustedcas_filepath: certs/ca/root-ca.pem
plugins.security.ssl.http.pemtrustedcas_filepath: certs/ca/root-ca.pem
plugins.security.ssl.transport.enforce_hostname_verification: false
plugins.security.ssl.http.enabled: true
plugins.security.allow_default_init_securityindex: true
plugins.security.authcz.admin_dn:
    - CN=AAAAAAAAA-ADMIN,OU=AAAAAAAAA,O=AAAAAAAAA,L=AAAAAAAAA,ST=AAAAAAAAA,C=AAAAAAAAA
plugins.security.nodes_dn:
    - CN=opensearch-node01,OU=AAAAAAAAA,O=AAAAAAAAA,L=AAAAAAAAA,ST=AAAAAAAAA,C=AAAAAAAAA
    - CN=opensearch-node02,OU=AAAAAAAAA,O=AAAAAAAAA,L=AAAAAAAAA,ST=AAAAAAAAA,C=AAAAAAAAA
    - CN=opensearch-node03,OU=AAAAAAAAA,O=AAAAAAAAA,L=AAAAAAAAA,ST=AAAAAAAAA,C=AAAAAAAAA
    - CN=opensearch-node04,OU=AAAAAAAAA,O=AAAAAAAAA,L=AAAAAAAAA,ST=AAAAAAAAA,C=AAAAAAAAA
    - CN=opensearch-node05,OU=AAAAAAAAA,O=AAAAAAAAA,L=AAAAAAAAA,ST=AAAAAAAAA,C=AAAAAAAAA
plugins.security.audit.type: internal_opensearch
plugins.security.enable_snapshot_restore_privilege: true
plugins.security.check_snapshot_restore_write_privileges: true
plugins.security.restapi.roles_enabled: ["all_access", "security_rest_api_access"]
cluster.routing.allocation.disk.threshold_enabled: false
opendistro_security.audit.config.disabled_rest_categories: NONE
opendistro_security.audit.config.disabled_transport_categories: NONE

Environment of Opensearch-Dashboards:
  OPENSEARCH_HOSTS: '["https://opensearch-node01:9200","https://opensearch-node02:9200","https://opensearch-node03:9200","https://opensearch-node04:9200","https://opensearch-node05:9200"]' # must be a string with no spaces when specified as an environment variable
  DISABLE_INSTALL_DEMO_CONFIG: "true"

A volume also replaces the opensearch_dashboards.yml:
opensearch.ssl.verificationMode: none
opensearch.username: kibanaserver
opensearch.password: XXXXXXXXXXXXXXXXXXXXXXXXXX
opensearch.requestHeadersWhitelist: [authorization, securitytenant]
opensearch_security.multitenancy.enabled: true
opensearch_security.multitenancy.tenants.enable_global: false
opensearch_security.multitenancy.tenants.enable_private: false
opensearch_security.multitenancy.tenants.preferred: [Private, Global]
opensearch_security.readonly_mode.roles: [kibana_read_only]
opensearch_security.cookie.secure: false
server.host: '<IP_ADDRESS>'

Here's the config.yml of Opensaerch-Security:
_meta:
  type: "config"
  config_version: 2

config:
  dynamic:
    kibana:
      multitenancy_enabled: true
      private_tenant_enabled: true
      default_tenant: Global
      server_username: kibanaserver
      index: '.kibana'
    do_not_fail_on_forbidden: false
    http:
      anonymous_auth_enabled: false
      xff:
        enabled: false
    authc:
      basic_auth_internal:
        http_enabled: true
        transport_enabled: true
        order: 1
        http_authenticator:
          type: basic
          challenge: true
        authentication_backend:
          type: internal

STEPS TO REPLICATE
After the cluster is configured and functioning and Dashboards is also functioning well, just stop one opensearch node and Dashboards stops working as intended.

The problem begins when I shut down a node. At that point Dashboards stops working properly and I get kicked to the login page, and it fails to login every time.

@gpedras This sounds like more of a support request, for the security plugin we steer folks to https://forum.opensearch.org/ so the answers are more searchable from web browsers, I'm going to close this issue.  Could you create a thread about this issue there and post a link on this closed issue?

Sure thing


Fix text completions

We should start with this: https://github.com/atom/atom-languageclient/pull/254

When I looked into copying that PR to this repo it looks like most of the code has already been updated. I'm not sure how to rebase that PR onto the changes that have happened since it was opened.

A similar bug was reported downstream in the ide-python library.
https://github.com/atom-community/ide-python/issues/251
I was able to isolate it to the change here made in #100. When I revert the change on my local copy of ide-python's dependencies, it fixes the issue. So there might be some interaction between the two issues.

A similar bug was reported downstream in the ide-python library.
https://github.com/atom-community/ide-python/issues/251
I was able to isolate it to the change here made in #100. When I revert the change on my local copy of ide-python's dependencies, it fixes the issue. So there might be some interaction between the two issues.

A similar bug was reported downstream in the ide-python library.
atom-community/ide-python#251
I was able to isolate it to the change here made in #100. When I revert the change on my local copy of ide-python's dependencies, it fixes the issue. So there might be some interaction between the two issues.

Thanks for the report. I transferred the issue.

A similar bug was reported downstream in the ide-python library.
atom-community/ide-python#251
I was able to isolate it to the change here made in #100. When I revert the change on my local copy of ide-python's dependencies, it fixes the issue. So there might be some interaction between the two issues.

Thanks for the report. I transferred the issue.

Sometimes when I press TAB nothing gets written by autocomplete.

Sometimes when I press TAB nothing gets written by autocomplete.

Sometimes when I press TAB nothing gets written by autocomplete.

That seems like an issue for the autocomplete package.

Sometimes when I press TAB nothing gets written by autocomplete.

That seems like an issue for the autocomplete package.

I'm pretty sure test completions are fixed in v1.0.6
If there are still issues create another issue with specific details.

I'm pretty sure test completions are fixed in v1.0.6
If there are still issues create another issue with specific details.


Fixed invalid error codes when sending request to a unavailable API endpoint with a binary file with .yaml extension

Fix https://github.com/wso2/api-manager/issues/2267

This is a duplicate PR of https://github.com/wso2/product-apim/pull/13306


Fix logging baker v3

Codecov Report

Merging #266 into master will decrease coverage by 8.54%.
The diff coverage is 82.81%.

@@            Coverage Diff             @@
##           master     #266      +/-   ##
==========================================
- Coverage   80.09%   71.54%   -8.55%
==========================================
  Files         127      148      +21
  Lines        3310     3648     +338
  Branches      137      143       +6
==========================================
- Hits         2651     2610      -41
- Misses        659     1038     +379

Impacted Files
Coverage Δ

...untime/akka/actor/process_index/ProcessIndex.scala
82.02% <66.66%> (+0.3%)
:arrow_up:

...actor/process_instance/ProcessInstanceLogger.scala
84.5% <80%> (-7.95%)
:arrow_down:

.../akka/actor/process_instance/ProcessInstance.scala
85.81% <94.44%> (+0.09%)
:arrow_up:

...ing/baker/runtime/scaladsl/RecipeInformation.scala
0% <0%> (-100%)
:arrow_down:

...aker/runtime/scaladsl/RecipeInstanceMetadata.scala
0% <0%> (-100%)
:arrow_down:

...rotomappings/SensoryEventStatusMappingHelper.scala
0% <0%> (-92.31%)
:arrow_down:

...tion/protomappings/SensoryEventResultMapping.scala
0% <0%> (-90.91%)
:arrow_down:

...la/com/ing/baker/runtime/scaladsl/BakerEvent.scala
0% <0%> (-71.43%)
:arrow_down:

...ing/baker/runtime/javadsl/IngredientInstance.scala
0% <0%> (-66.67%)
:arrow_down:

.../ing/baker/runtime/javadsl/RecipeInformation.scala
0% <0%> (-60%)
:arrow_down:

... and 42 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a7cad84...6cbaccf. Read the comment docs.


feat: Improve performance of add dataset page

SUMMARY

Create new celery task that warms up tables in a database schema, takes database id & schema name as args
Use AntdSelect select in table selection input, which is able to handle up to 100,000 options without impacting the performance of the page.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Before

After

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #21 (c2a4251) into pinterest-release-2.1 (e3a8a6e) will decrease coverage by 0.03%.
The diff coverage is 8.00%.

@@                    Coverage Diff                    @@
##           pinterest-release-2.1      #21      +/-   ##
=========================================================
- Coverage                  56.35%   56.32%   -0.03%
=========================================================
  Files                       1883     1884       +1
  Lines                      72565    72560       -5
  Branches                    7887     7879       -8
=========================================================
- Hits                       40892    40873      -19
- Misses                     29651    29668      +17
+ Partials                    2022     2019       -3

Flag
Coverage Δ

presto
52.71% <8.00%> (-0.04%)
:arrow_down:

python
58.94% <8.00%> (-0.04%)
:arrow_down:

unit
52.46% <0.00%> (-0.04%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...s/CRUD/data/dataset/AddDataset/LeftPanel/index.tsx
80.70% <ø> (+2.13%)
:arrow_up:

superset/tasks/celery_app.py
0.00% <0.00%> (ø)

superset/tasks/database.py
0.00% <0.00%> (ø)

superset/tasks/cache.py
30.88% <66.66%> (+0.51%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


extract REGEX_PLACEHOLDER

closes https://github.com/staabm/phpstan-dba/issues/109

will fix in https://github.com/staabm/phpstan-dba/pull/111


New JK-BMS JK-B2A8S30P not yet supported?

Describe the problem
New JK-BMS JK-B2A8S30P seems not recognised with serial battery. Tried several versions 1.2 and beta 1.3 but no joy.
On the same Cerbo GW I have 2x B2A8S20P with no issue.
the new B2A8S30P is the 300A version for 4S and 8S. It is running the same FW version, according to the iOS app.
From the iOS App, I see that the Device ID is by default = 1, and can't be change to 0 on the legacy B2A8S20P, this is set by default to 0
Also I see that I have few choices for the protocol on this new B2A8S30P. I tried few options, but no joy.
Any hint? I'm not sure providing the USB log will be relevant as I don't see anything interesting appart that trying to recognise the BMS 3x times and then declare there is no BMS.
Also I noticed that it seems to hang the BMS part after some period because I don't see anymore the red led of the BMS blinking, and it becomes impossible to switch off the BMS with the power switch, unless I disconnect the USB interface.
Driver version
v1.2 & 1.3
Venus OS device type
Cerbo GX
Venus OS version
v3.30
BMS type
JKBMS / Heltec BMS
Cell count
4
Battery count
1
Connection type
Serial USB adapter to RS485
Config file
[DEFAULT]

; If you want to add custom values/settings, then check the values/settings you want to change in "config.default.ini"
; and insert them below to persist future driver updates.

; Example (remove the semicolon ";" to uncomment and activate the value/setting):

; --------- Battery Current limits ---------
MAX_BATTERY_CHARGE_CURRENT = 200.0
MAX_BATTERY_DISCHARGE_CURRENT = 200.0

Relevant log output
@400000006629508d30cb9d84 INFO:SerialBattery:-- Testing BMS: 3 of 3 rounds
@400000006629508d30d6ad8c INFO:SerialBattery:Testing Jkbms
@400000006629508e06d74a14 ERROR:SerialBattery:>>> ERROR: No reply - returning
@400000006629508e25f39574 ERROR:SerialBattery:ERROR >>> No battery connection at /dev/ttyUSB0
@40000000662950a03916d47c INFO:SerialBattery:
@40000000662950a03923385c INFO:SerialBattery:Starting dbus-serialbattery
@40000000662950a0393bfc34 INFO:SerialBattery:dbus-serialbattery v1.0.20231125beta
@40000000662950d10e515244 *** CCGX booted (0) ***

Any other information that may be helpful
No response

Tomorrow, I will try to connect this BMS via bluetooth. I believe it should work...

Ask your reseller for the protocol documentation, this should help me to get it fixed.

This is the RS485 protocol for the new JK JK-PB1A16S10P  JK-PB1A16S15P  JK-PB2A16S20P etc
Jikong.BMS.RS485.Modbus.universal.protocol.V1.0.pdf

I made the request with the vendor to receive updated protocol for this model.
I tried a second BMS unit, and this is the same. I also tried to change the UART1 protocol (by default it was "000 - 4G-SPS Remote module communication") with "001 - JKBMS RS485 Modbus v1.0".
There is also choice of:
"002 - NIU U SERIES"
"003 - China tower shared battery cabin..."
"006 - Growatt_BMS_RS485_Protocol"
but no luck still the same results.
See the logs with version 1.2.xxx and 1.3.xx:
@40000000662d83c53567e1f4 INFO:SerialBattery:Starting dbus-serialbattery @40000000662d83c53593c454 INFO:SerialBattery:Venus OS v3.40~8 @40000000662d83c535a62b44 INFO:SerialBattery:dbus-serialbattery v1.2.20240408 @40000000662d83d536afc374 INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds @40000000662d83d536baa884 INFO:SerialBattery:Testing Jkbms @40000000662d83d60c7fab3c ERROR:SerialBattery:>>> ERROR: No reply - returning @40000000662d83d62a8ca1ac INFO:SerialBattery:-- Testing BMS: 2 of 3 rounds @40000000662d83d62a971574 INFO:SerialBattery:Testing Jkbms @40000000662d83d70037debc ERROR:SerialBattery:>>> ERROR: No reply - returning @40000000662d83d71e4b8fd4 INFO:SerialBattery:-- Testing BMS: 3 of 3 rounds @40000000662d83d71e588824 INFO:SerialBattery:Testing Jkbms @40000000662d83d72f685c34 ERROR:SerialBattery:>>> ERROR: No reply - returning @40000000662d83d811ec95bc ERROR:SerialBattery:ERROR >>> No battery connection at /dev/ttyUSB1 @40000000662d83e709aebca4 INFO:SerialBattery: @40000000662d83e709bb999c INFO:SerialBattery:Starting dbus-serialbattery @40000000662d83e709ddd354 INFO:SerialBattery:Venus OS v3.40~8 @40000000662d83e709e78b9c INFO:SerialBattery:dbus-serialbattery v1.3.20240427dev @40000000662d83f70aef761c INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds @40000000662d83f70afec414 INFO:SerialBattery:Testing Jkbms @40000000662d83f71cc906b4 ERROR:SerialBattery:>>> ERROR: No reply - returning @40000000662d83f73af2dbc4 INFO:SerialBattery:-- Testing BMS: 2 of 3 rounds @40000000662d83f73af2feec INFO:SerialBattery:Testing Jkbms @40000000662d83f813fa47dc ERROR:SerialBattery:>>> ERROR: No reply - returning @40000000662d83f832173054 INFO:SerialBattery:-- Testing BMS: 3 of 3 rounds @40000000662d83f832231f04 INFO:SerialBattery:Testing Jkbms @40000000662d83f909104a24 ERROR:SerialBattery:>>> ERROR: No reply - returning @40000000662d83f926fac85c ERROR:SerialBattery:ERROR >>> No battery connection at /dev/ttyUSB1 @40000000662d83fb14afff64 INFO:SerialBattery: @40000000662d83fb14ba638c INFO:SerialBattery:Starting dbus-serialbattery @40000000662d83fb14d8c8cc INFO:SerialBattery:Venus OS v3.40~8 @40000000662d83fb14e301fc INFO:SerialBattery:dbus-serialbattery v1.3.20240427dev @40000000662d840b15e2f56c INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds @40000000662d840b15f11e6c INFO:SerialBattery:Testing Jkbms @40000000662d840b27bd3d9c ERROR:SerialBattery:>>> ERROR: No reply - returning @40000000662d840c0a6ea58c INFO:SerialBattery:-- Testing BMS: 2 of 3 rounds @40000000662d840c0a7cc2d4 INFO:SerialBattery:Testing Jkbms @40000000662d840c1c34ae24 ERROR:SerialBattery:>>> ERROR: No reply - returning @40000000662d840c3a4e46f4 INFO:SerialBattery:-- Testing BMS: 3 of 3 rounds @40000000662d840c3a5904f4 INFO:SerialBattery:Testing Jkbms @40000000662d840d100d0434 ERROR:SerialBattery:>>> ERROR: No reply - returning @40000000662d840d2e2a5624 ERROR:SerialBattery:ERROR >>> No battery connection at /dev/ttyUSB1

@kommando828 I looked at your doc, and effectively, I have this protocol available to be set on the UART1, with the IOS app.
@mr-manuel I suppose this driver has not yet been implemented in dbus-serialbattery ?

JK Pinouts are reversed to normal, maybe try reversing A and B, reversing Can_L and Can_H worked for me for  JK-PB2A16S20P direct BMS Canbus to inverter.

The BMS is not this form factor and the RD485 adapter (provided by JK) is connecting on the GPS port.
according to Google translate A is yellow and B is white. I also used the same adapter from the working B2A8S20P, and still can't get the BMS recognised.
I'm afraid the GPS port is not anymore supporting the same protocol as the B2A8S20P.
I have my test lab setup, I will try to attach the 485 interface to a computer and see if we can't get something out of this new 300A BMS...

Here is what it looks like:

Assuming the two left most connectors are to the temperature sensors, have you tried connecting to the CAN/RS485 port to the right of the GPS. Just making odd suggestions as the documentation of JK is so bad you have to experiment to get anywhere. If this CAN/RS485 port is the same as on the JK-PB2A then you only need to RS485 USB on the PC and not the JK RS485 box as it is already RS485 and not TTL.

I tried with Windows app JK-BMS-MONITOR 2.7.0, BMS configured as Dev Address 1 and UART protocol 001 - JKBMS RS485 Modbus v1.0
No communication :-(
I'm talking with JK BMS vendor, but I'm afraid it will go nowhere...

You would assume that the very latest released BMS would follow the other most recent releases, but in JK world it seems every release they start from the beginning and change everything. Feature wise they are the best BMS but support wise they leave a lot to be desired. Seems the only customer they listen to is Andy at Off Grid Garage.

@kommando828 good advice, I will try to connect to the RS485 connector, next to the GPS one.
Does some one know what is the name of this connector, so I can source it?

Your photo is private so I can't blow the photo up to see the connector. Could you post a closeup of the connector, the various sellers listings are silent on what type it is or any closeup's.

here you are:

Yes now that I am awake ;)
What a weird connector.

Looks like a JST GH type
https://www.mattmillman.com/info/crimpconnectors/common-jst-connector-types/

Looking at the picture, I think the SMD drivers are not soldered. and I think the option of Can or 485 is a choice of with one they solder.
Game over!

On the top left of the picture, I think this is a MAX 485 that is supposed to fit there.
If I find the time I will try to fit one here and check if I get some life over 485 port....

If a MAX485 should go there then you should find TTL signals on the correct pins that feed the signal to the MAX485.

JK gave me access to the following Google drive: https://drive.google.com/drive/folders/1RZ7IP5g2uS3PzJo2RcMnLJw6343AhlqI?spm=a2g0s.imconversation.0.0.7ddc3e5fEeTB9L
I'm attaching the spec sheet for the JK-B2A8S-10P-20P-30P series. Both original, and a tentative of English translation. If you guys have better tool for chinese->english, feel free to share.
JK-B2A8S-10P-20P-30P-EN-V1.0.pdf
Uploading JK-B2A8S-10P-20P-30P主动均衡保护板使用说明书-V1.0.pdf…

My discussion with the store is going in a dead loop.
I'm afraid the conclusion is that the GPS port is deactivated, despite they are selling their GPS->RS485 adapter as a bundle with the BMS...

Can you write me on Discord? Maybe I have an idea now. Did you already measured, if you get some signals from the GPS port? It already happend that there where some broken GPS ports out there.

Hi Louis, not sure how I can reach you on Discord, but I can tell you that I don't believe this is because my GPS port is broken, because I have 2x units behaving exactly the same.
I'm still discussing with JK BMS store, and according to them, they have identified that the GPS to RS485 adapter thet was sent with the units were not the required low voltage models.
I have serious doubt about this as the 200A version of the same BMS works perfectly with the same adapters. Anyways they are sending 2x new Low voltage adapters and will give a try, who knows, may be something changed on their GPS port....

Hi Louis, not sure how I can reach you on Discord, but I can tell you that I don't believe this is because my GPS port is broken, because I have 2x units behaving exactly the same. I'm still discussing with JK BMS store, and according to them, they have identified that the GPS to RS485 adapter thet was sent with the units were not the required low voltage models. I have serious doubt about this as the 200A version of the same BMS works perfectly with the same adapters. Anyways they are sending 2x new Low voltage adapters and will give a try, who knows, may be something changed on their GPS port....

JKBMS has two different serial Devices. you need to be shure to have the correct one, belive me.

OK after 2x months of fight with JKBMS, they have spotted that the RS485 adapters they sent bundled with the BMS were the wrong ones, and I'm happy to report here that latest v1.3 dbus-serialbattery works like a charm with the new 300A JK-B2A8S30P. IT was not so easy to spot the root cause because I tried the RS485 adapters that came with 200A version (JK-B2A8S30P) and it didn't worked. So most probably, the electronic must be more sensible to this low voltage RS485 requirement....


AtlasEngine: Stop resizing buffers on scroll

This regressed in ad2358d.
We're interested in the size of the viewport only, but it can shift up/down
during scrolling. In these situations we shouldn't resize our buffers of course.
Validation Steps Performed

Scroll
Not setting ApiInvalidations::Size ✅

Turns out ad2358d isn't in 1.14 (I think?) so it doesn't need to be backported.

I think that commit is in 1.14. We should tag this one up.


i18n Japanese date format cannot be filtered

Describe the bug
It seems that i18n use the long format, which is "%Y年%m月%d日(%a)", to show in the table list. When filtering, it deliver by this format and cannot search from database
  config.model "model_name" do
    configure :date_field_name do
      strftime_format "%Y-%m-%d"
    end
  end

I do this to let filter work, but it will display the column in this format too.
Reproduction steps
Use datepicker to pick a date on date field to filter, but not working.
Expected behavior
Show the list date field column in i18n long format, but deliver by iso8601 when filtering will be better.

It is not supposed to perform like this after https://github.com/railsadminteam/rails_admin/commit/01e8d5fc8ec94e68af6fdbd80759a751cd83f74a. So my guess is that you have old RailsAdmin assets somewhere in your app, via vendorizatiion or something.
Please check it, and if the issue still happens please let me know.


Add mode for pretrained phi network

I did some preliminary testing, and I think it works. I pushed to my repo but I'm holding off pushing to yours because I think a joint code review when we both have fresh eyes wouldn't be a bad idea.

Let's both look at this tomorrow before merging


Wrong line wrap in csv

If the description string (json) contains \r\n than the csv format is broken.
Quick fix:
open csv in Notepad++
replace all \r\n with nothing (in Advanced Mode)
save the file
now it is interpreted correctly by excel (if you want to use excel)

Line wraps within a Cell are not possible in CSV-Files by Excel.


feat(MeasureTheory): define contents on semi-rings of sets

Define additive contents and prove their basic properties on (semi)-rings of sets.
Define rings of sets.

Co-authored-by: Peter Pfaffelhuber<EMAIL_ADDRESS>Part of the formalization of the Kolmogorov Extension Theorem.

bors r+
Thanks!

bors r+


GI broken/much too bright

Godot version:
Godot 3.1 master, commit 16e6738
OS/device including version:
Arch Linux, Linux 4.20.11, AMD RTX 580 with Mesa 18.3.4
Issue description:
As of one of the latest commits, GIProbes in Godot seem to be broken.
Wherever used, they produce very bright, unrealistic results even at default settings. The propagation slider doesn't have any effect at all

Steps to reproduce:
set up any scene using a GI Probe
Minimal reproduction project:

Can anyone bisect this?

While I don't know how to bisect, since I do build Godot quite often, I have just tested some older builds and the bug didn't occur after commit 8b231b9, but was already present after 5f5f338. So it must have been introduced somewhere in between. Don't know if this helps.

This commit here made a couple of slight changes to the GI code (in a bid to fix some warnings).
https://github.com/godotengine/godot/pull/26099
Apparently, the use of clamp rather than max is needed to make sure they work properly.

Unfortunately, this didn't fix it for me :(

Just tested too, the commit that made changes to the GI code should be reverted.
Here's a quick and dirty example project with a 3D scene and a GI probe, the builds a few days ago and ones made just now show very different results.
GITest.zip

There are more issues, looks like @marxin misinterpreted what CLAMP does (and I failed spotting the regression). Will push another fix.

There are more issues, looks like @marxin misinterpreted what CLAMP does (and I failed spotting the regression). Will push another fix.

Ooops. Sorry for that and thanks for the fix.


email.php frontend

Email.php front end done!
have a look and give your comments

I have merged the sam_forget_password branch  which is front end for email.php


document some limitations on repo topics

Why:
There are some limitations on repository topics, and without more documentation, the only way to know about them is trial-and-error.
What's being changed (if available, include any code snippets, screenshots, or gifs):

Added a few bullet points describing the list of limitations on topics that I have found.
Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

@janiceilene Thanks for the review! I have moved the new text to the end of the "About topics" section, and please let me know if this needs any more tweaks.

This looks great @hopkinsth! Thank you so much ⚡ We're frozen for a bit while folks are on holiday, but I'll get this added to the list of things to merge once we're thawed ❄


Add conditional to use file.path as opts.file

Relates to #324

Superseded by #353

Thanks for your contribution @lucasconstantino


NixOS 23.11

This switches nixpkgs from the nixos-23.05 branch to nixos-23.11.
Several new things:

NixOS 23.11 has the quartoMinimal packages, which is way smaller, because it does not depend on Java, Python, R. With dependencies, its 434MiB vs 2.7GiB

NixOS uses _FORTIFY_SOURCE=3 by default for extra buffer checks, but this caused an issue with epics-base (see commit)

Some upstream Kafka options changed, and also now support Kraft mode. We use that for the integration test, and as a recommended way in the documentation. This removes the need for Zookeeper, and so frees port 8080.

cc @Rider128

NixOS uses _FORTIFY_SOURCE=3 by default for extra buffer checks, but this caused an issue with epics-base (see commit)

Is this issue known about upstream? Is it a false positive added by the compiler or a real issue that just doesn't happen to give unwanted results?

@Synthetica9 FYI the _FORTIFY_SOURCE=3 issue is being tracked in https://github.com/epics-base/epics-base/issues/514 and hopefully fixed in https://github.com/epics-base/epics-base/pull/517


Add the activeParticipats event to the notification service RN+Android

Add following events to the notification service:

active participants

Only RN and Android work. iOS to be done in separate ticket.

Please add following events also

participantJoined
participantLeft

@mohsindlb, we have planed this already under a different ticket. Please see: https://github.com/DolbyIO/comms-sdk-react-native/issues/75

Implemented in 3.8.0 Beta 1
@asadumair iOS is implemented as well, but as per first message, it has been tracked in a different ticket.


VMCreate: Update key gen message

Description
Outline the issue here:
Need to update keygen message to remove cloud shell reference. Opening issue here per thread with Mayuri/Yugang.
New string:
SSH key files ‘id_rsa.pub’ and ‘id_rsa’ have been generated under ~/.ssh to allow SSH access to the VM. If using machines without permanent storage, back up your keys to a safe location.

Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here:
CLI Version: What version of the CLI and modules are installed? (Use az --version)
Answer here:
OS Version: What OS and version are you using?
Answer here:
Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here:

approved to @yugangw-msft for upcoming sprint.


fix: count to and from separately for wallet balance

Codecov Report
Patch and project coverage have no change.

Comparison is base (9a09fe7) 84.53% compared to head (cabbaf1) 84.53%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #424   +/-   ##
=======================================
  Coverage   84.53%   84.53%
=======================================
  Files          32       32
  Lines        4191     4191
=======================================
  Hits         3543     3543
  Misses        648      648

Flag
Coverage Δ

unittests
84.53% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[SMALLFIX] Small fixes to improve tests

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20594/
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20596/
Test PASSed.


Investigate FAB hover implemetation

Investigate adding the MUI FAB  on hover on the following total card components:
Bank Balance
Payments Due
Monthly Bills
Also potential extra add/edit implementation for the monthly bills and payments due table
This will impact the Edit Note https://github.com/Craig-97/Money-Manager/issues/11 implementation so should be completed first

Investigated this on the edit note functionality implementation and the behaviour looks good on desktop but is even worse than the double click implementation on mobile as you need to tap once to see the FAB then again to open the edit dialog.
Most likely solution is placing an Edit IconButton alongside the Delete Button on the notes footer


add filters to news-flash: source, news_flash_count, start_date, end_…

…date, road_number
Signed-off-by: Adva Klinger<EMAIL_ADDRESS>

@advak is this one ready to merge?

@atalyaalon, yes it's ready!


Webpack/Browserify: Error: Cannot find module "fs"

This is an edge case, but likely to become more common as more people use Webpack/Browserify to support modular javascript in the browser.
Nock's modules themselves wrap its require('fs') try/catch to handle for the browser. However, the source of the error is the mkdirp import inside lib/back.js. The mkdirp module imports fs without the try/catch.
Since nock doesn't appear to use mkdirp except on the server, a simple fix for this is to wrap the mkdirp import into the same try/catch as the fs import.

Looks like nock isn't really supported this way/in the browser, I'll close this for now and use something else :)

Fix landed on v7.2.0.

I still have the same issue, and I'm using the 7.2.2. I also tried the 7.3.0 and 7.4.0, nothing changed.
WARNING in ./~/nock/lib/scope.js
Module not found: Error: Cannot resolve module 'fs' in /Users/antoinerey/Sites/app/node_modules/nock/lib
 @ ./~/nock/lib/scope.js 21:7-20

WARNING in ./~/nock/lib/interceptor.js
Module not found: Error: Cannot resolve module 'fs' in /Users/antoinerey/Sites/app/node_modules/nock/lib
 @ ./~/nock/lib/interceptor.js 15:9-22

WARNING in ./~/nock/lib/back.js
Module not found: Error: Cannot resolve module 'fs' in /Users/antoinerey/Sites/app/node_modules/nock/lib
 @ ./~/nock/lib/back.js 16:7-20

ERROR in ./~/mkdirp/index.js
Module not found: Error: Cannot resolve module 'fs' in /Users/antoinerey/Sites/app/node_modules/mkdirp
 @ ./~/mkdirp/index.js 2:9-22

Confirmed that this is still an issue with webpack for me as of 8.0.0.

Could we please reopen this issue? I'm encountering the same issue with :
"nock": "^8.0.0",
"webpack": "1.12.11",
"karma-webpack": "1.7.0",

actually, looks like this might be related to #409

The webpack plugin helped me. Maybe that should be covered in the documentation. But I'm at the veriy beginning wick nock and do not know if it fails somewhere else in the browser.

Still having this issue.

Has anyone been able to solve this issue? Im having the same error when trying to import express. Please Help

我也遇到了，不知道什么原因，你们解决了的说一下啊QAQ

Hey folks, I don’t see webpack compatibility to be really in scope of the projoect. If someone wants to take this one and send a pull request to resolve what problem you have, I’d be happy to accept it given that it’s not adding  a lot of complexity and that it has tests that make sure it won’t break again in future. Otherwise I recommend we close & lock this issue.
What do you think @paulmelnikow?


Uniswap Forks - Added Quickswap, Solarbeam, Trader Joe, Spiritswap, VVS Finance, and fixed pricing.

rename abis/Trisolaris to lowercase for consistency


Bug: Meson build with dev.py fails to detect SciPy with debian python

While trying to build SciPy with meson on a 32bit machine for #15814  (using docker image ubuntu:i386:bionic; though this is not an architecture specific bug, I think)
After installing python3.8  and other required deps (through apt in ubuntu), and then python deps with pip3 (installed through get-pip.py).
On running python3.8 dev.py -j 2 --build-only , build goes through fine; even the installation goes through fine.
Meson build setup OK
Build OK
Installing, see meson-install.log...
Installation OK

But later the script fails when get_project_info is called in dev.py script to import scipy, with the error message attached below.
Trying to find scipy from development installed path at: /__w/scipy/scipy/build-install/lib/python3.8/site-packages
Traceback (most recent call last):
  File "dev.py", line 393, in get_project_info
    test, version, mod_path = runtests.import_module()
  File "/__w/scipy/scipy/runtests.py", line 356, in import_module
    __import__(PROJECT_MODULE)
ModuleNotFoundError: No module named 'scipy'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "dev.py", line 635, in <module>
    main(argv=sys.argv[1:])
  File "dev.py", line 282, in main
    test, version, mod_path = get_project_info()
  File "dev.py", line 403, in get_project_info
    test, version, mod_path = runtests.import_module()
  File "/__w/scipy/scipy/runtests.py", line 356, in import_module
    __import__(PROJECT_MODULE)
ModuleNotFoundError: No module named 'scipy'
Error: Process completed with exit code 1.

The problem is that in dev.py, get_site_packages method returns '/scipy/build-install/lib/python3.8/site-packages' but actually meson installs scipy to '/scipy/build-install/lib/python3/dist-packages'
Feel free to check logs about the error and for reproducibility here.
Additional Information
When I run  python3.8 -c "import site; print(site.getsitepackages())" I get the following:
['/usr/local/lib/python3.8/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.8/dist-packages']

I guess this issue is also discussed in mesonbuild/meson#8739, explaining problems with debian python and dist-packages vs site-packages or python3.x vs python3, depending on what python (system, venv, compiled) is being used.
SciPy/NumPy/Python version information
1.9.0.dev0+1925.653fd09 1.19.0 sys.version_info(major=3, minor=8, micro=0, releaselevel='final', serial=0)
Pitch
I can suggest a hacky fix to tweak dev.py specifically in get_project_info or more specifically PATH_INSTALLED variable to also fall back to check for other possible installation paths that meson used in debian like here, for example utilizing path from ['/usr/local/lib/python3.8/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.8/dist-packages'] and stripping them to
['/lib/python3.8/dist-packages', '/lib/python3/dist-packages', '/lib/python3.8/dist-packages'] and then joining it with the prefix.
There is probably a better way to do this. I can send a PR after a discussion if this is indeed a valid bug.
cc @rgommers @Smit-create

Thanks for the detailed bug report @AnirudhDagar. You diagnosed it correctly, it's indeed due to that mess Debian made. It looks like it boils down to:
>>> import sys
>>> from sysconfig import get_path
>>> from pathlib import Path
>>> plat_path = Path(get_path("platlib"))

where plat_path gives python3.8/site-packages while things get installed to python3/dist-packages.
I don't think there's a correct solution, so a hacky one to extend get_site_packages and see if the constructed path exists and trying python3 and dist-packages fallbacks if not seems like the right thing to do here. A PR would be great.

Thanks for the quick reply and confirmation, sending a PR in a bit.

Does this work fine with runtests.py? That has a bit different hack:
https://github.com/scipy/scipy/blob/820fe86bf3ad8ba1c5647632b131659ed7bd447e/runtests.py#L431-L433

Does this work fine with runtests.py?

Do you mean if Debian python used with runtests.py (distutils based build) works without failing? Yes, it does. See Linux_Python_38_32bit_full job example.
IIUC, I don't think there is any hack here. This works in runtests.py because it defines dst_dir where the build needs to install scipy eg: /scipy/build/testenv/lib/python3.8/site-packages and then installs it to the same path.
Meson uses the path detected from global site-packages (which in case of debian is ..../python3/dist-packages/...) of the selected python interpreter to install scipy. Then we try to recreate that same path for exporting PYTHONPATH in dev.py using get_path('platlib'). But for Debian python with the current logic it mismatches the actual installed path to the one we get through platlib.
Please correct me/explain a bit more if I don't understand your comment fully. Thanks!


Back to development

Coverage remained the same at 83.603% when pulling ce4ad76863a099e31a30c8cde3ed9e8cb77ab893 on backtodevfuture into 153cc21d199f5a4b65d0d7219c1f423ea58cfab5 on master.


[Feature Request] Add Tremor dashboard library

https://www.tremor.so/

Hey @jschuur - thanks for the suggestion! How would you want it implemented? ie. do you want it used as part of a generate command? Do you just want all relevant packages installed + any lingering setup so it's ready to go?


Reimplement Vaporetto with supporting multiple tags

Supports multiple tags
Currently, a single tag followed by a slash after each token will train the tag classifier on each token.
This branch changes so that multiple tags containing pronunciation can be predicted.
To specify multiple tags, use multiple slashes as follows:
この/代名詞/コノ 人/名詞/ヒト は/助詞/ワ 火星/名詞 人/接尾辞/ジン です/助動詞/デス

This feature does not support for unknown words now.
Changes in Predictor struct
In the previous version, the predict() function takes a Sentence and returns a modified one.
In this change, predict() takes a mutable reference of Sentence instead.
Changes in Sentence struct
In the previous version, the to_tokenized_vec() function returns a newly allocated vector containing tokens.
In this change, this function is removed and iter_tokens(), which returns an iterator for tokens, is added.
This branch also includes refactoring and other API changes.

Thank you for your significant modifications!
I'll split them into some parts and review this PR part by part.

By the way, there is something wrong with the UI of the review system (maybe because of many file changes).
If my comments are strange (e.g., duplicated), could you ignore them?

@kampersanda
Finally, I chose Vec to represent TagModels instead of HashMap because HashMap cannot control the order of keys.
The order is important to reduce compression ratio of the model.
In addition, Vec is more efficient to iterate items than HashMap.
e4b6244


Example of Mic Stream using flutter sound

Felix , thanks for  your work!
Can you please provide me an example  how to implement google_speech using mic stream with flutter_sound ?
[https://pub.dev/packages/flutter_sound]
i am hangang on that , over 1 month and no success. stream types provided by flutter sound and google_speech are different i cant do it.
Thanks in advance.

@menezes85 I've solved this particular problem, if you send me an email, I can send you some sample code (still not open on GH). My email is sveinbjorn at sveinbjorn, dot org.

@felixjunghans I also would like to implement with Flutter Sound. Thank you so much.

@felixjunghans thank you for your package. Did you get around to implementing this with Flutter Sound?
I am also stuck on passing the stream to streamingRecognize when using Flutter Sound.
Is any other package better suited, any help would be welcome

@RishiKar Yes, I currently use it with flutter_sound_lite. I have now added a minimal example. Please have a look at examples/flutter_sound_example. I hope this helps you.

@felixjunghans Thank you so much. I got it to work. Now I am running into issues with flutter sound for using bluetooth devices for recording and playback 🥲 but otherwise it does work.


Error: Visualize_episodes

Hello.

Following the readme.txt instructions, I tried running visualize the episode:
python visualize_episodes.py --dataset_dir dataset/aloha_mobile_wipe_wine --episode_idx 10

data save dir: download "aloha_mobile_wipe_wine" from google drive. (episode_0.hdf5 - to episode_49.hdf5)

result: numpy.exceptions.AxisError:
all_cam_videos = np.concatenate(all_cam_videos, axis=2) # width dimension
numpy.exceptions.AxisError: axis 2 is out of bounds for array of dimension 2

Please support. Thanks a lot!

meet the same problem

Sorry for the confusion: the visualize script here is used for the legacy sim envs. Please use this https://github.com/MarkFzp/mobile-aloha/blob/main/aloha_scripts/visualize_episodes.py instead.


Is there a plan to support older versions of macos?

Hey there. It's not something we're currently planning to support, but we're open to contributions. The difficulty with this is that there's no pre-ScreenCaptureKit API designed for (performant) window capture.
It may be possible to use CGDisplayStream, updating the source rectangle every time the window moves or resizes, and recreating when windows transition between displays, but that's out of scope for us currently, and would likely suffer from framing problems, and the inability to capture just the target window when it's occluded. For reference, here are the option keys that can be set on a CGDisplayStream: Display Stream Optional Property Keys

I'm closing this issue as not planned, but for anyone who might want to take this on, feel free to create a new issue.


feat(editor): add go to line command

Types

[x] 🎉 New Features

Background or solution
Changelog
Implement Go To Line action in editor

Codecov Report

Merging #569 (25baac8) into main (d5aecd9) will decrease coverage by 0.03%.
The diff coverage is 13.15%.

@@            Coverage Diff             @@
##             main     #569      +/-   ##
==========================================
- Coverage   59.14%   59.10%   -0.04%
==========================================
  Files        1204     1205       +1
  Lines       74303    74380      +77
  Branches    15412    15427      +15
==========================================
+ Hits        43946    43964      +18
- Misses      27673    27729      +56
- Partials     2684     2687       +3

Impacted Files
Coverage Δ

packages/core-browser/src/common/common.command.ts
100.00% <ø> (ø)

packages/core-browser/src/quick-open/index.ts
79.72% <ø> (ø)

.../browser/monaco-contrib/command/command.service.ts
59.28% <ø> (ø)

...c/browser/quick-open/workspace-symbol-quickopen.ts
52.13% <ø> (ø)

packages/i18n/src/common/en-US.lang.ts
100.00% <ø> (ø)

packages/i18n/src/common/zh-CN.lang.ts
100.00% <ø> (ø)

...ckages/editor/src/browser/quick-open/go-to-line.ts
13.15% <13.15%> (ø)

packages/file-service/src/common/files.ts
87.17% <0.00%> (ø)

packages/core-common/src/utils/file-uri.ts
81.25% <0.00%> (ø)

packages/core-browser/src/encoding-registry.ts
60.00% <0.00%> (ø)

... and 21 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d5aecd9...25baac8. Read the comment docs.

/publish

/publish


Lack of functions for interface cell

When add Dirichlet boundary to nodes connected to interface cell, an error occurred shown that no function geometirc_interpolation and reference_coordinates
using Ferrite, FerriteInterfaceElements, SparseArrays

grid = generate_grid(Quadrilateral, (10, 10))
addcellset!(grid, "up", (x) -> 0.0 <= x[2])
addcellset!(grid, "down", (x) -> x[2] <= 0.0)
addcellset!(grid, "bulk", 1:getncells(grid))

grid = insert_interfaces(grid, ["up", "down"])
addnodeset!(grid, "loadPoint", (x) -> x[1] ≈ 1.0 && x[2] ≈ 0.0)

dh = DofHandler(grid)
set_bulk = getcellset(grid, "bulk")
set_interface = getcellset(grid, "interfaces")
ip_bulk = Lagrange{RefQuadrilateral,1}()^2
ip_interface = InterfaceCellInterpolation(Lagrange{RefLine,1}())^2
add!(SubDofHandler(dh, set_bulk), :u, ip_bulk)
add!(SubDofHandler(dh, set_interface), :u, ip_interface)
close!(dh);

ch = ConstraintHandler(dh)
add!(ch, Dirichlet(:u, getfacetset(grid, "left"), Returns(zeros(2))))
add!(ch, Dirichlet(:u, getnodeset(grid, "loadPoint"), Returns(1.0), [1]))
@time "ch" close!(ch)

ERROR: MethodError: no method matching geometric_interpolation(::Type{InterfaceCell{RefQuadrilateral, Line, 4}})

Closest candidates are:
  geometric_interpolation(::Type{QuadraticTetrahedron})

Applying dirichlet constraints directly to nodes are always a bit iffy in Ferrite. First of all, your nodeset "loadpoint" has two nodes in it, one from each side of the interface.
julia> getnodeset(grid, "loadPoint")
OrderedCollections.OrderedSet{Int64} with 2 elements:
  66
  132

Which one do you want to apply the constraint to?
A work around is to apply the constraint to a vertex instead. A vertex is similar to a node, but the vertex is also associated with an element VertexIndex(Cellid, LocalVertexID) (which makes it a bit easier for the constraint handler to find the correct dof):
addvertexset!(grid, "loadPoint", (x) -> x[1] ≈ 1.0 && x[2] ≈ 0.0)
julia> getvertexset(grid, "loadPoint")
OrderedCollections.OrderedSet{VertexIndex} with 4 elements:
  VertexIndex((50, 3)) #Bottom bulk
  VertexIndex((60, 2)) #Top bulk
  VertexIndex((110, 1)) #Cohesive element
  VertexIndex((110, 3)) #cohesive element

Lets say we want to apply a constraint to the top bulk material, simply change the dirichlet to:
add!(ch, Dirichlet(:u, [getvertexset(grid, "loadPoint")[1]], Returns(1.0), [1]))

The best option would be to try to re-formulate the Dirichlet constraint to be applied to "facets" instead, because they are usually uniquely defined.

@lijas  Thank you very much for your help. My original intention was to apply dirichlet constraints to both nodes, so according to your prompt, the correct code should be:
add!(ch, Dirichlet(:u, collect(getvertexset(grid, "loadPoint"))[[1,2]], Returns(1.0), [1]))

This approach is feasible because the load applied to the interface cell can always be treated to the bulk cells.


VFS-570 Write Ability for HDFS Provider

VFS-570 Write Ability for HDFS Provider. Push request to include Aron's patch

Hi.. Is there an issue with this pull request or can it be integrated?


fix: Item activity mobile

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Bugfix

Needs Design check

@exezbcz please review

Context

[x] Closes #9093

Did your issue had any of the "$" label on it?

[x] My DOT address: Payout

Screenshot 📸

[x] My fix has changed UI

Copilot Summary
copilot:summary
copilot:poem

thanks!
pay 20 usd

😍 Perfect, I’ve sent the payout
💵 $20 @ 6.41 USD/DOT ~ 3.12 $DOT
🧗 16SjUbGKSdjCdWTy3NNT3JxbRVGGqD4mwkHpc6BD9U2Rp29Z
🔗 0xc7bc99876be4526ae67d9d0fc14cbf70c31c42dc0eb119be9f2d8fed62fc089e
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


I could not connect to it in docker machine on mac

I did like this.
bash-3.2$ docker run -d --name ikev2-vpn-server --privileged -p 500:500/udp -p 4500:4500/udp gaomd/ikev2-vpn-server:0.2.2
0419952b7b55d80712562202421f27141695244f7ac2894969bb7be722904021
bash-3.2$ docker-machine ip default
<IP_ADDRESS>
bash-3.2$ docker run -i -t --rm --volumes-from ikev2-vpn-server -e "HOST=<IP_ADDRESS>" gaomd/ikev2-vpn-server:0.2.2 generate-mobileconfig > ikev2-vpn.mobileconfig

Then I double-click the mobileconfig file.
However, I could not connect via it.
MBP 2014
OS: EI Capitan 10.11.2

Both failed on my vps

I could basically reproduce your situation, but it work perfect on the VPS, so I consider this problem was related to IP routing on the localhost, when connecting from local machine to local virtual (docker) machine.
I should have investigate more in the future, leave this issues open for more feedbacks.

SquirrelMajik,  could you open your ikev2-vpn.mobileconfig in a text editor and check the first few lines for an error message.


[BUG] SSO not working

Is there an existing issue for this?

[X] I have searched the existing issues

Are you using the latest docker image for BTPSA?

[X] I'm using the latest docker image for BTPSA.

Which area is mainly impacted
Security
Current Behavior
I want to log on using SSO, but calling ./btpsa -loginmethod sso still asks me for a password
[2022-05-01 08:01:16] WARNING    : YOU NEED TO PROVIDE YOUR BTP PASSWORD                       Please enter your BTP password (hit Enter when done):
Expected Behavior
Something similar to when using the CF or BTP CLI
Temporary Authentication Code ( Get one at https://login.cf.us10.hana.ondemand.c om/passcode ):
Steps To Reproduce

In the latest docker environment
Call ./btpsa -loginmethod sso

Logs and configuration files available?
No response
Anything else?
No response

Is it possible that you have set the loginmethod inside your parameters.json file to "basicAuthentication"?
The parameters.json file has a higher priority than the provided parameters in the command line.

Thank you, that was the issue. Shouldn't it be the other way around, that the command line have higher priority than the settings file?

I've been thinking back and forth on that question. I tend to agree with you. I'll create a feature request on this and let the community participate on the discussion and the final conclusion. Please feel free to join the discussion, too.

Added a new feature request here: https://github.com/SAP-samples/btp-setup-automator/issues/82


PatternTextStyle: anchor does not work as expected when pattern and value are both empty.

The UITextField says it has correct offset but the caret somehow appears at the start. For example, while testing, offset == 6 is at the end of the UITextField, and offset == 5 is somehow at the start…

Is this an issue with the zero with space: U+200B?

OK. So I think UITextField treats zero width space characters like this: if the caret appears before a zero-width character, increment it forwards until the next non-zero-width character. If no such character is found, display the caret at the start of the UITextField.

Guess I have to make an anchor-less solution...


extra blank lines

Is it possible to create a function to be able to remove all extra blank lines and not all blank lines ? something like this : https://marketplace.visualstudio.com/items?itemName=rintoj.blank-line-organizer
Example :
// start of file

const Person = {
    item : "item"

}

person.item = "item 1"

// end of file

would end up being :
// start of file

const Person = {
    item : "item"

}

person.item = "item 1"

// end of file

in other words: Remove Consecutive Empty Lines?

You can try it
StringManipulation.zip

Exactly, ok great, thanks for the fast response. I'll try it.

Would you know when you might be able to publish these changes to JetBrains plugin?

yes, now.


cdk 2

has a migration to cdk 2.* begun? just wondering if someone has done the leg work before i dig in ;)
thx, j

So far there are no activities. You are welcome to support...  ;)


Code snippets are hard to read on dark backgrounds

Is this a BUG REPORT or FEATURE REQUEST?:
bug
What happened:
Currently code snippets are hard to read on darker backgrounds.
See: https://about.txtdirect.org/hosted/
What you expected to happen:
We should either invert the text color or add a light background  to code snippets on dark backgrounds.
Anything else we need to know?:
Happy for other suggestions. Just wanted to track this.

This is actually fixed in the dev/colors PR. Inline code and link is much harder to deal with.

Invert the color on the inline and block codes.

code block and inline code inverts the text and background color to showcase the difference to normal text.


feat(native_blockifier): vm resource fee costs in a struct

This change is

Codecov Report
Attention: 25 lines in your changes are missing coverage. Please review.

Comparison is base (0a5416b) 70.43% compared to head (64c3cd5) 70.30%.

Files
Patch %
Lines

crates/native_blockifier/src/py_block_executor.rs
0.00%
19 Missing :warning:

crates/blockifier/src/block_context.rs
58.33%
4 Missing and 1 partial :warning:

crates/blockifier/src/transaction/objects.rs
90.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@               Coverage Diff                @@
##           main-v0.13.1    #1396      +/-   ##
================================================
- Coverage         70.43%   70.30%   -0.14%
================================================
  Files                59       59
  Lines              7713     7745      +32
  Branches           7713     7745      +32
================================================
+ Hits               5433     5445      +12
- Misses             1853     1872      +19
- Partials            427      428       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.