useNavigate causes slow TS performance

Describe the bug
I have a fairly small project (it will grow), right now there are about ~20 pages, but I am already facing some performance issues after including the router package, mainly in the IntelliSense and auto-complete. After some investigations, I have narrowed down part of the issue to be that for every component I use navigate from useNavigate, I get a bad compilation time for that file.
I have identified this using --generateTrace flag for tsc, it points to every single one of these files to the particular line of when the navigate(...) method is being used.
npx @typescript/analyze-trace trace
Hot Spots
├─ Check file /users/me/dev/project/applications/web/dashboard/src/pages/policiesaddedit/policiesaddedit.tsx (1050ms)
├─ Check file /users/me/dev/project/packages/web/ui/src/components/sidebar/sidebar.tsx (1001ms)
│  └─ Check deferred node from (line 70, char 9) to (line 82, char 16) (979ms)
│     └─ Check expression in /users/me/dev/project/applications/web/dashboard/src/router/index.tsx from (line 84, char 24) to (line 84, char 30) (651ms)
│        └─ Check expression from (line 71, char 16) to (line 77, char 3) (651ms)
│           └─ Check expression from (line 71, char 27) to (line 77, char 2) (649ms)
│              └─ Check expression from (line 72, char 5) to (line 72, char 14) (642ms)
│                 └─ Check expression from (line 32, char 19) to (line 64, char 3) (626ms)
│                    └─ Check expression from (line 32, char 41) to (line 64, char 2) (626ms)
│                       └─ Check expression from (line 34, char 5) to (line 63, char 7) (444ms)
│                          └─ Check expression from (line 34, char 36) to (line 63, char 6) (435ms)
│                             └─ Check expression from (line 35, char 9) to (line 62, char 11) (435ms)
│                                └─ Check expression from (line 35, char 37) to (line 62, char 10) (430ms)
├─ Check file /users/me/dev/project/applications/web/dashboard/src/pages/signup/index.tsx (814ms)
│  └─ Check deferred node from (line 54, char 9) to (line 223, char 16) (735ms)
│     └─ Check expression from (line 55, char 13) to (line 58, char 44) (732ms)
│        └─ Check expression from (line 57, char 22) to (line 57, char 46) (731ms)
│           └─ Check expression from (line 57, char 23) to (line 57, char 45) (731ms)
│              └─ Compare types 137362 and 137370 (731ms)
│                 └─ Check expression from (line 39, char 20) to (line 48, char 19) (731ms)
│                    └─ Check expression from (line 39, char 20) to (line 45, char 23) (730ms)
│                       └─ Check expression from (line 39, char 20) to (line 44, char 96) (730ms)
│                          └─ Check expression from (line 44, char 23) to (line 44, char 95) (730ms)
│                             └─ Check expression from (line 44, char 29) to (line 44, char 95) (730ms)
├─ Check file /users/me/dev/project/applications/web/dashboard/src/pages/login/index.tsx (795ms)
│  └─ Check deferred node from (line 57, char 9) to (line 124, char 16) (725ms)
│     └─ Check expression from (line 58, char 13) to (line 61, char 44) (719ms)
│        └─ Check expression from (line 60, char 22) to (line 60, char 46) (718ms)
│           └─ Check expression from (line 60, char 23) to (line 60, char 45) (718ms)
│              └─ Compare types 134742 and 134800 (717ms)
│                 └─ Check expression from (line 34, char 20) to (line 51, char 14) (717ms)
│                    └─ Check expression from (line 38, char 17) to (line 50, char 18) (716ms)
│                       └─ Check expression from (line 45, char 32) to (line 45, char 113) (716ms)
├─ Check file /users/me/dev/project/applications/web/dashboard/src/pages/apikeysedit/index.tsx (703ms)
│  └─ Check deferred node from (line 35, char 9) to (line 65, char 10) (553ms)
│     └─ Check expression from (line 41, char 20) to (line 64, char 15) (553ms)
│        └─ Check expression from (line 58, char 21) to (line 64, char 14) (537ms)
│           └─ Check expression from (line 59, char 24) to (line 63, char 19) (537ms)
├─ Check file /users/me/dev/project/applications/web/dashboard/src/pages/accountedit/index.tsx (615ms)
│  └─ Check deferred node from (line 33, char 32) to (line 43, char 6) (516ms)
│     └─ Check expression from (line 36, char 13) to (line 36, char 62) (515ms)
│        └─ Check expression from (line 36, char 19) to (line 36, char 62) (515ms)
└─ Check file /users/me/dev/project/applications/web/dashboard/src/pages/resolversinstancesaddedit/resolversinstancesaddedit.tsx (513ms)
   └─ Check deferred node from (line 55, char 9) to (line 72, char 10) (377ms)
      └─ Check expression from (line 58, char 17) to (line 61, char 40) (373ms)
         └─ Check expression from (line 58, char 17) to (line 61, char 25) (373ms)
            └─ Check expression from (line 58, char 17) to (line 61, char 19) (373ms)

I am using the navigate like (example from SignUp):
export default function SignUpPage() {
    const navigate = useNavigate({ from: '/sign-up' });

    const onSubmit = useCallback(
        async (data: SignUpSchemaType) => {
            // auth code
                .then(() => navigate({ to: '/verify-account', search: { email: data.email } }))
        },
        [context.auth],
    );

From the example, on the line with navigate I get the hotspot from the report.
Is there anything I can do to help out the compiler for faster resolution? Maybe if there are some recommendations, it would be helpful to add on the docs site.
Your Example Website or App
/
Steps to Reproduce the Bug or Issue

Import via useNavigate
Use method navigate
Slow TS compile

Expected behavior
Fast TS compile
Screenshots or Videos
No response
Platform

OS: MacOS 2019, Intel i9, 16GB RAM
Browser: [e.g. Chrome, Safari, Firefox]
Version: 1.14.0

Additional context
I have may other instnaces where navigation is made via Link and those instances doesn't seem to cause slow compilation. Maybe because they are JSX?

Are you using file-based routing? if no, can you try it out and also trace it in comparison?

Are you using file-based routing? if no, can you try it out and also trace it in comparison?

Using the code based routes, primary because when I was starting the router implementation there was no docs recommendation for the file based one.
I can try it tomorrow. Does the file based one have better performance?

Does the file based one have better performance?

It might since it might build the route tree differently. However the useNavigate typing is the same ...
looking forward to your results!

Are you using file-based routing? if no, can you try it out and also trace it in comparison?

Hi! We are using file based routers and the ts compiler completely times out for us. We have around 100 routes but suspect the issues occurs with far fewer routes. I can possible send you some traces tomorrow.

Are you using file-based routing? if no, can you try it out and also trace it in comparison?

Hi! We are using file based routers and the ts compiler completely times out for us. We have around 100 routes but suspect the issues occurs with far fewer routes. I can possibly send you some traces tomorrow.

How is the VS Code auto-complete experience for you? Is it slow to show suggestions on files that include any of the router components?

Are you using file-based routing? if no, can you try it out and also trace it in comparison?

Hi! We are using file based routers and the ts compiler completely times out for us. We have around 100 routes but suspect the issues occurs with far fewer routes. I can possibly send you some traces tomorrow.

How is the VS Code auto-complete experience for you? Is it slow to show suggestions on files that include any of the router components?

It's really slow. 20-30s or sometimes no suggestions. A colleague of mine reports that files with no references to route components are quick/normal.

Do you have some circular dependencies? e.g. do you use fooRoute.fullPath instead of the string literal /foo?

In my case, Navigate component rerenders multiple times.

Do you have some circular dependencies? e.g. do you use fooRoute.fullPath instead of the string literal /foo?

In our case, we use  from: fooRoute.fullPath in our navigates, i.e. const navigate = useNavigate({ from: Route.fullPath });. This only refers to file routes in the same file.
Our trace hotspots also point to navigates both the hook and the <Navigate> component, and also to isRoute() from useMatchRoute(). The problem seems to be linked to the to property.

Are you using file-based routing? if no, can you try it out and also trace it in comparison?

I have tried to migrate to file-based routing, and the performance is even worse. For example for the file of policiesaddedit what used to be ~1000ms now is at ~2000ms
Here is the experience with InteliSense experience when the file doesn't have the Router interaction:
https://github.com/TanStack/router/assets/1628876/43456be9-229a-42f4-b381-ba46888c3cf1
Here is the experience when the component has Router interaction. Must note that this is very simple component that even here the experience is not that bad. In my policiesaddedit component it takes ~5s to create the suggestions.
https://github.com/TanStack/router/assets/1628876/da5640c7-6455-4c60-9fe8-3a6dbd938552

Here it is the hotspot log:
Hot Spots
├─ Check file /users/me/dev/project/applications/web/dashboard/src/pages/policiesaddedit/policiesaddedit.tsx (2052ms)
│  ├─ Check deferred node from (line 95, char 9) to (line 111, char 10) (941ms)
│  │  └─ Check expression from (line 98, char 17) to (line 100, char 18) (940ms)
│  │     └─ Check expression from (line 98, char 17) to (line 98, char 109) (940ms)
│  │        └─ Check expression from (line 98, char 17) to (line 98, char 103) (939ms)
│  └─ Check variable declaration from (line 94, char 11) to (line 113, char 6) (883ms)
│     └─ Check expression from (line 94, char 22) to (line 113, char 6) (883ms)
│        └─ Check expression from (line 112, char 9) to (line 112, char 66) (883ms)
│           └─ Compare types 43842 and 53223 (881ms)
│              ├─ {"id":43842,"kind":"AnonymousType","location":{"path":"/users/me/dev/project/node_modules/.pnpm/@tanstack+react-router@1.14.0_react-dom@18.2.0_react@18.2.0/node_modules/@tanstack/react-router/dist/esm/usenavigate.d.ts","line":9,"char":5}}
│              └─ {"id":53223,"kind":"AnonymousFunction","location":{"path":"/users/me/dev/project/applications/web/dashboard/src/pages/policiesaddedit/policiesaddedit.tsx","line":64,"char":9}}
├─ Check file /users/me/dev/project/applications/web/dashboard/src/pages/signup/index.tsx (1919ms)
│  └─ Check deferred node from (line 54, char 9) to (line 223, char 16) (1790ms)
│     └─ Check expression from (line 55, char 13) to (line 58, char 44) (1784ms)
│        └─ Check expression from (line 57, char 22) to (line 57, char 46) (1783ms)
│           └─ Check expression from (line 57, char 23) to (line 57, char 45) (1783ms)
│              └─ Compare types 33165 and 33208 (1783ms)
│                 └─ Check expression from (line 39, char 20) to (line 48, char 19) (1782ms)
│                    └─ Check expression from (line 39, char 20) to (line 45, char 23) (1782ms)
│                       └─ Check expression from (line 39, char 20) to (line 44, char 96) (1782ms)
│                          └─ Check expression from (line 44, char 23) to (line 44, char 95) (1780ms)
│                             └─ Check expression from (line 44, char 29) to (line 44, char 95) (1780ms)
│                                └─ Check expression from (line 44, char 38) to (line 44, char 94) (574ms)
├─ Check file /users/me/dev/project/applications/web/dashboard/src/pages/login/index.tsx (1897ms)
│  └─ Check deferred node from (line 60, char 9) to (line 127, char 16) (1766ms)
│     └─ Check expression from (line 61, char 13) to (line 64, char 44) (1762ms)
│        └─ Check expression from (line 63, char 22) to (line 63, char 46) (1762ms)
│           └─ Check expression from (line 63, char 23) to (line 63, char 45) (1762ms)
│              └─ Compare types 36665 and 33208 (1762ms)
│                 └─ Check expression from (line 37, char 20) to (line 54, char 14) (1761ms)
│                    └─ Check expression from (line 41, char 17) to (line 53, char 18) (1760ms)
│                       └─ Check expression from (line 48, char 32) to (line 48, char 113) (1760ms)
│                          └─ Check expression from (line 48, char 41) to (line 48, char 112) (575ms)
├─ Check file /users/me/dev/project/applications/web/dashboard/src/routes/__root.tsx (1572ms)
│  └─ Check variable declaration from (line 42, char 11) to (line 49, char 7) (1226ms)
│     └─ Check expression from (line 42, char 29) to (line 49, char 7) (1225ms)
│        └─ Check expression in /users/me/dev/project/applications/web/dashboard/src/router.ts from (line 22, char 24) to (line 22, char 30) (765ms)
│           └─ Check expression from (line 11, char 16) to (line 17, char 3) (764ms)
│              └─ Check expression from (line 11, char 29) to (line 17, char 2) (763ms)
│                 └─ Check expression from (line 12, char 5) to (line 12, char 14) (762ms)
│                    └─ Check expression in /users/me/dev/project/applications/web/dashboard/src/routetree.gen.ts from (line 264, char 26) to (line 297, char 3) (759ms)
│                       └─ Check expression from (line 264, char 48) to (line 297, char 2) (759ms)
│                          └─ Check expression from (line 265, char 3) to (line 290, char 5) (716ms)
│                             └─ Check expression from (line 265, char 25) to (line 290, char 4) (545ms)
│                                └─ Check expression from (line 266, char 5) to (line 289, char 7) (545ms)
│                                   └─ Check expression from (line 266, char 37) to (line 289, char 6) (539ms)
├─ Check file /users/me/dev/project/applications/web/dashboard/src/pages/resolversinstancesaddedit/resolversinstancesaddedit.tsx (1552ms)
│  └─ Check deferred node from (line 55, char 9) to (line 72, char 10) (1178ms)
│     └─ Check expression from (line 58, char 17) to (line 61, char 40) (1176ms)
│        └─ Check expression from (line 58, char 17) to (line 61, char 25) (1176ms)
│           └─ Check expression from (line 58, char 17) to (line 61, char 19) (1176ms)
├─ Check file /users/me/dev/project/applications/web/dashboard/src/pages/accountedit/index.tsx (1224ms)
│  └─ Check deferred node from (line 33, char 32) to (line 43, char 6) (1119ms)
│     └─ Check expression from (line 36, char 13) to (line 36, char 62) (1119ms)
│        └─ Check expression from (line 36, char 19) to (line 36, char 62) (1118ms)
├─ Check file /users/me/dev/project/applications/web/dashboard/src/pages/policiesdetails/policiesdetails.tsx (966ms)
│  └─ Check deferred node from (line 37, char 31) to (line 37, char 85) (845ms)
│     └─ Check expression from (line 37, char 37) to (line 37, char 85) (845ms)
├─ Check file /users/me/dev/project/applications/web/dashboard/src/pages/apikeysdetails/apikeysdetails.tsx (963ms)
│  └─ Check deferred node from (line 38, char 31) to (line 38, char 85) (854ms)
│     └─ Check expression from (line 38, char 37) to (line 38, char 85) (854ms)
└─ Check file /users/me/dev/project/applications/web/dashboard/src/pages/apikeysedit/index.tsx (901ms)
   └─ Check deferred node from (line 35, char 9) to (line 65, char 10) (776ms)
      └─ Check expression from (line 41, char 20) to (line 64, char 15) (776ms)
         └─ Check expression from (line 58, char 21) to (line 64, char 14) (774ms)
            └─ Check expression from (line 59, char 24) to (line 63, char 19) (774ms)

Taking as example policiesaddedit, here are the lines that are mentioned:
const onSubmit = useCallback(
        async (data: PolicyFormData) => {
            try {
                const res = props.type === 'add' ? await handleAddSubmit(data) : await handleEditSubmit(data);
// Line 98 bellow with `navigate`
                navigate({ to: '/iam/policies/$policyId', params: { policyId: res.policy.policyId } }).catch(
                    console.error,
                );
            } catch (e) {
                if (e instanceof Error) {
                    if (e.cause instanceof ZodError) {
                        form.setError('root', { message: fromZodError(e.cause).toString() });
                    } else {
                        form.setError('root', { message: e.message });
                    }
                }
                console.error('error creating policy', e);
            }
        },
// Line 112 bellow with the `navigate`
        [props.type, navigate, handleAddSubmit, handleEditSubmit],
    );

I do not have any circular dependencies between the code, route definitions, and generated route tree.
Here is my generated route tree
// This file is auto-generated by TanStack Router

// Import Routes

import { Route as rootRoute } from './routes/__root'
import { Route as AuthenticationLayoutImport } from './routes/_authenticationLayout'
import { Route as AuthImport } from './routes/_auth'
import { Route as AuthenticationLayoutVerifyAccountImport } from './routes/_authenticationLayout/verify-account'
import { Route as AuthenticationLayoutSignUpImport } from './routes/_authenticationLayout/sign-up'
import { Route as AuthenticationLayoutLoginImport } from './routes/_authenticationLayout/login'
import { Route as AuthenticationLayoutForgotPasswordImport } from './routes/_authenticationLayout/forgot-password'
import { Route as AuthBaseLayoutImport } from './routes/_auth/_baseLayout'
import { Route as AuthBaseLayoutResolversIndexImport } from './routes/_auth/_baseLayout.resolvers/index'
import { Route as AuthBaseLayoutIamIndexImport } from './routes/_auth/_baseLayout.iam/index'
import { Route as AuthBaseLayoutAccountIndexImport } from './routes/_auth/_baseLayout.account/index'
import { Route as AuthBaseLayoutResolversInstancesImport } from './routes/_auth/_baseLayout.resolvers/instances'
import { Route as AuthBaseLayoutIamUsersImport } from './routes/_auth/_baseLayout.iam/users'
import { Route as AuthBaseLayoutIamPoliciesImport } from './routes/_auth/_baseLayout.iam/policies'
import { Route as AuthBaseLayoutIamApiKeysImport } from './routes/_auth/_baseLayout.iam/api-keys'
import { Route as AuthBaseLayoutAccountEditImport } from './routes/_auth/_baseLayout.account/edit'
import { Route as AuthBaseLayoutResolversInstancesAddImport } from './routes/_auth/_baseLayout.resolvers/instances.add'
import { Route as AuthBaseLayoutResolversInstancesInstanceIdImport } from './routes/_auth/_baseLayout.resolvers/instances.$instanceId'
import { Route as AuthBaseLayoutIamPoliciesAddImport } from './routes/_auth/_baseLayout.iam/policies.add'
import { Route as AuthBaseLayoutIamPoliciesPolicyIdImport } from './routes/_auth/_baseLayout.iam/policies.$policyId'
import { Route as AuthBaseLayoutIamApiKeysApiKeyIdImport } from './routes/_auth/_baseLayout.iam/api-keys.$apiKeyId'
import { Route as AuthBaseLayoutResolversInstancesInstanceIdEditImport } from './routes/_auth/_baseLayout.resolvers/instances.$instanceId.edit'
import { Route as AuthBaseLayoutIamPoliciesPolicyIdEditImport } from './routes/_auth/_baseLayout.iam/policies.$policyId.edit'
import { Route as AuthBaseLayoutIamApiKeysApiKeyIdEditImport } from './routes/_auth/_baseLayout.iam/api-keys.$apiKeyId.edit'

// Create/Update Routes

const AuthenticationLayoutRoute = AuthenticationLayoutImport.update({
  id: '/_authenticationLayout',
  getParentRoute: () => rootRoute,
} as any)

const AuthRoute = AuthImport.update({
  id: '/_auth',
  getParentRoute: () => rootRoute,
} as any)

const AuthenticationLayoutVerifyAccountRoute =
  AuthenticationLayoutVerifyAccountImport.update({
    path: '/verify-account',
    getParentRoute: () => AuthenticationLayoutRoute,
  } as any)

const AuthenticationLayoutSignUpRoute = AuthenticationLayoutSignUpImport.update(
  {
    path: '/sign-up',
    getParentRoute: () => AuthenticationLayoutRoute,
  } as any,
)

const AuthenticationLayoutLoginRoute = AuthenticationLayoutLoginImport.update({
  path: '/login',
  getParentRoute: () => AuthenticationLayoutRoute,
} as any)

const AuthenticationLayoutForgotPasswordRoute =
  AuthenticationLayoutForgotPasswordImport.update({
    path: '/forgot-password',
    getParentRoute: () => AuthenticationLayoutRoute,
  } as any)

const AuthBaseLayoutRoute = AuthBaseLayoutImport.update({
  id: '/_baseLayout',
  getParentRoute: () => AuthRoute,
} as any)

const AuthBaseLayoutResolversIndexRoute =
  AuthBaseLayoutResolversIndexImport.update({
    path: '/resolvers/',
    getParentRoute: () => AuthBaseLayoutRoute,
  } as any)

const AuthBaseLayoutIamIndexRoute = AuthBaseLayoutIamIndexImport.update({
  path: '/iam/',
  getParentRoute: () => AuthBaseLayoutRoute,
} as any)

const AuthBaseLayoutAccountIndexRoute = AuthBaseLayoutAccountIndexImport.update(
  {
    path: '/account/',
    getParentRoute: () => AuthBaseLayoutRoute,
  } as any,
)

const AuthBaseLayoutResolversInstancesRoute =
  AuthBaseLayoutResolversInstancesImport.update({
    path: '/resolvers/instances',
    getParentRoute: () => AuthBaseLayoutRoute,
  } as any)

const AuthBaseLayoutIamUsersRoute = AuthBaseLayoutIamUsersImport.update({
  path: '/iam/users',
  getParentRoute: () => AuthBaseLayoutRoute,
} as any)

const AuthBaseLayoutIamPoliciesRoute = AuthBaseLayoutIamPoliciesImport.update({
  path: '/iam/policies',
  getParentRoute: () => AuthBaseLayoutRoute,
} as any)

const AuthBaseLayoutIamApiKeysRoute = AuthBaseLayoutIamApiKeysImport.update({
  path: '/iam/api-keys',
  getParentRoute: () => AuthBaseLayoutRoute,
} as any)

const AuthBaseLayoutAccountEditRoute = AuthBaseLayoutAccountEditImport.update({
  path: '/account/edit',
  getParentRoute: () => AuthBaseLayoutRoute,
} as any)

const AuthBaseLayoutResolversInstancesAddRoute =
  AuthBaseLayoutResolversInstancesAddImport.update({
    path: '/add',
    getParentRoute: () => AuthBaseLayoutResolversInstancesRoute,
  } as any)

const AuthBaseLayoutResolversInstancesInstanceIdRoute =
  AuthBaseLayoutResolversInstancesInstanceIdImport.update({
    path: '/$instanceId',
    getParentRoute: () => AuthBaseLayoutResolversInstancesRoute,
  } as any)

const AuthBaseLayoutIamPoliciesAddRoute =
  AuthBaseLayoutIamPoliciesAddImport.update({
    path: '/add',
    getParentRoute: () => AuthBaseLayoutIamPoliciesRoute,
  } as any)

const AuthBaseLayoutIamPoliciesPolicyIdRoute =
  AuthBaseLayoutIamPoliciesPolicyIdImport.update({
    path: '/$policyId',
    getParentRoute: () => AuthBaseLayoutIamPoliciesRoute,
  } as any)

const AuthBaseLayoutIamApiKeysApiKeyIdRoute =
  AuthBaseLayoutIamApiKeysApiKeyIdImport.update({
    path: '/$apiKeyId',
    getParentRoute: () => AuthBaseLayoutIamApiKeysRoute,
  } as any)

const AuthBaseLayoutResolversInstancesInstanceIdEditRoute =
  AuthBaseLayoutResolversInstancesInstanceIdEditImport.update({
    path: '/edit',
    getParentRoute: () => AuthBaseLayoutResolversInstancesInstanceIdRoute,
  } as any)

const AuthBaseLayoutIamPoliciesPolicyIdEditRoute =
  AuthBaseLayoutIamPoliciesPolicyIdEditImport.update({
    path: '/edit',
    getParentRoute: () => AuthBaseLayoutIamPoliciesPolicyIdRoute,
  } as any)

const AuthBaseLayoutIamApiKeysApiKeyIdEditRoute =
  AuthBaseLayoutIamApiKeysApiKeyIdEditImport.update({
    path: '/edit',
    getParentRoute: () => AuthBaseLayoutIamApiKeysApiKeyIdRoute,
  } as any)

// Populate the FileRoutesByPath interface

declare module '@tanstack/react-router' {
  interface FileRoutesByPath {
    '/_auth': {
      preLoaderRoute: typeof AuthImport
      parentRoute: typeof rootRoute
    }
    '/_authenticationLayout': {
      preLoaderRoute: typeof AuthenticationLayoutImport
      parentRoute: typeof rootRoute
    }
    '/_auth/_baseLayout': {
      preLoaderRoute: typeof AuthBaseLayoutImport
      parentRoute: typeof AuthImport
    }
    '/_authenticationLayout/forgot-password': {
      preLoaderRoute: typeof AuthenticationLayoutForgotPasswordImport
      parentRoute: typeof AuthenticationLayoutImport
    }
    '/_authenticationLayout/login': {
      preLoaderRoute: typeof AuthenticationLayoutLoginImport
      parentRoute: typeof AuthenticationLayoutImport
    }
    '/_authenticationLayout/sign-up': {
      preLoaderRoute: typeof AuthenticationLayoutSignUpImport
      parentRoute: typeof AuthenticationLayoutImport
    }
    '/_authenticationLayout/verify-account': {
      preLoaderRoute: typeof AuthenticationLayoutVerifyAccountImport
      parentRoute: typeof AuthenticationLayoutImport
    }
    '/_auth/_baseLayout/account/edit': {
      preLoaderRoute: typeof AuthBaseLayoutAccountEditImport
      parentRoute: typeof AuthBaseLayoutImport
    }
    '/_auth/_baseLayout/iam/api-keys': {
      preLoaderRoute: typeof AuthBaseLayoutIamApiKeysImport
      parentRoute: typeof AuthBaseLayoutImport
    }
    '/_auth/_baseLayout/iam/policies': {
      preLoaderRoute: typeof AuthBaseLayoutIamPoliciesImport
      parentRoute: typeof AuthBaseLayoutImport
    }
    '/_auth/_baseLayout/iam/users': {
      preLoaderRoute: typeof AuthBaseLayoutIamUsersImport
      parentRoute: typeof AuthBaseLayoutImport
    }
    '/_auth/_baseLayout/resolvers/instances': {
      preLoaderRoute: typeof AuthBaseLayoutResolversInstancesImport
      parentRoute: typeof AuthBaseLayoutImport
    }
    '/_auth/_baseLayout/account/': {
      preLoaderRoute: typeof AuthBaseLayoutAccountIndexImport
      parentRoute: typeof AuthBaseLayoutImport
    }
    '/_auth/_baseLayout/iam/': {
      preLoaderRoute: typeof AuthBaseLayoutIamIndexImport
      parentRoute: typeof AuthBaseLayoutImport
    }
    '/_auth/_baseLayout/resolvers/': {
      preLoaderRoute: typeof AuthBaseLayoutResolversIndexImport
      parentRoute: typeof AuthBaseLayoutImport
    }
    '/_auth/_baseLayout/iam/api-keys/$apiKeyId': {
      preLoaderRoute: typeof AuthBaseLayoutIamApiKeysApiKeyIdImport
      parentRoute: typeof AuthBaseLayoutIamApiKeysImport
    }
    '/_auth/_baseLayout/iam/policies/$policyId': {
      preLoaderRoute: typeof AuthBaseLayoutIamPoliciesPolicyIdImport
      parentRoute: typeof AuthBaseLayoutIamPoliciesImport
    }
    '/_auth/_baseLayout/iam/policies/add': {
      preLoaderRoute: typeof AuthBaseLayoutIamPoliciesAddImport
      parentRoute: typeof AuthBaseLayoutIamPoliciesImport
    }
    '/_auth/_baseLayout/resolvers/instances/$instanceId': {
      preLoaderRoute: typeof AuthBaseLayoutResolversInstancesInstanceIdImport
      parentRoute: typeof AuthBaseLayoutResolversInstancesImport
    }
    '/_auth/_baseLayout/resolvers/instances/add': {
      preLoaderRoute: typeof AuthBaseLayoutResolversInstancesAddImport
      parentRoute: typeof AuthBaseLayoutResolversInstancesImport
    }
    '/_auth/_baseLayout/iam/api-keys/$apiKeyId/edit': {
      preLoaderRoute: typeof AuthBaseLayoutIamApiKeysApiKeyIdEditImport
      parentRoute: typeof AuthBaseLayoutIamApiKeysApiKeyIdImport
    }
    '/_auth/_baseLayout/iam/policies/$policyId/edit': {
      preLoaderRoute: typeof AuthBaseLayoutIamPoliciesPolicyIdEditImport
      parentRoute: typeof AuthBaseLayoutIamPoliciesPolicyIdImport
    }
    '/_auth/_baseLayout/resolvers/instances/$instanceId/edit': {
      preLoaderRoute: typeof AuthBaseLayoutResolversInstancesInstanceIdEditImport
      parentRoute: typeof AuthBaseLayoutResolversInstancesInstanceIdImport
    }
  }
}

// Create and export the route tree

export const routeTree = rootRoute.addChildren([
  AuthRoute.addChildren([
    AuthBaseLayoutRoute.addChildren([
      AuthBaseLayoutAccountEditRoute,
      AuthBaseLayoutIamApiKeysRoute.addChildren([
        AuthBaseLayoutIamApiKeysApiKeyIdRoute.addChildren([
          AuthBaseLayoutIamApiKeysApiKeyIdEditRoute,
        ]),
      ]),
      AuthBaseLayoutIamPoliciesRoute.addChildren([
        AuthBaseLayoutIamPoliciesPolicyIdRoute.addChildren([
          AuthBaseLayoutIamPoliciesPolicyIdEditRoute,
        ]),
        AuthBaseLayoutIamPoliciesAddRoute,
      ]),
      AuthBaseLayoutIamUsersRoute,
      AuthBaseLayoutResolversInstancesRoute.addChildren([
        AuthBaseLayoutResolversInstancesInstanceIdRoute.addChildren([
          AuthBaseLayoutResolversInstancesInstanceIdEditRoute,
        ]),
        AuthBaseLayoutResolversInstancesAddRoute,
      ]),
      AuthBaseLayoutAccountIndexRoute,
      AuthBaseLayoutIamIndexRoute,
      AuthBaseLayoutResolversIndexRoute,
    ]),
  ]),
  AuthenticationLayoutRoute.addChildren([
    AuthenticationLayoutForgotPasswordRoute,
    AuthenticationLayoutLoginRoute,
    AuthenticationLayoutSignUpRoute,
    AuthenticationLayoutVerifyAccountRoute,
  ]),
])

For what it's worth, I was having extreme slowness on TS 4.8, updating to TS 5.1  has drastically sped up type checking.

For what it's worth, I was having extreme slowness on TS 4.8, updating to TS 5.1  has drastically sped up type checking.

Currently on 5.2.2 myself, tried with the latest 5.3 but there is no performance improvement.

Got a smaller performance hit (faster performance compared to previously) by separating the route tree building into separate files
// index.tsx
import rootRoute, { type DashboardAppContext } from './rootRoute';
import { authRoutes } from './authentication';
import { authenticatedRoutes } from './authenticated';
import termsRoute from './termsRoute';

const routeTree = rootRoute.addChildren([authRoutes, authenticatedRoutes, termsRoute]);

export const router = createRouter({
    routeTree,
    // ....

// authentication/index.ts
export const authRoutes = authLayoutRoute.addChildren([
    loginRoute,
    signUpRoute,
    forgotPasswordRoute,
    verifyAccountRoute,
    renewPasswordRoute,
]);

// same for authenticatedRoutes

But still, some hotspots are >1000ms

Optimizations in this area are very welcome, so please, if you find something out, let us know.
Even if those changes would be breaking, we might consider them for v2 if the TS compiler performance can be improved significantly.

I was looking into using Link with a large number of routes. I wonder if this is the same issue I noticed.
Regarding what I looked into when tracing. I found possibly something interesting:
RelativeToAutoComplete has SplitPaths which splits all paths regardless as a defaulted type parameter.  If you make SplitPaths inline so it's only evaluated when it's needed and then when the 'from' prop is not specified (TFrom is defaulted to string) then return all paths without splitting all the paths.  This skips the crazy splitting of a large union of paths. With these changes I noticed significant performance improvements when not using the 'from' prop
I tried this with 600 odd routes and check time went from 12.69s (with excessively deep instantiation errors) to 2.49s (with no errors)
useNavigation is more complicated. It's defaulting TFrom to all paths and this is harder to check for (not sure why it's defaulted this way?). TS seems to checking a large union here as well. I was able to get similar performance as Link if TFrom is defaulted to string and some other odd changes
This doesn't fix performance issues when the 'from' prop is specified. There might be a better way to work out the relative paths. But that requires more work and thinking how to approach it. I would maybe try to avoid parsing of huge unions and try to narrow it down
I usually try not to iterate over large unions unnecessarily and minimise checking against them

sounds super interesting, can you please open a PR so I can have a look?

I raised a PR. Looking into further improvements but this is a good start I think
https://github.com/TanStack/router/pull/1202

This is amazing @chorobin! Just tried it and there is a huge performance gain.

@toteto Glad it helped with your situation. Out of interest, what kind of gains are you seeing?

@schiller-manuel I have some improvements for relative paths as this is still using Split and slower than it could be. Should I raise another issue for this? At least relative pathing should be faster.

definitely, please create a PR
I noticed that relative paths did not have autocomplete working (already broken before your last PR) so if this works again, it would be great

Cool. Yeah. I noticed that. It will work. It might be worth getting tests around these types to stop those sorts of regressions

tests would also be cool 😀

@toteto Glad it helped with your situation. Out of interest, what kind of gains are you seeing?

Would say it cuts down the auto complete and suggests times by at least half. Used to be ~6s now it is sub 2s. Also I have a PR lined up that updates Zodios to v11-beta that also has magnificent performance improvement... So it could be said that this Monday I felt like I got a brand new supercomputer 😅
@schiller-manuel noticed that all the tests are commented out. Any pointers for an effort to bring some of them up?


fixes cluster not starting post kube-aws up

v0.8.0 would not start until I added the requires.

Thanks just tested this and cluster is starting perfectly

Ugh.  We removed this in an attempt to fix this issue, but it looks like it didn't help. https://github.com/coreos/coreos-kubernetes/issues/545.
cc @colhom.

Can confirm that this issue hit my existing cluster. Upon reboot/OS update, the kubelet's depdency chain failed and didn't restart it.

The issue has to do with retry limits of one or more of the various dependencies of kubelet.service. The way to fix this is go through all service dependencies and make sure each is allowed to retry for a very long time / ad infinitum.

@colhom thanks, i'll give that a go when I have a few cycles. Should I close this pull request in that case?

@johnt337 I'll close it out here. When do you think you'll have that PR up?

@colhom if it's still open I'll try and take a look this weekend.

There is a lot of background on (what I believe is) the issue at https://github.com/coreos/coreos-kubernetes/issues/545

Sorry so just getting around to looking into this again.
I see that by default /usr/lib64/systemd/system/flanneld.service is set to type=notify and it contains a --set-env=NOTIFY_SOCKET=/run/systemd/notify \ in it's ExecStart.
Should it be a matter of Wants=docker.service to maintain start order during boot time?


Attempting to connect a GitHub account which already is linked with another account results in a vague error

What
If you attempt to connect a GitHub account which already is linked with another account, you'll get a vague error which hints at an issue with the access token. We should handle this better.

Proposal
We should hint to the user that the account already is linked to someone else.

Will be fixed by #1977! Actually, proper error message was there, but some nasty React re-rendering were submitting the callback twice, so you got the expired/invalid error after (very briefly) seeing the already-linked error.


wagyu: 0.6.1 -> 0.6.3

This also includes a fix for the rustc-serialize build issue.
Description of changes
ZHF: #309482
Currently the package can not be built. However, this PR fixes that.

failed build: https://hydra.nixos.org/build/259447531

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 311947 run on x86_64-linux 1

1 package built:

wagyu

runs fine, fixes https://hydra.nixos.org/build/258475687, LGTM


how to listen on the change of the screen ?rotation

(maybe i know  i look like  i am fool)
i am viewing your code ,i know the aidl listens the phone rotation,but how the pc knows phone is roating?

how the pc knows phone is roating

The PC doesn't know the device rotation.
When the device rotates, it just receives a frame having another dimension, so it resizes itself.
(Note that it would not be sufficient if we would need to draw a device around the video on the client side)

how the pc knows phone is roating

The PC doesn't know the device rotation.
When the device rotates, it just receives a frame having another dimension, so it resizes itself.
(Note that it would not be sufficient if we would need to draw a device around the video on the client side)

you means client auto resize itself when  it receives a frame having another dimension.
But f I only use the scrcpy server, and then use the jmuxer to decode on frontend, how will the frontend listen when the screen is rotated. Only when it is monitored can the jmuxer be reset


_build_serving_image doesn't actually pushes the built image

While reading the source of this project, came across this block of code in the _build_serving_image function. Due to that return in the first line of the quoted segment, the rest of the code (that should do the pushing the image to the registry) is unreachable. I presume it's not intended?
https://github.com/Ark-kun/google_cloud_mlflow/blob/014e3ba09708ef4b33036dd92402d932041e40c6/google_cloud_mlflow/_mlflow_model_gcp_deployment_utils.py#L207-L222

Thank you for reporting this issue.
This dead code was removed on Jan 7 in https://github.com/Ark-kun/google_cloud_mlflow/commit/52ebf42a2ed7d60979ea55152a9e88496155edc8
The image is being pushed to the repository by the preceding code.
If you're interested, here is how the code progressed:

Use MLflow's build process that uses docker CLI
Use docker Python library to push the image
Patch MLflow to build and push image using Cloud Build gcloud CLI
Patch MLflow to build and push image using Cloud Build client library
[prerelease] Use Vertex AI's built-in serving images

Please report any other issues you've found.


Gauge card: update colors to match theme colors

The basic primary colors clash horribly with the themes. Need to define them in the themes so that it looks more cohesive.

Gross:

Discovered via https://github.com/th3jesta/ha-lcars/issues/8

Added the variables to all themes.
Added values appropriate for Default theme to all themes.
SHould be good, but further refinement for individual themes may be necessary or desirable.


Add CDK

https://github.com/kolomied/awesome-cdk
AWS CDK is a popular framework for defining cloud infrastructure in code. There is a vibrant community around the framework that builds solutions on top of it. Having a curated awesome list that mentions the valuable projects would be very helpful.
Reviewed #1832,  #1823

unicorn

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

@sindresorhus Went through the checklist again:

Passed everything through awesome-lint
Added missing descriptions
Header cleanup
Made logo right aligned

Any clues about missing pieces?

@sindresorhus any chance you can review updated repo please?

@kolomied I went through your list and haven't noticed anything, majority of the stuff from your initial pr have been fixed. Descriptions some of them are self explanatory so i don't think you had to "over" explain them but I guess is good that you did it anyway.

The title used throughout should be AWS Cloud Development Kit. Just CDK is not very useful.

@sindresorhus Thanks for the review - I accepted your #readme suggestion.
About AWS Cloud Development Kit vs CDK - I tend to disagree. The acronym is widely used in community, Google searches, etc. I would say that CDK is far more recognizable.
Less importantly - AWS Cloud Development Kit is quite mouthful to be awesome.

@sindresorhus Could you please reconsider the renaming requirement? Any chance we can proceed with this PR?

Hey @kolomied I believe you can leave https://github.com/kolomied/awesome-cdk#contribute off the body of the content and rather use a pull_request_template.md that calls it up to attention at the appropriate moment when someone decide to really make a contribution. I know this has been automatically generated by dar5hak/generator-awesome-list but I'm recommending it anyway.

@n370 Thanks for the suggestion - this is a great idea. Created pull_request_template.md and fixed the name of Contributing section to adhere to the latest awesome-lint release.
@sindresorhus Can you give it another go? I do think the repo is in a good shape now.

@sindresorhus Happy New Year!
Could you please take a look at the awesome-cdk repository and provide some feedback if you think that this PR still shouldn't be merged?

@sindresorhus Happy New Year!
Could you please take a look at the awesome-cdk repository and provide some feedback if you think that this PR still shouldn't be merged?

Tweet: https://twitter.com/awesome__re/status/1347088862158352389

Tweet: https://twitter.com/awesome__re/status/1347088862158352389


Update SoundCloud Downloader to 2.6.4

Thank you for the contribution. It was merged directly as d708de39e92fcd9e464a0b6755249989e890fc96 to keep commit history cleaner. Your contribution is still credited to you.


Animate accordion carrot to indicate when section is open/closed

Animate the accordion '>' to indicate when a section is open or closed. '^' should point to the right when closed and shift 90 degree down when open.

Closed by #180


How to setup proper environment

@jfkirk This is a very interesting project. I try to setup my local environment and run some basic example code. I have following installed:
Python 3.5.5 :: Anaconda, Inc.
Tensorflow 1.4.1
CUDA 8.0
cudnn 6.0

However, I got following error:
Traceback (most recent call last):
  File "tensorrec_example.py", line 15, in <module>
    model.fit(interactions, user_features, item_features, epochs=5, verbose=True)
  File "/home/trend/.conda/envs/py_3.5/lib/python3.5/site-packages/tensorrec/tensorrec.py", line 533, in fit
    n_sampled_items=n_sampled_items)
  File "/home/trend/.conda/envs/py_3.5/lib/python3.5/site-packages/tensorrec/tensorrec.py", line 601, in fit_partial
    self._build_tf_graph(n_user_features=n_user_features, n_item_features=n_item_features)
  File "/home/trend/.conda/envs/py_3.5/lib/python3.5/site-packages/tensorrec/tensorrec.py", line 488, in _build_tf_graph
    self._record_graph_hook_names()
  File "/home/trend/.conda/envs/py_3.5/lib/python3.5/site-packages/tensorrec/tensorrec.py", line 171, in _record_graph_hook_names
    output_classes = hook._output_classes
AttributeError: 'Iterator' object has no attribute '_output_classes'

Any ideas? Thank you!

Hey @trenddev ! Thanks for checking it out.
I think your problem is a TensorFlow version mismatch. TensorRec currently runs on TensorFlow 1.7.
You can update all of your requirements by downloading requirements.txt and running:
pip install -r requirements.txt

Closing for now -- if you run in to more problems, feel free to re-open this issue.


Crazy CPU usage when running inside Docker

Ebitengine Version
v2.7.8
Operating System

[ ] Windows
[ ] macOS
[X] Linux
[ ] FreeBSD
[ ] OpenBSD
[ ] Android
[ ] iOS
[ ] Nintendo Switch
[ ] PlayStation 5
[ ] Xbox
[ ] Web Browsers

Go Version (go version)
1.22
What steps will reproduce the problem?

Normal CPU usage, the same when its running directly on the host
What happens instead?
When ebiten engine runs inside of a docker container, the CPU usage is extremely high close to 100% in all the CPUs.
Anything else you feel useful to add?
No response

Problem solved. It looks like ebiten needs access to /dev/dri
 docker run -it --rm \
          --device /dev/dri \
          --net=host \
          --env="DISPLAY" \
          ghcr.io/mcuadros/ebiten-environment:1.22-bookworm \
          go run github.com/hajimehoshi/ebiten/v2/examples/2048@latest


Tests for handling data from HEADER tags

Tests for processing HEADER tags when used within span field_mapping.
The following functions to be tested:

handle_data_from_header
find_matching_header_value
get_value_type
add_or_append_value

Outcomes:

Tests written
Tests pass
Tests reviewed and accepted

Due to other functionality being developed this testing is not required now.


Add a complex back-end code sample

Not necesarry for v6. May be created as a Community project sample.


[BIOMAGE-2018] - Add heatmap select data

Description
A user wants to have "Select Data" for the custom heatmap in Plots and Tables. This PR adds that option.
Some feedback from Vicky:

Select Data option should appear after Gene Selection. In doing this, I removed the HeatmapPlotControls component because it's only a wrapper without much value to the added abstraction.
The scratchpad option shown in Select Data should be changed to Custom cell sets, as this is what is shown in Data Exploration. This translation should also be made for some other plots (e.g. frequency and marker heatmap). A fix is introduced in this PR.

Details
URL to issue
https://biomage.atlassian.net/browse/BIOMAGE-2018
Link to staging deployment URL (or set N/A)
https://ui-agi-shaggy-mongoose.scp-staging.biomage.net/
Links to any PRs or resources related to this PR
N/A
Integration test branch
master
Merge checklist
Your changes will be ready for merging after all of the steps below have been completed.
Code updates
Have best practices and ongoing refactors being observed in this PR

[ ] Migrated any selector / reducer used to the new format.

Manual/unit testing

[ ] Tested changes using InfraMock locally or no tests required for change, e.g. Kubernetes chart updates.
[ ] Validated that current unit tests for code work as expected and are sufficient for code coverage or no unit tests required for change, e.g. documentation update.
[ ] Unit tests written or no unit tests required for change, e.g. documentation update.

Integration testing
You must check the box below to run integration tests on the latest commit on your PR branch.
Integration tests have to pass before the PR can be merged. Without checking the box, your PR
will not pass the required status checks for merging.

[ ] Started end-to-end tests on the latest commit.

Documentation updates

[ ] Relevant Github READMEs updated or no GitHub README updates required.
[ ] Relevant Wiki pages created/updated or no Wiki updates required.

Optional

[ ] Staging environment is unstaged before merging.
[ ] Photo of a cute animal attached to this PR.

Really? Is it the marker heatmap in Data Exploration or Plots and Tables? Do you mean not working because it resulted in the wrong display? Or does it not work?
I tested in local and it works if there are custom cell sets under Scratchpad. I tested it in local and it works.

When I switch to custom cellsets the legend still shows the louvain clusters

When I switch to custom cellsets the legend still shows the louvain clusters, and also if there are no custom cell sets it just shows a weird empty plot. Can you make it also show properly that is empty? Like use <Empty> maybe if there are no custom cell sets?

Addressed, added an information text if there are no cell sets.


Xcode11 fixes

Update CI and fix an intermittent test failure.  Add some missing diagnostics.

Codecov Report

Merging #12 into master will decrease coverage by 0.08%.
The diff coverage is 93.33%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
- Coverage   98.51%   98.42%   -0.09%
==========================================
  Files          12       12
  Lines         944      955      +11
==========================================
+ Hits          930      940      +10
- Misses         14       15       +1

Impacted Files
Coverage Δ

Sources/ModelVersionNode.swift
100% <100%> (ø)
:arrow_up:

Sources/Helpers.swift
96.03% <90%> (-0.81%)
:arrow_down:

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 a91a75f...443059c. Read the comment docs.


[a11y] contrast between caption and white to low

In the Cupertino theme the contrast between a white background and the caption text style is only 4.3. It needs to be 4.5 or better.
We currently use black54 for this, but according to spec grey700 (for a contrast ratio of 6) should be used.

What's the theme being referred to here?

@goderbauer can you explain the 4.3 and 4.5 values represent? Also, how can we reproduce these values on our end so that we can be sure we don't violate this again moving forward?
Also, the current values are based on iOS specs. Can you elaborate on what requirements/responsibilities we have to diverge from such specs for accessibility requirements?

You can check the contrast ratio between two colors here: https://contrast-ratio.com/

We also have the ability to write automated tests to check contrast ratios, see: https://github.com/flutter/flutter/blob/master/examples/flutter_gallery/test/accessibility_test.dart#L473

Can you point to what in the CupertinoThemeData or CupertinoTextThemeData are you referring to as the captions text style?

Not sure where to look and need more explanation such as https://github.com/flutter/flutter/issues/16397#issuecomment-481463678


chore: update changelog

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 78.97%. Comparing base (4a4687c) to head (f2aa88a).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #246   +/-   ##
=======================================
  Coverage   78.97%   78.97%
=======================================
  Files          52       52
  Lines        6834     6834
=======================================
  Hits         5397     5397
  Misses       1437     1437

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


Fix tetris line score bug

There is a bug in the Tetris classic game. If you manage to place the pieces in such a way where more than one line is going to be deleted, then the game indeed deleted the correct amount of lines but it doesn't update the score appropriately. The score lines are only updated by 1 increment. This PR addresses this issue.

@drpaneas Thank you very much for the review! Those classic games were not reviewed in some years!


Bug: Renaming Variables Longer than Indent Causes Error with Preview

Hello! I love this plugin!
There seems to be an issue when renaming variables that are longer than the indent, as shown in the video.
https://github.com/smjonas/inc-rename.nvim/assets/44737273/ebdbd835-b819-40c0-b24f-79e145d59938
$ nvim --version
NVIM v0.9.1
Build type: Release
LuaJIT 2.1.0-beta3

My neovim config at the time of reporting this issue: https://github.com/DrPoppyseed/config/tree/a88db7befae3985fcfd9998b10cf6f11998ad82d/dot_config/nvim

Thanks for reporting, should be fixed now :)


Question: How does the demo app decide content is live?

I am attempting to test HLS Live playback in shaka player, and I cant get the time display or seek bar to show a Live Content state.
Example.
Note* that is referencing controls.css, muxjs, and skaka-player.ui.js from the demo site.
Viewing the same content on the demo site does show a Live state as I would expect.
Demo site.
I have compared the player and ui configurations, and other than a close button and a dash.clockSyncUrl in the demo site, I can't see any differences.

In your example, you constructed a new player:
  <div id="player-container" data-shaka-player-container>
    <video data-shaka-player></video>
  </div>

    window.addEventListener('load', function(){
      shaka.polyfill.installAll();

      var p = document.querySelector('video');
      var player = new shaka.Player(p);

      player.configure({
        "preferredAudioLanguage": "en-NZ",
        "preferredTextLanguage": "en-NZ",
      });

      player.load('https://akamai-axtest.akamaized.net/routes/lapd-v1-acceptance/www_c4/Manifest.m3u8');
    });

But the UI library had already created a Player instance and attached it to the video.  You essentially forced it to detach and hijacked the video element with a player that's not connected to the UI controls.
Instead, you should use the player instance constructed by the UI library:
  document.addEventListener('shaka-ui-loaded', function() {
    controls = document.querySelector('video').ui.getControls();
    player = controls.getPlayer();
    player.load('https://akamai-axtest.akamaized.net/routes/lapd-v1-acceptance/www_c4/Manifest.m3u8');
  });

That worked a treat, thank you @joeyparrish

My pleasure.  Glad we could help!


Node face compare demo not working with TS

Issue Description
I'm trying to run the demo/node-face-compare.js script, but I have migrated it to TS. However, TypeScript is complaining about the type of the tensor with the following error:
Argument of type 'Tensor3D | Tensor4D' is not assignable to parameter of type 'TNetInput'.
  Type 'Tensor3D' is not assignable to type 'TNetInput'.
    Type 'Tensor<Rank.R3>' is not assignable to type 'Tensor4D'.
      Types of property 'shape' are incompatible.
        Type '[number, number, number]' is not assignable to type '[number, number, number, number]'.
          Source has 3 element(s) but target requires 4.ts(2345)

Image for reference:

Steps to Reproduce
Try to run this script with ts-node or something.
Expected Behavior
To work, I guess, I suppose this is an issue with the types.
Environment

Module version? @vladmandic/face-api": "^1.7.8 and "@tensorflow/tfjs-node": "^4.2.0".
Built-in demo or custom code? Demo, but with TS instead of JS.
Type of module used (e.g. js, esm, esm-nobundle)? CommonJS.
Browser or NodeJS and version (e.g. NodeJS 14.15 or Chrome 89)? NodeJS v18.12.1.
OS and Hardware platform (e.g. Windows 10, Ubuntu Linux on x64, Android 10)? 5.19.17-2-MANJARO.
Packager (if any) (e.g, webpack, rollup, parcel, esbuild, etc.)? No, only tsc and ts-node executing it directly.

i'm going to assume this is similar to other issue you've just created - https://github.com/vladmandic/human/issues/328
make sure that models are actually correctly loaded, not just last error message.

In fact, this isn't similar, this is just a type error.

ok, i'll take a look

i just tried to reproduce using your script and it works just fine here - i guess it up to project setup - please share full reproduction project that i can just clone (tsconfig.json & package.json are key)

any updates?

Hi there, last week was crazy for me, did not have time to check it, I will review it right away. Sorry for the delay.

Here is the repo with the issue.

ok, i see what the issue is, but i don't see a way to resolve it without major change on how face-api is built.
the error is misleading, the  core issue is that Tensor type signatures are not the same in @tensorflow/tfjs (browser package) and @tensorflow/tfjs-node (nodejs package)
you can confirm by basically doing:
const tensor = tf.node.decodeImage(buffer, 3) as faceApi.tf.Tensor3D

easiest temporary solution is to relax that typecheck:
  const faces = await faceApi.detectAllFaces(tensor as any, optionsSSDMobileNet)

extracting and bundling different typedefs for different flavors of tfjs during faceapi build would be out-of-scope for now. i did restructure some typedefs, so do a git pull anyhow.
btw, off-topic, but if you're building for node and using esm, you may want to import node flavor of faceapi explictly as its auto import resolver may pick browser esm version:
import faceApi from<EMAIL_ADDRESS>

as per previous note, i'm closing the issue as its cosmetic only and full fix would be out of scope for now.


update health card display styling

Made some changes to design -

Left out SMART logo since we do not have permissions to use this yet.
Left out dose numbering, immunizations may not be complete or in order so this could be confusing/inaccurate.
Removed COVID-19 from label since we are not filtering immunization entries by COVID codes.

Looks pretty good. Only issue I see is when the lot number is really long some of the text gets cut off.


Fix typo

a -> an

@changeworld : Thanks for your contribution! The author, @alch-msft, has been notified to review your proposed change.

Merging typo fix.
@changeworld Thank you.


Python: how to create spreadsheet column with validation list

On the website, you can create a Quip spreadsheet and set certain columns to present a popup with a validated list of items. For example, column A of each row could be "Yes" or "No" values and column B could be the names of US state. You can even assign colors to each menu item. Column three could be a free-form chunk of text.
I'm looking to programmatically take output from a database and create these via the Python API. Doesn't have to be python. Just wondering if this capability is exposed via the API.
Any way to do this?

Any updates on this issue? I am implementing a Python app that populates a Quip spreadsheet with rows that contain a cell that ideally should have Data Validation (Green, Yellow, Red). Is it possible to apply Data Validation to a cell via the API?
I setup a Quip spreadsheet that includes the required Data Validation, and then got the thread. Even then I did not see how the Data Validation is stored/applied. Is it even possible to view the Data Validation for a cell via the API?

Is anyone ever going to answer this question?  I've seen it posted a few times on here...


CI: bump Rust to 1.74.1

coverage: 59.9%. remained the same
when pulling 4932653e304b3919dd4cbf9bb868470889c6e71f on feature/ci-bump-rust
into 7c402a4ffe9bd2a82fd91a76c1b21a16f147802a on master.


Update user_info.dart

allow covert UserInfo object to map, easier debug for developers
Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[ ] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] The analyzer (flutter analyze) does not report any problems on my PR.
[ ] I read and followed the Flutter Style Guide.
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[ ] I updated CHANGELOG.md to add a description of the change.
[ ] I signed the CLA.
[ ] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[ ] No, this is not a breaking change.

@ferso  Thanks for the PR, we have an update to auth coming up and I think this should fit nicely into that. I'll merge this but it will not be published till our larger auth update is ready.

@googlebot I signed it!
On Tue, Jul 28, 2020 at 9:07 AM Arthur Thompson<EMAIL_ADDRESS>wrote:

Merged #3040 https://github.com/FirebaseExtended/flutterfire/pull/3040
into master.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FirebaseExtended/flutterfire/pull/3040#event-3594541257,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADHDVRP6XYYYOB57ZWBQ73R53LTLANCNFSM4PKHZWXA
.

This is actually a breaking change for child objects that implement UserInfo which might be something to include in the changelog – had to roll forward when pulling this change internally.


Migrate scrapy to headless-chrome?

A few weeks ago, the chromium project announced headless chromium as new, clean way to open websites in a non-UI server context.
The announcement had quite an impact in the headless-browser scene and resulted in the resignment of the phantomJS maintainer.
Since the current webkit engine of Splash dates back to 2013, I wanted to know whether there are any plans to port splash to headless chrome?

will take a lot of work, i guess

Webkit is upgraded to a much more recent version in Splash master (~Safari in mid-2016), and will be upgraded further (to Webkit trunk) in future, thanks to https://github.com/annulen/webkit. You can use scrapinghub/splash:master Docker image to try the changes, or wait for Splash 3.0 release.
Switching to Headless Chromium would be a huge change indeed. We don't have engineering resources to make this switch in a near future. Also, it may be easier to create a separate Scrapy + Headless Chromium intergation project.
Switching to Headless Chromium has both advantages and disadvantages; it seems there are more advantages. But some Splash features can't be implemented in Headless Chromium AFAIK - e.g. per-request proxy options are impossible if I'm not mistaken (this feature is nice to have e.g. for Crawlera integration, to avoid using Crawlera for static resources).

Thanks! Will try the master container to see if I can get around my scraping issues.

got the following error when trying out the master dockerfile:
$ docker pull scrapinghub/splash:master
master: Pulling from scrapinghub/splash
75c416ea735c: Pulling fs layer
c6ff40b6d658: Pulling fs layer
a7050fc1f338: Pulling fs layer
f0ffb5cf6ba9: Waiting
be232718519c: Waiting
02e48393bcae: Waiting
a699b90bbc99: Waiting
41da8db2bf8f: Waiting
ba57071e497d: Waiting
55c87f8bb02f: Waiting
error pulling image configuration: Get https://dseasb33srnrn.cloudfront.net/regi
stry-v2/docker/registry/v2/blobs/sha256/b3/b3f69a08d665f155a61dad4b436c4112f7580
36e2e5a1d4f97658707829b0d48/data?Expires=1498738729&Signature=BUj4fCBuoG2MDqovD8
9-hQ4UarCvnxIKG7qce0gkS6TC67GLSSR6fw2E1R7anC1iCyiaiA44tIniU0mtA1~HAVhlHjC73iQc3Z
j45ZStlPdSpOutmc4YEsOum33hbxG1Hox53J0CYatrXkOsHyzLqgyKXeU45QVab-Q7Kt2lVrE_&Key-P
air-Id=APKAJECH5M7VWIS5YZ6Q: read tcp <IP_ADDRESS>:46376-><IP_ADDRESS>:443: read: c
onnection reset by peer

Could you try it again? It looks like a temporary issue - either a dockerhub issue, or a network issue.

We 've now successfully tested splash 3.0 and are really impressed: The execution time of our scraping jobs (running layoutstats,js on ~ 120 URLs) dropped from approx 75 minutes to just 25 minutes :-) Taking screenshots also seems to work more reliable now. Big kudos to you and the guys behind the "Chromium 2016" port!


Add voxel palette editor plugin

Description

Added voxel palette editor plugin.
Added the plugin to tesseratos sample.
Implemented equality operator for AnyAsset

Checklist

[x] Self-review changes.
[x] Evaluate impact on the documentation.
[x] Ensure test coverage.
[x] Write new samples.

I think first we should implement #709 since it would be useful here.

LGTM, ty for working on this!


Fix #118 Add bindists for GHC 9.4.3

Follows the approach taken to date for GHC 9.4.1 and GHC 9.4.2.

The script in #122 also passes for this (after adjusting the version):
passed check sha1 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-i386-deb9-linux.tar.xz
passed check sha256 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-i386-deb9-linux.tar.xz
passed check sha1 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-x86_64-deb9-linux.tar.xz
passed check sha256 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-x86_64-deb9-linux.tar.xz
passed check sha1 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-x86_64-fedora33-linux.tar.xz
passed check sha256 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-x86_64-fedora33-linux.tar.xz
passed check sha1 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-x86_64-apple-darwin.tar.bz2
passed check sha256 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-x86_64-apple-darwin.tar.bz2
passed check sha1 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-aarch64-apple-darwin.tar.bz2
passed check sha256 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-aarch64-apple-darwin.tar.bz2
passed check sha1 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-x86_64-unknown-mingw32-int_native.tar.xz
passed check sha256 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-x86_64-unknown-mingw32-int_native.tar.xz
passed check sha1 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-x86_64-unknown-mingw32-int_native.tar.xz
passed check sha256 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-x86_64-unknown-mingw32-int_native.tar.xz
passed check sha1 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-x86_64-unknown-mingw32.tar.xz
passed check sha256 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-x86_64-unknown-mingw32.tar.xz
passed check sha1 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-aarch64-deb10-linux.tar.xz
passed check sha256 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-aarch64-deb10-linux.tar.xz
passed check sha1 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-aarch64-deb10-linux.tar.xz
passed check sha256 https://downloads.haskell.org/~ghc/9.4.3/ghc-9.4.3-aarch64-deb10-linux.tar.xz

I think Debian will work better with Stackage nightly (which is why I approved this). But probably @juhp can speak about the Fedora case

Maybe @hasufell has some more insight on this?

Maybe @hasufell has some more insight on this?
but I think debian10 would be more portable overall

This is where I disagree. I consider debian not portable. Their downstream patches sometimes cause problems, or the way they build libraries.
https://bugzilla.redhat.com/show_bug.cgi?id=1875587
There was a prominent case where they broke Skype for other distros, because they're even messing with SONAMEs sometimes: https://bugs.gentoo.org/415985

I am going to merge this, which follows what Stack originally did for GHC 9.4.1 and GHC 9.4.2, and if something needs fixing (#117 or some other permutation) then it can be applied to all of GHC 9.4.1 to GHC 9.4.3.

It might be that centos7 is a better default bindist choice for Linux?
At least I see on RHEL8 that ghcup causes the centos7 bindists of 9.2.5 and 9.4.3 to be installed.

So also in the Stackage build server environment we are still using Ubuntu 20.04 and the current default 9.4.3 tarball gives
/var/stackage/.stack/programs/x86_64-linux/ghc-tinfo6-9.4.3/lib/ghc-9.4.3/bin/ghc-pkg: /lib/x86_64-linux-gnu/libc.so.6: version `GLI
BC_2.32' not found (required by /var/stackage/.stack/programs/x86_64-linux/ghc-tinfo6-9.4.3/lib/ghc-9.4.3/bin/../lib/x86_64-linux-gh
c-9.4.3/libHSrts-1.0.2-ghc9.4.3.so)

I think it is better to change to centos7, even though that is an older platform than fedora27 (which was roughly rhel/centos 8).

https://gitlab.haskell.org/ghc/ghc/-/issues/22268 is the upstream ticket with related discussion

This also broke Stackage CI in github, but we have worked around it by moving the CI action to use Ubuntu 22.04.
(On the Stackage buildserver I worked around it by manually installing the debian10 bindist by hand into our Ubuntu 20.04 build container environment.)


[Bug]: Multiple Setup/Init Issues

Preflight Checklist

[X] I could not find a solution in the documentation, the existing issues or discussions
[ ] I have joined the ZITADEL chat

Environment
Self-hosted
Version
v2.52.0
Database
PostgreSQL
Database Version
15.4.0
Describe the problem caused by this bug

Not possible to provide the master key using environment variable. There are various options to provide the master key to Zitadel. Out of these options the environment variable one which is not working. Passing the master key as a command line argument works though, but we would prefer using the environment variable.

When changing the password policy to require at least 12 chars long password instead of the default 8 and setting the initial admin password to e.g. deadbeefdeadbeef for the zitadel-admin user the following error is received on init:

time="2024-05-26T06:06:27Z" level=error msg="migration failed" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:68" error="ID=COMMA-HuJf6 Message=Errors.User.PasswordComplexityPolicy.MinLength" name=03_default_instance
time="2024-05-26T06:06:27Z" level=fatal msg="migration failed" caller="/home/runner/work/zitadel/zitadel/cmd/setup/setup.go:210" error="ID=COMMA-HuJf6 Message=Errors.User.PasswordComplexityPolicy.MinLength" name=03_default_instance

The initial password provided clearly meets the MinLength requirement set, though.
To reproduce
See problem description.
Screenshots
No response
Expected behavior

Setting the master key using the environment variable works.
When using a custom password policy and providing a compliant initial admin password the init does not fail and login is possible.

Operating System
Single pod, single container with container image ghcr.io/zitadel/zitadel:v2.52.0 running on latest k3s cluster.
Relevant Configuration
No response
Additional Context
No response

Hi @ad-zsolt-imre, would you confirm me the scope of this issue? Are you using Zitadel helm chart or any other way to try to use the environment variable?

Hi @doncicuto . I'm not using the Zitadel helm chart. I wanted to put a simple deployment manifest together for Zitadel and that's how I noticed the behaviour in the description of the issue.
Basically what I'm doing is that I'm passing the ZITADEL_MASTERKEY env var to the Zitadel container. Snippet from the deployment manifest:
          env:
            - name: ZITADEL_MASTERKEY
               value: deadbeefdeadbeefdeadbeefdeadbeef

Thanks @ad-zsolt-imre. Are you passing the following flag
--masterkeyFromEnv         read masterkey for en/decryption keys from environment variable (ZITADEL_MASTERKEY)
to the zitadel setup/start command?

@doncicuto  Ah, no, I did not. Sorry, it seems I missed that completely. Thanks a lot for pointing out. I will update and test once I have time again.
Regarding the password policy issue, do you have any suggestions?

Perfect for the first part of the issue :smile:. I'll try to test the password policy issue and let you know @ad-zsolt-imre

Hi again @ad-zsolt-imre. Can you paste another snippet from your deployment manifest or the Zitadel config yaml part that sets your admin password and also the one that sets the custom password complexity policy to have a min lenght of 12?
For the error message you've provided and checked against the source code, either the password is not being passed correctly (from an env?) and assumed to be empty or there's an issue with the password complexity setting.

The MinLength of the password complexity policy is below:
  PasswordComplexityPolicy:
    MinLength: 12 # ZITADEL_DEFAULTINSTANCE_PASSWORDCOMPLEXITYPOLICY_MINLENGTH

A snippet from the configmap I used:
        Human:
          # In case that UserLoginMustBeDomain is false (default) and if you don't overwrite the username with an email,
          # it will be suffixed by the org domain (org-name + domain from config).
          # for example zitadel-admin in org `My Org` on domain.tld -><EMAIL_ADDRESS>          UserName: zitadel-admin # ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_USERNAME
          FirstName: ZITADEL # ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_FIRSTNAME
          LastName: Admin # ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_LASTNAME
          NickName: # ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_NICKNAME
          DisplayName: # ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_DISPLAYNAME
          Email:
            Address: # ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_EMAIL_ADDRESS
            Verified: false # ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_EMAIL_VERIFIED
          PreferredLanguage: en # ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_PREFERREDLANGUAGE
          Gender: # ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_GENDER
          Phone:
            Number: # ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_PHONE_NUMBER
            Verified: # ZITADEL_DEFAULTINSTANCE_ORG_HUMAN_PHONE_VERIFIED
          Password: {{ .Values.services.zitadel.defaultAdminPassword }}

I can confirm {{ .Values.services.zitadel.defaultAdminPassword }} yielded the deadbeefdeadbeef.


[1.4] Idempotent Kafka secret creation in e2e tests

Backport of https://github.com/knative-sandbox/eventing-kafka/pull/1277

YOLO


Nothing work

I put the PS3_GAME folder inside the folder and when i launch make_pkg.bat, i have nothing :(, any solution ?

some logs will help.
but try rename folder to title_id

It work thanks but on question, it can convert cfw backup to ofw to work with the new package manager for PS3 4xxxx ?

Yes, you can. other tool: https://github.com/friendlyanon/CFW2OFW-Helper

But we need a HAN Enabler to play this game ?

Only install need HAN


Decode String in Java

Related Issue
Closes: #730
Describe the changes you've made
Added the Java source code file for the problem Decode String
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
NA
Language used for coding
Java
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have documented the code.
[x] New and existing unit tests pass locally with my changes.

Have you solved two issues in one?

Sorry, I didn't realise it. I'll make the changes rightaway

I'll reopen another PR and add the code


CP-SAT: Performance drops from 60s to 700s - why?

Hello all
First of all, thanks to the hard working team for providing CP-SAT as open source project. It looks very promising.
I am investigating whether CP-SAT could serve as solver component for our nurse shift scheduling solution. I used your following shift scheduling example as a basis for a prototype:
https://github.com/google/or-tools/blob/master/examples/dotnet/ShiftSchedulingSat.cs
CP-SAT looks very promising so far but I am running into performance problems with the prototype we built.
The problem:
Adding an additional type of constraint ("cover constraint") caused a drop in solving performance from roughly 1 minute to roughly 12 minutes. I am not an expert in constraint programming but I do have the impression that a drop by 12x is way too high.
The additional constraint:
            // Cover constraints
            foreach (int s in Range(numShifts))
            {
                foreach (int w in Range(numWeeks))
                {
                    foreach (int d in Range(7))
                    {
                        var works = new List<IntVar>();
                        foreach (int e in Range(numEmployees))
                        {
                            if(work[e, s, w * 7 + d] != null)
                                works.Add(work[e, s, w * 7 + d]);
                        }
                        IntVar[] wa = works.ToArray();

                        var optDemand = weeklyCoverDemands[d, s];
                        optDemand = Math.Min(numEmployees, optDemand);

                        if (optDemand > 0)
                            model.Add(wa.Sum() <= optDemand); // don't staff more people than optimal-demand
                    }
                }
            }

A longer code snippet from the prototype can be seen here:
https://pastebin.com/ssWUTH8F
My question:

Is this performance drop to be expected - is it by design of CP-SAT?
Can I improve/fix my code to reduce the performance drop?

Thank you very much for your insights!
Best regards,
Adrian

You are adding a lot of constraints, no? And you are making the problem much harder.
The model already penalyze over-capacity.
Why don't you just try to increase the over-capacity penalty?

Hello Laurent
No there is no other excess penalty.
Yes, my model contains roughly 80 nurses and 30 shifts so it ends up adding more constraints than the original example.
Compared to a real life case however the constraints are very few. A real life case will easily contain additional 15 different types of constraints.
I am currently using a TabuSearch algorithm that yields "ok" results in 2 minutes.
Are there any tools available that would help me troubleshoot and profile cp-sat performance in my prototype?
Thanks,
Adrian

There is:
https://github.com/google/or-tools/blob/master/examples/dotnet/ShiftSchedulingSat.cs#L117
currently the model allow excess shifts, but penalizes them.
Your model forbids any excess.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le lun. 4 mars 2019 à 00:15, adihe<EMAIL_ADDRESS>a écrit :

Hello Laurent
No there is no other excess penalty.
Yes, my model contains roughly 80 nurses and 30 shifts so it ends up
adding more constraints than the original example.
Compared to a real life case however the constraints are very few. A real
life case will easily contain additional 15 different types of constraints.
I am currently using a TabuSearch algorithm that yields "ok" results in 2
minutes.
Are there any tools available that would help me troubleshoot and profile
cp-sat performance in my prototype?
Thanks,
Adrian
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1102#issuecomment-469059530,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKj17Twh9jABbDAarxDRPsloYixjXEMDks5vTC1RgaJpZM4baT-V
.

About testing the model, not much.
You can have a look at number of branches per seconds to estimate how heavy
the model is.
Can you try adding parallelism
solver.StringParameters = "numSearchWorkers:8";
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le lun. 4 mars 2019 à 09:32, Laurent Perron<EMAIL_ADDRESS>a écrit :

There is:
https://github.com/google/or-tools/blob/master/examples/dotnet/ShiftSchedulingSat.cs#L117
currently the model allow excess shifts, but penalizes them.
Your model forbids any excess.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68
53 00
Le lun. 4 mars 2019 à 00:15, adihe<EMAIL_ADDRESS>a écrit :

Hello Laurent
No there is no other excess penalty.
Yes, my model contains roughly 80 nurses and 30 shifts so it ends up
adding more constraints than the original example.
Compared to a real life case however the constraints are very few. A real
life case will easily contain additional 15 different types of constraints.
I am currently using a TabuSearch algorithm that yields "ok" results in 2
minutes.
Are there any tools available that would help me troubleshoot and profile
cp-sat performance in my prototype?
Thanks,
Adrian
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1102#issuecomment-469059530,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKj17Twh9jABbDAarxDRPsloYixjXEMDks5vTC1RgaJpZM4baT-V
.

Note the string parameters to enable parallelism in C# should read
solver.StringParameters = "num_search_workers:8";

Thank you very much for your suggestion, I will try this and get back to you.
BR,
Adrian

The configuration change "num_search_workers:8" did not help, the performance dropped further.
I rewrote the prototype in large parts and the problem has gone since. Unfortunately I cannot tell exactly why it has gone.
So far I came up with the following rules of thumb regarding designing cp-sat models for good performance, some of them of course rather obvious:

Keep the amount of variables and constraints as low as possible
Keep value range of each variable as narrow as possible and prefer boolean variables over int variables
Constrain the sum of variables (e.g. works.sum() ==0) instead of constraining each individual variable (e.g. work[e,s,d] == 0)
Replace constraints (e.g. model.Add()) by optimization function (e.g. model.Minimize(xyz)) wherever possible
Prefer approaches with a AddBoolOr constraint over approaches that use constraints with OnlyEnforceIf
Precalculate your model to make sure that you don't create contraints that are impossible to hit (I found that CP-SAT does not do this automatically yet)
Segregate problem into smaller problems and merge the results - if possible
Structure your problem into steps that are easy to turn on/off in order to troubleshoot constraints that cause performance impacts

Any comments on this?
Do you have any further general performance recommendations?

Good summary of how to write a good model :-)
A few comments:

Prefer approaches with a AddBoolOr constraint over approaches that use
constraints with OnlyEnforceIf

I would rephrase that as: prefer boolean constraints over other integer
constraints.
I do not understand:

Precalculate your model to make sure that you don't create contraints
that are impossible to hit (I found that CP-SAT does not do this
automatically yet)

About recommendations, modeling is an art and we have very little
background on modeling with CP-SAT.
Good job.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mar. 12 mars 2019 à 10:27, adihe<EMAIL_ADDRESS>a écrit :

The configuration change "num_search_workers:8" did not help, the
performance dropped further.
I rewrote the prototype in large parts and the problem has gone since.
Unfortunately I cannot tell exactly why it has gone.
So far I came up with the following rules of thumb regarding designing
cp-sat models for good performance, some of them of course rather obvious:

Keep the amount of variables and constraints as low as possible
Keep value range of each variable as narrow as possible and prefer
boolean variables over int variables
Constrain the sum of variables (e.g. works.sum() ==0) instead of
constraining each individual variable (e.g. work[e,s,d] == 0)
Replace constraints (e.g. model.Add()) by optimization function
(e.g. model.Minimize(xyz)) wherever possible
Prefer approaches with a AddBoolOr constraint over approaches that
use constraints with OnlyEnforceIf
Precalculate your model to make sure that you don't create
contraints that are impossible to hit (I found that CP-SAT does not do this
automatically yet)
Segregate problem into smaller problems and merge the results - if
possible
Structure your problem into steps that are easy to turn on/off in
order to troubleshoot constraints that cause performance impacts

Any comments on this?
Do you have any further general performance recommendations?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1102#issuecomment-471918071,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKj17WL3WwrFryP_-JsU5Zq9WHEvKuwFks5vV3LlgaJpZM4baT-V
.

Hi Laurent
Thanks!
Let me explain what I meant by that bullet. Imagine the nurse scheduling problem. You have a model and you feed data (nurses,shifts,fixed assignments,etc) into it. If you analyze the data you might figure out that some nurses do have a day off each Friday/Saturday/Sunday and therefore these particular nurses do not need constraints such as "shift X not longer than 4 days in a row". So you can reduce the number of constraints by preprocessing/analyzing the data.

Yes, but just solving wise, I am not sure it is worth the effort :-)
But, doing analysis on all the solutions are always worth it.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le ven. 15 mars 2019 à 06:00, adihe<EMAIL_ADDRESS>a écrit :

Hi Laurent
Thanks!
Let me explain what I meant by that bullet. Imagine the nurse scheduling
problem. You have a model and you feed data (nurses,shifts,fixed
assignments,etc) into it. If you analyze the data you might figure out that
some nurses do have a day off each Friday/Saturday/Sunday and therefore
these particular nurses do not need constraints such as "shift X not longer
than 4 days in a row". So you can reduce the number of constraints by
preprocessing/analyzing the data.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1102#issuecomment-473159433,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKj17dL4ODpnv13BhhtMLkvI4twIKqk5ks5vWyjUgaJpZM4baT-V
.

Replace constraints (e.g. model.Add()) by optimization function (e.g. model.Minimize(xyz)) wherever possible

Update on this:
If the constraint significantly reduces the solution space it may be worth implementing it as a hard constraint (such as model.Add(..)) instead of optimization function (e.g. model.Minimize(xyz)). I am using a technique where I solve the model first with a hard constraint approach and if I get a an infeasible solution I perform a fallback and solve again with the optimization function instead. You could call this technique "hard-constraint-relaxation". It improves overall performance in case you have many sub-models where only few of them will require a fallback retry.

Hi,
Is this still active ?
Have you tried with 7.2 ?
Thanks

It is resolved. Thank you.

Keep the amount of variables and constraints as low as possible

In thoery, in constraint programming adding new constraints leads to faster solutions. What's your take on this in practice using or-tools ?

This is not always true. Additional constraints can help if they propagate,
can slow down if they are expensive and ineffective.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mar. 10 nov. 2020 à 19:53, zarglayoun<EMAIL_ADDRESS>a
écrit :

Keep the amount of variables and constraints as low as possible

In thoery, in constraint programming adding new constraints leads to
faster solutions. What's your take on this in practice using or-tools ?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1102#issuecomment-724896466,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUPL3I7Z7FD5YE6EJYCRVTSPGDZLANCNFSM4G3JH6KQ
.

Do you have an example when adding aome constraints the problem take more time to be solved (assuming that the number of variables does not change).

hh

hh


Short solution needed: "Lua and Redis usage example" (lua-redis)

Please help us write most modern and shortest code solution for this issue:
Lua and Redis usage example (technology: lua-redis)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

Lua and Redis usage example


highlight.js for themeStyle=dark & modal fixes

Default highlight.js theme has light background that is not that nice for dark theme. Probably, tomorrow-night is not the best option in visual terms, I've just picked random dark theme as it was better than default.
To make it possible I had to disable rule .markdown code {background-color:#f4f1bb; color:#111} in dark-style.css as it specifies really light background for code blocks in dark theme. I'm unsure that it's expected style, is it? It's rendered that way:

Thank you @darkk! This brought up a couple important issues.
I agree with your changes to the modals.
Since Hugo 0.28, Chroma for syntax highlighting has been built in. This has advantages in that no highlight js is required to easily pick a highlight theme. I've made changes to the config that lets you choose a theme using pygmentsStyle (Chroma and Pygments share config options).
Because of a conflict with Bulma (which I use to build some of the css) Chroma is not affecting the code. Temporarily I've set some variables to make those bits more amenable to the light/dark theme.

@hivickylai thank! Yes, I'm aware of pygments / chroma but I thought that highlight.js is a conscious choice based on some limitation or something else, but I've not managed to understand the reason for that from minified CSS :)
Thanks for sharing!


sessions: new: fix error

/cc @juanignaciosl :eyes:

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)


Add test for .softmax.argmax

Issue: #3552

Should I skip PYTHON with .skipIf or add it to the test.yaml file?

Is PYTHON broken too?

Yup, getting same answer as CLANG also


Improved stresstest

To test all algorithms on different data.

Wait, why would you convert all of those innocent spaces to tabs? :(

Innocent, hah! =)
Well, I'm much more used to tabs than spaces.
Is there a problem with that?

The problem is that there isn't a consistent definition of how many spaces
are in a tab.  I keep all of my text editors set to 2 spaces per tab, and I
automatically convert all tabs to spaces.  But obviously, there are severe
disagreements.
See
http://www.codinghorror.com/blog/2009/04/death-to-the-space-infidels.html
I prefer spaces strongly.  However, if you feel differently, that's fine.
I'll just create a new commit after I merge this one to convert them all
back. :)
(If you are going to update your pull request, that's fine.  I'll wait a
little bit before merging.)
--Christopher
On Sat, Feb 25, 2012 at 13:15, Antony Dovgal <
<EMAIL_ADDRESS>
wrote:

Innocent, hah! =)
Well, I'm much more used to tabs than spaces.
Is there a problem with that?

Reply to this email directly or view it on GitHub:
https://github.com/swenson/sort/pull/6#issuecomment-4174769

Reverted that patch.

The problem is that there isn't a consistent definition of how many spaces are in a
tab.
Exactly.
YOU can adjust that setting as you like and others can use, say, 3 spaces for a Tab, while you can't change the number of spaces you use for spaces, apparently.

Yes. But it makes it hard to use both (like when trying to get fine-grained alignment of, say, command-line arguments, or comments).
Merging now. Thanks!


invalid constraint expression reported on apply instead of create

EdgeDB Version: 2.8+afca054
EdgeDB CLI Version: 2.3.0-dev.895+cba06af
OS Version: ubuntu 22.04

The following schema doesn't generate errors on migration create, but it produces edgedb error: UnsupportedFeatureError: set returning operator <QualName std::DISTINCT> is not supported in simple expressions on migration apply. It seems like this could be detected at create time instead.
module default {
  type MyThing {
    property traits -> array<str> {
      constraint expression on (array_agg(distinct array_unpack(__subject__)) = __subject__)
    }
  };
}

Yeah there are a lot of similar errors we should detect at create time.
We should also probably avoid the QualName turd


⚠ Bofrost.at has degraded performance

In 80ba9bf, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1538 ms

Resolved: Bofrost.at performance has improved in 73063da after 13 minutes.


chore:make file to build asset count and releated asset zip files

to build and push asset count and related asset make file

Merging this to test pipeline
@plyubich


Microsoft SQL Server hooks and operators

Microsoft SQL Server Hook
Microsoft SQL Server Operator
SQL Server to Hive Operator

@mistercrunch found an issue which I need to resolve before moving on this PR ... Always using mssql_default for some reason ... must of missed something when trying to utilize the new dbapi class.

@mistercrunch issue has been corrected ... should be good for review

Looks great. A few pointers to add doc entries here:
https://github.com/airbnb/airflow/blame/master/docs/code.rst#L53
and here:
https://github.com/airbnb/airflow/blame/master/docs/installation.rst#L26

@mistercrunch corrections and doc have been added to the PR. Ill work on moving the limit logic to the dbapi hook some time this week.

As long as the goal is to get data OUT OF mssql, then it's ok

:+1:

@mistercrunch rebased with master to resolve merge conflicts

This triggered and interesting unrelated bug... Somehow since a previous refactor some operators depend on others (CheckOperators). Since order coming out of a dict is somewhat random, adding a new item in the dict in operators/__init__.py triggered things to come through in a different order where the dependency wasn't met. Anyhow, I pushed fix for this, I should be able to merge once the unit tests are all done.


'container example' link is wrong in wiki/config

'container example' link is broken in https://github.com/Annoraaq/phaser-grid-movement-plugin/wiki/Config

Good catch! Thank you. It is fixed now 👍


chore(main): release 3.66.0

:robot: I have created a release beep boop
3.66.0 (2024-09-21)
Features

icons: Update Lucide to https://github.com/lucide-icons/lucide/releases/tag/0.445.0 (c8db3e7)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v3.66.0
:sunflower:


is operator: mention C# version for patterns

Fixes #27448
/cc: @trivalik

The change does not touch the snippet ":::code language="csharp" source="snippets/shared/IsOperator.cs" id="IntroExample":::" or the sentence in front of it.


Character Error Portuguese (pt-br)

OS: Windows 10
Issue Descriptions: See attached image. Accented characters not properly showing.
Steps to Reproduce: n/a

This appears to be an issue with your system fonts?  Do other programs (in particular chrome) support / render these characters correctly.

Nope. This only happens when using GPMDP.

Ah, looks like I need to pull in an extended verson of Roboto to get these characters

Happens in Linux too:

Note that it only happens in the strings from gmpdp itself, the strings from Google Play Music webpage shows fine.

This issue has been added to the 4.0.0 milestone.
What does this mean?
It means that the next major release should contain this feature / bugfix.  If you are responsible for this issue please ensure that it is fully up to date to give me the best change of implementing / fixing what needs to be done.
What do you need to do?
If the issue is tagged with "Awaiting Response" it means that I need something from you, be that more information or in some cases a PR with the issue resolution 👍 .  Just do whatever you can to help me sort it out.
So when will this glorious 4.0.0 release come out?
Who knows... 😆  The major component of 4.0.0 is a rewrite of ALL the renderer process code and logic into a React based toolkit that I am creating from scratch over in #1581 .  Subscribe there for more updates as 4.0.0 will not be released until that is merged.


Chunks array is empty

In line 114, it's supposed to say 'dataavaiable'. The package currently listens to the event 'dataAvailable' which causes the bug.

Could you fork and make that change and do a pull request? That way you get credit for the fix in the commit history.


Issue in LAB_08_explore_mcas.md

Lab/Demo: 08
Task: 01
Step: 09
Description of issue: App connector is not available.
As per the Lab guide, there should be app connector in the setting cog icon but it is not available there which is effecting Task 2 and Task 3 as well.

hi Ritu786:  thank you for your comment.  I have re-checked the in Microsoft 365 tenant used for the SC900 labs (available through an authorized lab hoster) and app connector is shown, per the image below.  If you are using a different tenant you may see different information.  If you have other questions/issues please advise.  thanks!


AQCU-1733: remove unnecessary code actually impacting whether or not …

…approval bars drew when multiple time series are plotted
And adjust logic of the R markdown to only display the header details when appropriate (excluding discrete and min max)

Weird formatting not in line with the rest of json document. Not a big deal

Coverage decreased (-0.004%) to 97.111% when pulling 0ccbabe71bb098e24cedf353067d2bc1fed760f3 on mhines-usgs:AQCU-1733 into eeb5e55835107d2b07850fce1954eddffad7e5f0 on USGS-R:master.

@isuftin I think I fixed it, but if you still see something funky let me know


changed version of cli dependency to more secure

The previous version of the dependency is unsafe, more info:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809252
Tested with nsp: https://github.com/nodesecurity/nsp

Thank you! 😺


[UI] unnecessary check when to switch username or password.

Done and close this one. @wy65701436


Facility specific messaging added to GOLDEN EARS DUP confirmation pages

Description:
As a Garibaldi visitor, I want to get park specific information so that I can be better prepared.
As a bc parks staff, I want to provide park specific information after a user has booked a day use pass so they can be better prepared. This is part of responsible recreation messaging.
Acceptance Criteria:

[ ] Update Garibaldi confirmation pages with approved text and links
[ ]

Development Checklist:

[ ] ...
[ ] ...
[ ] ...

Dependencies

Blocked by #400
Blocking

Relevant documentation as reference
Definition of Ready

[ ] Acceptance criteria are included
[ ] Wireframes are included (if applicable)
[ ] Design / Solution is accepted by Product Owner (if applicable)
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

Definition of Done

In progress:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] UI meets accessibility requirements
[ ] Unit tests are written
[ ] Work is traceable in GitHub
[ ] PR linked to ticket number
[ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment

Code review:

[ ] Code is peer reviewed and has passed CI/CD tests

QA:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] Code is potentially shippable to the production environment
[ ] Functional features have been tested and passed by QA
[ ] UI components tested by designer
[ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)

PO Review:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] Reviewed and approved by Product Owner

Notes:

Question on whether this should be a user story?

November 21, 2024 - DUP prioritization session. This ticket/issue was identified as high priority. Due date will be for the pre-May LW.
https://app.mural.co/t/bcparks2575/m/bcparks2575/1729124366479/8adea59d9e76fb3eb1e33395f1c1857a8c07fb7b