Slow Tests

I'm submitting this issue because I believe there to be a problem with the test suite that is really hindering the contributor developer experience, plus there could be a more serious underlying problem that could be causing this.
I don't believe the specs on my machine to be amazing but nor do I believe them to be low end and I have run test suites, including integrations, of similar size before with no problem.
I'm using the provided docker-compose file in the docker dir. - This is using about 2GB of ram.
 Did you forget to wait for something async in your test?
    Attempted to log "warning In order to use "@prisma/client", please install Prisma CLI. You can install it with "npm add -D prisma".".

      93 |
      94 |   if (!localPath && !installedGlobally) {
    > 95 |     console.error(
         |             ^
      96 |       `${c.yellow(
      97 |         'warning',
      98 |       )} In order to use "@prisma/client", please install Prisma CLI. You can install it with "npm add -D prisma".`,

      at console.error (../../node_modules/.pnpm/@jest+console@27.5.1/node_modules/@jest/console/build/BufferedConsole.js:163:10)
      at main (scripts/postinstall.js:95:13)

Shortly after this, I'm getting a few more passing tests then an error stating that there is many instances of Prisma client constructed:
PASS  src/__tests__/aggregate.test.ts
 PASS  src/__tests__/resolveDatasources.test.ts
 PASS  src/__tests__/document.test.ts
 PASS  src/__tests__/mergeBy.test.ts
 PASS  src/__tests__/getLogLevel.test.ts
 PASS  src/__tests__/integration/happy/async-hooks/test.ts
 PASS  src/__tests__/integration/happy/signals/test.ts
 PASS  src/__tests__/integration/happy/logging/library.ts
 PASS  src/__tests__/integration/happy/sqlite-variable-limit/test.ts (6.585 s)
 PASS  src/__tests__/integration/happy/logging/binary.ts
 PASS  src/__tests__/integration/happy/referentialActions-onDelete-cascade-mysql/test.ts
 PASS  src/__tests__/integration/happy/referentialActions-onDelete-cascade-postgresql/test.ts
 PASS  src/__tests__/integration/happy/json-filtering-postgres/test.ts
 PASS  src/__tests__/integration/happy/native-types-mysql/test.ts
 PASS  src/__tests__/integration/happy/interactive-transactions-postgres/test.ts (23.57 s)
  ● Console

    console.warn
      warn(prisma-client) There are already 10 instances of Prisma Client actively running.

      81 |       const runningEngines = engines.filter((e) => e.engine);
      82 |       if (runningEngines.length === 10) {
    > 83 |         console.warn(`${import_chalk.default.yellow("warn(prisma-client)")} There are already 10 instances of Prisma Client actively running.`);
         |                 ^
      84 |       }
      85 |     }
      86 |   }

      at LibraryEngine.checkForTooManyEngines (../engine-core/dist/library/LibraryEngine.js:83:17)
      at new LibraryEngine (../engine-core/dist/library/LibraryEngine.js:77:10)
      at PrismaClient.getEngine (src/runtime/getPrismaClient.ts:454:47)
      at new PrismaClient (src/runtime/getPrismaClient.ts:425:29)
      at Object.<anonymous> (src/__tests__/integration/happy/interactive-transactions-postgres/test.ts:658:12)

 PASS  src/__tests__/integration/happy/native-types-postgres/test.ts (19.823 s)
 PASS  src/__tests__/integration/happy/json-filtering-mysql/test.ts (27.959 s)
 PASS  src/__tests__/types/types.test.ts (426.401 s)
 FAIL  src/__tests__/integration/happy/composites-mongo/upsert/required/create.ts (473.354 s)
  ● upsert > required > create › set

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      18 |   })

It's at this point when the tests completely stop my machine(100%cpu, 100%ram) and hang for a unknown amount of time sometimes > 1 hour.
I can't trust the location of the warnings because of the way jest is rendering the console logs, and so it's really unknown where this error is happening.
I have tried running the tests with --maxWorkers=50% to no avail:
PC Specs
Running tests with Gitbash

Related
Some issues I dug out that could be related to this.

https://github.com/prisma/prisma/issues/8989
https://github.com/prisma/prisma/issues/7249
https://github.com/prisma/prisma/issues/12858
https://github.com/prisma/prisma/issues/9902
https://github.com/prisma/prisma/issues/12028
https://github.com/prisma/prisma/issues/9042

Looping this one in too https://github.com/prisma/prisma/pull/13029

then an error stating that there is many instances of Prisma client constructed:

That warning (not error) is expected to be there.
What is your complete setup from "checkout repo" to when you run the tests?

then an error stating that there is many instances of Prisma client constructed:

That warning (not error) is expected to be there.

Could you be a little more specific ?

What did you do to install dependencies and other setup steps after checking out the repo?
What databases exactly have you started with which commands?
Have you manually set any additional env vars before running cd ./packages/client && pnpm run test?

What did you do to install dependencies and other setup steps after checking out the repo? What databases exactly have you started with which commands? Have you manually set any additional env vars before running cd ./packages/client && pnpm run test?

1, Node
Version: 16.0.0
2, Prerequisites:
https://github.com/prisma/prisma/blob/main/CONTRIBUTING.md#general-prerequisites
3, Fork
git clone FORK_URL

Navigate into the fork:
cd prisma

Pull upstream main:
git pull https://github.com/prisma/prisma

4, Install
Use pnpm to install dependency's
pnpm i
pnpm run setup

5, Docker

Run default docker:
cd ./docker && docker-compose up -d

5, Env
Place .envrc file in the root of project:
export TEST_POSTGRES_URI="postgres://prisma:prisma@localhost:5432/tests"
export TEST_POSTGRES_ISOLATED_URI="postgres://prisma:prisma@localhost:5435/tests"
export TEST_POSTGRES_URI_MIGRATE="postgres://prisma:prisma@localhost:5432/tests-migrate"
export TEST_POSTGRES_SHADOWDB_URI_MIGRATE="postgres://prisma:prisma@localhost:5432/tests-migrate-shadowdb"

export TEST_MYSQL_URI="mysql://root:root@localhost:3306/tests"
export TEST_MYSQL_ISOLATED_URI="mysql://root:root@localhost:3307/tests"
export TEST_MYSQL_URI_MIGRATE="mysql://root:root@localhost:3306/tests-migrate"
export TEST_MYSQL_SHADOWDB_URI_MIGRATE="mysql://root:root@localhost:3306/tests-migrate-shadowdb"

export TEST_MARIADB_URI="mysql://prisma:prisma@localhost:4306/tests"

export TEST_MSSQL_URI="mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master" # for `mssql` lib used in some tests
export TEST_MSSQL_JDBC_URI="sqlserver://localhost:1433;database=master;user=SA;password=Pr1sm4_Pr1sm4;trustServerCertificate=true;"
export TEST_MSSQL_JDBC_URI_MIGRATE="sqlserver://localhost:1433;database=tests-migrate;user=SA;password=Pr1sm4_Pr1sm4;trustServerCertificate=true;"
export TEST_MSSQL_SHADOWDB_JDBC_URI_MIGRATE="sqlserver://localhost:1433;database=tests-migrate-shadowdb;user=SA;password=Pr1sm4_Pr1sm4;trustServerCertificate=true;"

export TEST_MONGO_URI="mongodb://root:prisma@localhost:27018/tests?authSource=admin"
export TEST_MONGO_URI_MIGRATE="mongodb://root:prisma@localhost:27017/tests-migrate?authSource=admin"

export TEST_COCKROACH_URI=postgresql://prisma@localhost:26257/

5(a), Run Direnv:
direnv allow

6 Run Tests
cd ./packages/client && pnpm run test

What did you do to install dependencies and other setup steps after checking out the repo? What databases exactly have you started with which commands? Have you manually set any additional env vars before running cd ./packages/client && pnpm run test?

1, Node
Version: 16.0.0
2, Prerequisites:
https://github.com/prisma/prisma/blob/main/CONTRIBUTING.md#general-prerequisites
3, Fork
git clone FORK_URL

Navigate into the fork:
cd prisma

Pull upstream main:
git pull https://github.com/prisma/prisma

4, Install
Use pnpm to install dependency's
pnpm i
pnpm run setup

5, Docker

Run default docker:
cd ./docker && docker-compose up -d

5, Env
Place .envrc file in the root of project:
export TEST_POSTGRES_URI="postgres://prisma:prisma@localhost:5432/tests"
export TEST_POSTGRES_ISOLATED_URI="postgres://prisma:prisma@localhost:5435/tests"
export TEST_POSTGRES_URI_MIGRATE="postgres://prisma:prisma@localhost:5432/tests-migrate"
export TEST_POSTGRES_SHADOWDB_URI_MIGRATE="postgres://prisma:prisma@localhost:5432/tests-migrate-shadowdb"

export TEST_MYSQL_URI="mysql://root:root@localhost:3306/tests"
export TEST_MYSQL_ISOLATED_URI="mysql://root:root@localhost:3307/tests"
export TEST_MYSQL_URI_MIGRATE="mysql://root:root@localhost:3306/tests-migrate"
export TEST_MYSQL_SHADOWDB_URI_MIGRATE="mysql://root:root@localhost:3306/tests-migrate-shadowdb"

export TEST_MARIADB_URI="mysql://prisma:prisma@localhost:4306/tests"

export TEST_MSSQL_URI="mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master" # for `mssql` lib used in some tests
export TEST_MSSQL_JDBC_URI="sqlserver://localhost:1433;database=master;user=SA;password=Pr1sm4_Pr1sm4;trustServerCertificate=true;"
export TEST_MSSQL_JDBC_URI_MIGRATE="sqlserver://localhost:1433;database=tests-migrate;user=SA;password=Pr1sm4_Pr1sm4;trustServerCertificate=true;"
export TEST_MSSQL_SHADOWDB_JDBC_URI_MIGRATE="sqlserver://localhost:1433;database=tests-migrate-shadowdb;user=SA;password=Pr1sm4_Pr1sm4;trustServerCertificate=true;"

export TEST_MONGO_URI="mongodb://root:prisma@localhost:27018/tests?authSource=admin"
export TEST_MONGO_URI_MIGRATE="mongodb://root:prisma@localhost:27017/tests-migrate?authSource=admin"

export TEST_COCKROACH_URI=postgresql://prisma@localhost:26257/

5(a), Run Direnv:
direnv allow

6 Run Tests
cd ./packages/client && pnpm run test

Running the commands using Gitbash on Windows.

Side note: Instructions on how to install direnv on Windows that worked for me: https://gist.github.com/rmtuckerphx/4ace28c1605300462340ffa7b7001c6d

Hm, I think I can not reproduce:
Test Suites: 6 failed, 5 skipped, 178 passed, 184 of 189 total
Tests:       55 failed, 18 skipped, 697 passed, 770 total
Snapshots:   546 passed, 546 total
Time:        696.575 s
Ran all test suites.
 ELIFECYCLE  Test failed. See above for more details.

Failures are mostly timeouts though indeed:
Summary of all failing tests
FAIL src/__tests__/integration/happy/full-text-search-postgres/test.ts (12.234 s)
  ● full-text-search (postgres) › findMany with &

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_POSTGRES_URI
      20 | describe('full-text-search (postgres)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_POSTGRES_URI += '-full-text-search'
      23 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-postgres/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-postgres/test.ts:20:1)

  ● full-text-search (postgres) › findMany with |

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_POSTGRES_URI
      20 | describe('full-text-search (postgres)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_POSTGRES_URI += '-full-text-search'
      23 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-postgres/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-postgres/test.ts:20:1)

  ● full-text-search (postgres) › findMany with <->

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_POSTGRES_URI
      20 | describe('full-text-search (postgres)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_POSTGRES_URI += '-full-text-search'
      23 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-postgres/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-postgres/test.ts:20:1)

  ● full-text-search (postgres) › findMany with & and |

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_POSTGRES_URI
      20 | describe('full-text-search (postgres)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_POSTGRES_URI += '-full-text-search'
      23 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-postgres/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-postgres/test.ts:20:1)

  ● full-text-search (postgres) › findMany with !

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_POSTGRES_URI
      20 | describe('full-text-search (postgres)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_POSTGRES_URI += '-full-text-search'
      23 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-postgres/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-postgres/test.ts:20:1)

  ● full-text-search (postgres) › no results

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_POSTGRES_URI
      20 | describe('full-text-search (postgres)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_POSTGRES_URI += '-full-text-search'
      23 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-postgres/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-postgres/test.ts:20:1)

  ● full-text-search (postgres) › bad operator

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_POSTGRES_URI
      20 | describe('full-text-search (postgres)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_POSTGRES_URI += '-full-text-search'
      23 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-postgres/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-postgres/test.ts:20:1)

  ● full-text-search (postgres) › order by relevance on a single field

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_POSTGRES_URI
      20 | describe('full-text-search (postgres)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_POSTGRES_URI += '-full-text-search'
      23 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-postgres/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-postgres/test.ts:20:1)

  ● full-text-search (postgres) › order by relevance on multiple fields

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_POSTGRES_URI
      20 | describe('full-text-search (postgres)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_POSTGRES_URI += '-full-text-search'
      23 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-postgres/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-postgres/test.ts:20:1)

  ● full-text-search (postgres) › multiple order by statements on different fields

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_POSTGRES_URI
      20 | describe('full-text-search (postgres)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_POSTGRES_URI += '-full-text-search'
      23 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-postgres/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-postgres/test.ts:20:1)

  ● Test suite failed to run

    TypeError: Cannot read properties of undefined (reading 'user')

      54 |
      55 |   afterAll(async () => {
    > 56 |     await prisma.user.deleteMany()
         |                  ^
      57 |     await prisma.$disconnect()
      58 |     process.env.TEST_POSTGRES_URI = baseUri
      59 |   })

      at src/__tests__/integration/happy/full-text-search-postgres/test.ts:56:18

FAIL src/__tests__/integration/happy/full-text-search-mysql/test.ts (25.288 s)
  ● full-text-search (mysql) › findMany with +

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_MYSQL_URI
      20 | describe('full-text-search (mysql)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_MYSQL_URI += '-full-text-search'
      23 |     await tearDownMysql(process.env.TEST_MYSQL_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-mysql/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-mysql/test.ts:20:1)

  ● full-text-search (mysql) › findMany with OR

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_MYSQL_URI
      20 | describe('full-text-search (mysql)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_MYSQL_URI += '-full-text-search'
      23 |     await tearDownMysql(process.env.TEST_MYSQL_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-mysql/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-mysql/test.ts:20:1)

  ● full-text-search (mysql) › findMany with -

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_MYSQL_URI
      20 | describe('full-text-search (mysql)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_MYSQL_URI += '-full-text-search'
      23 |     await tearDownMysql(process.env.TEST_MYSQL_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-mysql/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-mysql/test.ts:20:1)

  ● full-text-search (mysql) › no results

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_MYSQL_URI
      20 | describe('full-text-search (mysql)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_MYSQL_URI += '-full-text-search'
      23 |     await tearDownMysql(process.env.TEST_MYSQL_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-mysql/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-mysql/test.ts:20:1)

  ● full-text-search (mysql) › bad operator

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_MYSQL_URI
      20 | describe('full-text-search (mysql)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_MYSQL_URI += '-full-text-search'
      23 |     await tearDownMysql(process.env.TEST_MYSQL_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-mysql/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-mysql/test.ts:20:1)

  ● full-text-search (mysql) › order by relevance on a single field

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_MYSQL_URI
      20 | describe('full-text-search (mysql)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_MYSQL_URI += '-full-text-search'
      23 |     await tearDownMysql(process.env.TEST_MYSQL_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-mysql/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-mysql/test.ts:20:1)

  ● full-text-search (mysql) › order by relevance on multiple fields

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_MYSQL_URI
      20 | describe('full-text-search (mysql)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_MYSQL_URI += '-full-text-search'
      23 |     await tearDownMysql(process.env.TEST_MYSQL_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-mysql/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-mysql/test.ts:20:1)

  ● full-text-search (mysql) › multiple order by statements on different fields

    thrown: "Exceeded timeout of 10000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      19 | const baseUri = process.env.TEST_MYSQL_URI
      20 | describe('full-text-search (mysql)', () => {
    > 21 |   beforeAll(async () => {
         |   ^
      22 |     process.env.TEST_MYSQL_URI += '-full-text-search'
      23 |     await tearDownMysql(process.env.TEST_MYSQL_URI!)
      24 |     await migrateDb({

      at src/__tests__/integration/happy/full-text-search-mysql/test.ts:21:3
      at Object.<anonymous> (src/__tests__/integration/happy/full-text-search-mysql/test.ts:20:1)

  ● Test suite failed to run

    TypeError: Cannot read properties of undefined (reading 'user')

      54 |
      55 |   afterAll(async () => {
    > 56 |     await prisma.user.deleteMany()
         |                  ^
      57 |     await prisma.$disconnect()
      58 |     process.env.TEST_MYSQL_URI = baseUri
      59 |   })

      at src/__tests__/integration/happy/full-text-search-mysql/test.ts:56:18

FAIL src/__tests__/integration/happy/blog-env-mssql/test.ts (96.856 s)
  ● blog-env-mssql › includes version in generated client

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › does not leak connection strings in node_modules

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › invokes beforeRequest hook

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › can throw validation errors

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › can run findMany queries

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › can run findMany queries with a `null` where

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › can run create queries

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › can run delete queries

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › can run update queries

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › $queryRaw › $queryRaw(sql`<SQL>`)

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › $queryRaw › $queryRaw(sql`<SQL>`) with params

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › $queryRaw › $queryRaw`<SQL>`

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › $queryRaw › $queryRaw`<SQL>` with join

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › $queryRaw › $queryRaw`<SQL>` with params

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › $queryRaw › $queryRaw(string) error

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › $queryRawUnsafe › $queryRawUnsafe(string)

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › $queryRawUnsafe › $queryRawUnsafe(string) with params

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › $executeRaw › $executeRaw(sql`<SQL>`)

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › $executeRaw › $executeRaw(sql`<SQL>`) with params

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › $executeRaw › $executeRaw`<SQL>`

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › $executeRaw › $executeRaw`<SQL>` with params

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › $executeRaw › $executeRaw(string) error

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › $executeRawUnsafe › $executeRawUnsafe(string)

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● blog-env-mssql › $executeRawUnsafe › $executeRawUnsafe(string) with params

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      12 |   const requests: any[] = []
      13 |
    > 14 |   beforeAll(async () => {
         |   ^
      15 |     const connectionString = process.env.TEST_MSSQL_URI || 'mssql://SA:Pr1sm4_Pr1sm4@localhost:1433/master'
      16 |     const setupParams: SetupParams = {
      17 |       connectionString,

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:14:3
      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-mssql/test.ts:9:41)

  ● Test suite failed to run

    TypeError: Cannot read properties of null (reading '$disconnect')

      43 |
      44 |   afterAll(async () => {
    > 45 |     await prisma.$disconnect()
         |                  ^
      46 |   })
      47 |
      48 |   test('includes version in generated client', () => {

      at src/__tests__/integration/happy/blog-env-mssql/test.ts:45:18

FAIL src/__tests__/integration/happy/json-filtering-postgres/test.ts (94.814 s)
  ● json-filtering(postgres) › lt(2)

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      17 |
      18 | describe('json-filtering(postgres)', () => {
    > 19 |   beforeAll(async () => {
         |   ^
      20 |     process.env.TEST_POSTGRES_URI += '-json-filtering'
      21 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      22 |     await migrateDb({

      at src/__tests__/integration/happy/json-filtering-postgres/test.ts:19:3
      at Object.<anonymous> (src/__tests__/integration/happy/json-filtering-postgres/test.ts:18:1)

  ● json-filtering(postgres) › lte(2)

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      17 |
      18 | describe('json-filtering(postgres)', () => {
    > 19 |   beforeAll(async () => {
         |   ^
      20 |     process.env.TEST_POSTGRES_URI += '-json-filtering'
      21 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      22 |     await migrateDb({

      at src/__tests__/integration/happy/json-filtering-postgres/test.ts:19:3
      at Object.<anonymous> (src/__tests__/integration/happy/json-filtering-postgres/test.ts:18:1)

  ● json-filtering(postgres) › gte(2)

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      17 |
      18 | describe('json-filtering(postgres)', () => {
    > 19 |   beforeAll(async () => {
         |   ^
      20 |     process.env.TEST_POSTGRES_URI += '-json-filtering'
      21 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      22 |     await migrateDb({

      at src/__tests__/integration/happy/json-filtering-postgres/test.ts:19:3
      at Object.<anonymous> (src/__tests__/integration/happy/json-filtering-postgres/test.ts:18:1)

  ● json-filtering(postgres) › gt(2)

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      17 |
      18 | describe('json-filtering(postgres)', () => {
    > 19 |   beforeAll(async () => {
         |   ^
      20 |     process.env.TEST_POSTGRES_URI += '-json-filtering'
      21 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      22 |     await migrateDb({

      at src/__tests__/integration/happy/json-filtering-postgres/test.ts:19:3
      at Object.<anonymous> (src/__tests__/integration/happy/json-filtering-postgres/test.ts:18:1)

  ● json-filtering(postgres) › string_contains(bc)

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      17 |
      18 | describe('json-filtering(postgres)', () => {
    > 19 |   beforeAll(async () => {
         |   ^
      20 |     process.env.TEST_POSTGRES_URI += '-json-filtering'
      21 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      22 |     await migrateDb({

      at src/__tests__/integration/happy/json-filtering-postgres/test.ts:19:3
      at Object.<anonymous> (src/__tests__/integration/happy/json-filtering-postgres/test.ts:18:1)

  ● json-filtering(postgres) › string_starts_with(a)

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      17 |
      18 | describe('json-filtering(postgres)', () => {
    > 19 |   beforeAll(async () => {
         |   ^
      20 |     process.env.TEST_POSTGRES_URI += '-json-filtering'
      21 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      22 |     await migrateDb({

      at src/__tests__/integration/happy/json-filtering-postgres/test.ts:19:3
      at Object.<anonymous> (src/__tests__/integration/happy/json-filtering-postgres/test.ts:18:1)

  ● json-filtering(postgres) › string_ends_with(c)

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      17 |
      18 | describe('json-filtering(postgres)', () => {
    > 19 |   beforeAll(async () => {
         |   ^
      20 |     process.env.TEST_POSTGRES_URI += '-json-filtering'
      21 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      22 |     await migrateDb({

      at src/__tests__/integration/happy/json-filtering-postgres/test.ts:19:3
      at Object.<anonymous> (src/__tests__/integration/happy/json-filtering-postgres/test.ts:18:1)

  ● json-filtering(postgres) › array_contains([1, 2, 3])

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      17 |
      18 | describe('json-filtering(postgres)', () => {
    > 19 |   beforeAll(async () => {
         |   ^
      20 |     process.env.TEST_POSTGRES_URI += '-json-filtering'
      21 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      22 |     await migrateDb({

      at src/__tests__/integration/happy/json-filtering-postgres/test.ts:19:3
      at Object.<anonymous> (src/__tests__/integration/happy/json-filtering-postgres/test.ts:18:1)

  ● json-filtering(postgres) › array_starts_with(5)

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      17 |
      18 | describe('json-filtering(postgres)', () => {
    > 19 |   beforeAll(async () => {
         |   ^
      20 |     process.env.TEST_POSTGRES_URI += '-json-filtering'
      21 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      22 |     await migrateDb({

      at src/__tests__/integration/happy/json-filtering-postgres/test.ts:19:3
      at Object.<anonymous> (src/__tests__/integration/happy/json-filtering-postgres/test.ts:18:1)

  ● json-filtering(postgres) › array_ends_with(12)

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      17 |
      18 | describe('json-filtering(postgres)', () => {
    > 19 |   beforeAll(async () => {
         |   ^
      20 |     process.env.TEST_POSTGRES_URI += '-json-filtering'
      21 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      22 |     await migrateDb({

      at src/__tests__/integration/happy/json-filtering-postgres/test.ts:19:3
      at Object.<anonymous> (src/__tests__/integration/happy/json-filtering-postgres/test.ts:18:1)

  ● json-filtering(postgres) › filter with Prisma.JsonNull

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      17 |
      18 | describe('json-filtering(postgres)', () => {
    > 19 |   beforeAll(async () => {
         |   ^
      20 |     process.env.TEST_POSTGRES_URI += '-json-filtering'
      21 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      22 |     await migrateDb({

      at src/__tests__/integration/happy/json-filtering-postgres/test.ts:19:3
      at Object.<anonymous> (src/__tests__/integration/happy/json-filtering-postgres/test.ts:18:1)

  ● json-filtering(postgres) › filter with Prisma.DbNull

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      17 |
      18 | describe('json-filtering(postgres)', () => {
    > 19 |   beforeAll(async () => {
         |   ^
      20 |     process.env.TEST_POSTGRES_URI += '-json-filtering'
      21 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      22 |     await migrateDb({

      at src/__tests__/integration/happy/json-filtering-postgres/test.ts:19:3
      at Object.<anonymous> (src/__tests__/integration/happy/json-filtering-postgres/test.ts:18:1)

  ● json-filtering(postgres) › filter with Prisma.AnyNull

    thrown: "Exceeded timeout of 90000 ms for a hook.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      17 |
      18 | describe('json-filtering(postgres)', () => {
    > 19 |   beforeAll(async () => {
         |   ^
      20 |     process.env.TEST_POSTGRES_URI += '-json-filtering'
      21 |     await tearDownPostgres(process.env.TEST_POSTGRES_URI!)
      22 |     await migrateDb({

      at src/__tests__/integration/happy/json-filtering-postgres/test.ts:19:3
      at Object.<anonymous> (src/__tests__/integration/happy/json-filtering-postgres/test.ts:18:1)

  ● Test suite failed to run

    TypeError: Cannot read properties of undefined (reading 'user')

      64 |   })
      65 |   afterAll(async () => {
    > 66 |     await prisma.user.deleteMany()
         |                  ^
      67 |     await prisma.$disconnect()
      68 |     process.env.TEST_POSTGRES_URI = baseUri
      69 |   })

      at src/__tests__/integration/happy/json-filtering-postgres/test.ts:66:18

FAIL src/__tests__/integration/happy/blog-env-postgresql/test.ts (95.08 s)
  ● Blog fixture: Postgres

    thrown: "Exceeded timeout of 90000 ms for a test.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      3 | import { setupPostgres, tearDownPostgres } from '../../../../utils/setupPostgres'
      4 |
    > 5 | test('Blog fixture: Postgres', async () => {
        | ^
      6 |   await generateTestClient()
      7 |
      8 |   const { PrismaClient, Prisma } = require('./node_modules/@prisma/client')

      at Object.<anonymous> (src/__tests__/integration/happy/blog-env-postgresql/test.ts:5:1)

FAIL src/__tests__/generation/generator.test.ts (307.881 s)
  ● generator › denylist from engine validation

    thrown: "Exceeded timeout of 90000 ms for a test.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      94 |   })
      95 |
    > 96 |   test('denylist from engine validation', async () => {
         |   ^
      97 |     const prismaClientTarget = path.join(__dirname, './node_modules/@prisma/client')
      98 |     // Make sure, that nothing is cached.
      99 |     try {

      at src/__tests__/generation/generator.test.ts:96:3
      at Object.<anonymous> (src/__tests__/generation/generator.test.ts:16:1)

Computer is a https://www.microsoft.com/en-us/d/surface-laptop-studio/8srdf62swkpf:
$ npx thispc
npm WARN exec The following package was not found and will be installed: thispc
Terminal size: undefinedxundefined

 User Information
┌─────────┬──────────┬──────────────────┬──────────────────┬─────────────────┬─────────────────────────────┐
│ (index) │ Username │     Hostname     │  Home Directory  │    Timezone     │          Timestamp          │
├─────────┼──────────┼──────────────────┼──────────────────┼─────────────────┼─────────────────────────────┤
│    0    │  'Jan'   │ 'Surface-Studio' │ 'C:\\Users\\Jan' │ 'Europe/Berlin' │ '2022-05-04T00:44:05+02:00' │
└─────────┴──────────┴──────────────────┴──────────────────┴─────────────────┴─────────────────────────────┘
 System Specification
┌─────────┬──────────────┬────────────┬──────────────────────────────────────────────────┬────────────┬───────────────┐
│ (index) │ Total Memory │ Total Cpus │                    Cpu Model                     │ Cpu Speed  │ System Uptime │
├─────────┼──────────────┼────────────┼──────────────────────────────────────────────────┼────────────┼───────────────┤
│    0    │  '31.84 GB'  │     8      │ '11th Gen Intel(R) Core(TM) i7-11370H @ 3.30GHz' │ '3.30 GHz' │    '2.2 d'    │
└─────────┴──────────────┴────────────┴──────────────────────────────────────────────────┴────────────┴───────────────┘
 System Information
┌─────────┬───────────────────┬──────────┬──────────────┬──────────────┬────────────────────────────────────────┐
│ (index) │ Operating System  │ Platform │     Type     │ Architecture │             Temp Directory             │
├─────────┼───────────────────┼──────────┼──────────────┼──────────────┼────────────────────────────────────────┤
│    0    │ 'Windows 10 Home' │ 'win32'  │ 'Windows_NT' │    'x64'     │ 'C:\\Users\\Jan\\AppData\\Local\\Temp' │
└─────────┴───────────────────┴──────────┴──────────────┴──────────────┴────────────────────────────────────────┘

#13149

I beleive this should be fixed right now. iTx caused the slowdown. Issue was fixed in prisma/prisma-engines#3028


GitHub URL Reference invalid

URL to Basic Multi Dialog sample returns a 404 error:
https://github.com/Microsoft/BotBuilder-Samples/tree/master/CSharp/core-BasicMultiDialog

@rcc-peters Links to the v4 samples should be good now. If you notice any, please use the feedback feature so we know which article has the issue.


Not building?

Describe the bug
cargo install fails with the following message

108  |                 self.spotify.seek_track(position_ms, device_id).await?
|                              ---------- ^^^^^^^^^^^ expected Duration, found u32
|                              |
|                              arguments to this method are incorrect
|

To Reproduce
Just run cargo install, build will fail.
Environment

OS: MacOS
Application version: N/A
Application features: if applicable, provide cargo features used to build spotify_player

Additional context
rustc 1.69.0 (84c898d65 2023-04-16)

Will close this issue for now as I assume --locked should fix it. Feel free to re-open if the issue still persists.


Is there any EventEmitter implementation for Preact?

I want to use preact with websockets. But I wondering is possible using like facebook's EventEmitter.

@mehmetkose you can just use the same EventEmitter (the Facebook one). Shouldn't be any different in preact.  We have a 200 byte functional version of EventEmitter we'll likely release soon, but for now Facebook's seems reasonable.
(Closing since I think that answers your question, but let me know if I missed the point!)

no question. thank you.

I built a port of Node's EventEmitter that is smaller, more functional and independent from other Node libs. I am using it with Preact. It can be found here:
uevents
It's pre-1.0.0 so any feedback is welcome!

We have a 200 byte functional version of EventEmitter we'll likely release soon

Sounds interesting! Maybe we could combine our efforts? My current implementation is a full port, but this could probably be trimmed down.

Wow that looks like an amazing drop-in for events - have you thought about submitting it as an official "browser" alias for the node module? Nice work!

Thanks! Well, the original EventEmitter from Node can already be used in the browser. It just pulled in some dependencies that I didn't want. When using React you hardly notice it, but with Preact you see how your bundle more than doubles in size when you pull in EventEmitter from Node because Preact is so tiny!  :)  So it seemed too much of a waste to do that...
It turns out that more modules pull in more than we bargained for... I also ended up creating my own version of debug, named ulog and I also forked Kriasoft's Universal Router and named it uroute. The reason I don't use preact-router is because I am doing server-side rendering and want to start rendering the page before the data has come back from e.g the database. So I need a router where I can easily decouple routing from rendering. But Universal Router (while a brilliant piece of code) uses Generators, which requires the Babel generator runtime, which is too big for my liking. So...  :)

That's awesome. I wonder if we can find a way to transpile generators to something smaller?


Handle failed transactions, reverted and avoid insertion.

See how to handle the following transaction so it is not added to the swap transactions database
https://etherscan.io/tx/0x01820523196083047e8b0ffbc8a7676e643cc7b857c4b5640ebc64a4d75a14fc

another case:
https://dashboard.tenderly.co/tx/mainnet/0x93127ec9b1c13815c6aca9363c737fcb5f874c6f8ddfc6a795b01308d5f17225


elfconv.sh fails possibly from unrecognized register?

This is the elfconv Docker container with a statically built nodejs in it. I'm assuming it failed to produce the lift.bc file?
root@b76e2aa57c0f:~/elfconv/bin# TARGET=wasm-browser ./elfconv.sh ../node/out/Release/node
[INFO] Building elfconv-Runtime ...
shared:INFO: (Emscripten: Running sanity checks)
[INFO] Generate libelfconv.a.
[INFO] Converting ELF to LLVM bitcode ...
E20240521 19:27:41.072849    56 Arch.cpp:3459] Unrecognized system register da17 with op0=3, op1=3, crn=4, crm=2, op2=7, bits.name=0xda17
./elfconv.sh: line 31:    56 Killed                  ./elflift --arch aarch64 --bc_out lift.bc --target_elf "$ELFPATH" --dbg_fun_cfg "$2"
[INFO] Generate lift.bc.
[INFO] Converting LLVM bitcode to WASM binary (for browser) ...
emcc: error: lift.bc: No such file or directory ("lift.bc" was expected to be an input file, based on the commandline arguments provided)
[INFO] Generate WASM binary.

Thank you for the error report.
This error is caused by the specified arm64 instruction in the node binary using the system register that elfconv doesn't support now.
Could you attach the binary? I will check it.


Remove citation styles

The reference text collected in ReferenceCollection.js has begun to
improperly include styles included via TemplateStyles, and these are now
being displayed to users in the Android app.
This patch adds 'style' to the list of selectors to strip when compiling
the reference text.
Bug: https://phabricator.wikimedia.org/T206527

great! i'll cut a build after lunch :)


Add initial minimal ArmNN delegate plugin.

Adds ArmNN delegate interface
Allows to specify backend id
Supports the following operators: Conv2d, DepthwiseCond2d, Pool2d, Softmax, Squeeze

@jdduke could you take a look at this, since it's in the mobile TensorFlow Lite code?

Thanks George, per offline discussion we'll sync up on this directly to discuss next steps.

@GeorgeARM, @jdduke Any update on this PR, please. Thanks!

Tentatively closing per offline discussions, we can reopen after further dialog around hosting and distribution.


Any support for custom entity?

Awesome project btw.
Would it be possible to support custom entity rendering?

Hi @zhangkaiyulw!
Did you mean atomic types of draft.js?


1.0.4

Fix npm deploy and test timeout.
Fix playback status, connection status, metadata and tracks support.

Fix npm deploy and test timeout.
Fix playback status, connection status, metadata and tracks support.

Fix npm deploy and test timeout.
Fix playback status, connection status, metadata and tracks support.


Improve user interaction with prover

Files don't need end with "spec.k".
"true" is not printed when no claims are found. A more appropriate
message is used instead.
Claims can be introduce by adding the "claim" attribute to a rule.
Modules now have ".claims" field for fetching Claims.

Jenkins: test this please


Not Playing Radio

Hi, I got an issue about the playing radio streaming link.
Radio is playing for the link with SSL but not playing with http://.
May be the links are AAC audio those are not playing. I already added network config rules. But it's not working. May be because of AAC stream audio. Please share your thought to overcome this issue

Hi Ajijul thanks for visiting my git repo.. But for your requirement I personally suggesting you to use "exoplayer" which is good and fit for your project.
https://github.com/google/ExoPlayer


Scan can exhaust GitHub REST API  rate limit when generating comments

The scan has no protection against blowing through the GitHub REST API rate limit when many many comments are to be generated.
Writing comments using GitHub REST API...
WARNING: In September 2022, v3.x of the Salesforce Code Analyzer will become the default version,
         and older versions, including your currently installed version, will no longer be supported.
         You can manually update to v3.x earlier for a smoother transition.
WARNING: As of April 27, 2022, v3.x of the Salesforce Code Analyzer is available as an open pilot.
         To update to v3.x and try out our pilot features, run these commands:
         > sfdx plugins:uninstall @salesforce/sfdx-scanner
         > sfdx plugins:install @salesforce/sfdx-scanner@latest-pilot
/home/runner/work/_actions/mitchspano/sfdx-scan-pull-request/v0.1/dist/index.js:6544
      const error = new requestError.RequestError(toErrorMessage(data), status, {
                    ^

RequestError [HttpError]: Validation Failed: {"resource":"PullRequestReviewComment","code":"abuse","field":"base"}
    at /home/runner/work/_actions/mitchspano/sfdx-scan-pull-request/v0.1/dist/index.js:6544:21
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async writeComments (/home/runner/work/_actions/mitchspano/sfdx-scan-pull-request/v0.1/dist/index.js:7[17](https://github.com/rsoesemann/salesforce-recipes/runs/7617457933?check_suite_focus=true#step:4:18)01:7) {
  status: 4[22](https://github.com/rsoesemann/salesforce-recipes/runs/7617457933?check_suite_focus=true#step:4:23),
  response: {
    url: 'https://api.github.com/repos/rsoesemann/salesforce-recipes/pulls/2/comments',
    status: 422,

    ...

    data: {
      message: 'Validation Failed',
      errors: [
        {
          resource: 'PullRequestReviewComment',
          code: 'abuse',
          field: 'base'
        }
      ],
      documentation_url: 'https://docs.github.com/rest'
    }
  },
  request: {
    method: 'POST',
    url: 'https://api.github.com/repos/rsoesemann/salesforce-recipes/pulls/2/comments',
    headers: {
      accept: 'application/vnd.github.v3+json',
      'user-agent': 'octokit-action.js/4.0.4 octokit-core.js/4.0.4 Node.js/16.13.0 (linux; x64)',
      authorization: 'token [REDACTED]',
      'content-type': 'application/json; charset=utf-8'
    },
    body: `{"commit_id":"7e02f10a68b649d3de0042b5e328[59](https://github.com/rsoesemann/salesforce-recipes/runs/7617457933?check_suite_focus=true#step:4:60)315ee38c33","path":"force-app/main/apex-domainbuilder/classes/Voldemort.cls","start_line":80,"start_side":"RIGHT","side":"RIGHT","line":81,"body":"| Engine | Category | Rule | Severity | Type |\\n| --- | --- | --- | --- | --- |\\n| pmd | Best Practices | UnusedLocalVariable | 5 | Error |\\n\\n[\\nVariable 'space' defined but not used\\n](https://pmd.github.io/pmd-6.47.0/pmd_rules_apex_bestpractices.html#unusedlocalvariable)"}`,
    request: {
      agent: ProxyAgent { promisifiedCallback: [Function (anonymous)] },
      hook: [Function: bound bound register]
    }
  }
}

https://docs.github.com/en/rest/rate-limit

Maybe not directly the same, but also hitting limits when to much comments are generated:
After following log output: Creating Check Runs using GitHub REST API...
"data": {
"message": "Invalid request.\n\nNo more than 50 items are allowed; 261 were supplied.",
"documentation_url": "https://docs.github.com/rest/checks/runs#create-a-check-run"
}


Add a tutorial taken from Alan's branch

I've included a commit with his version unmodified, in the hope that it makes merging them together in future easier.
Even if we haven't settled on a "new printer" API, we still could really do with basic tutorials in the docs.
I'll follow up with his calculus tutorial later.

Tutorial appears on the docs here: https://galgebra--375.org.readthedocs.build/en/375/tutorials/algebra.html

Note that CI fails due to the use of f-strings.
We could choose to not run tests against this file.


Document the need to compile before running tests

If you follow the "Running the Tests" instructions verbatim, the tests will not run because the code hasn't been compiled yet. The proper way to run tests is ceylon compile && ceylon test $(basename source/*).

I think talking about compile first is the way to go -- conceptually it makes more sense, since it is the precursor to test, and it reads better. I've adjusted the wording and amended my commit.
I copied over the same wording to TRACK_HINTS, as well.


Ensure clean shutdown and in flight messages are completed

Whilst running the component with DEBUG turned on I observed the
component never clears the setInterval timer during stop.
A 2nd behaviour observed and experienced in production is when
stop() is called on the component, the azure client connections are immediately stopped and closed,
this results in active in-flight messages currently being processed by a handler to
fail even if the actual processing within the handler succeeded, this is
a result of the call to await receiver.completeMessage(brokeredMessage); within the handler
that can never complete as the connection is already closed. This results in the messages
being re-queued and retried even if they previously succeeded.
This change tracks open subscriptions using a new array openSubscriptions then when
stop() is called each openSubscription is closed first. Based on MS docs this first
blocks and drains the open subscription cleanly. The code is then able to
wait on any inflight messages to be processed before closing the azure sb connections.
Tests all pass (although sometimes, they are a bit flaky and need re-run or run individually).

@hustler I have replicated this PR in this other one https://github.com/guidesmiths/systemic-azure-bus/pull/67
Do you think we can close this PR in favour of the replica one?


got build error

got the error during build:
Looking in indexes: https://mirrors.aliyun.com/pypi/simple/
Requirement already satisfied: pywin32 in c:\users\qkkkwa\appdata\local\anaconda3\envs\pyqt\lib\site-packages (308)
Requirement already satisfied: cffi in c:\users\qkkkwa\appdata\local\anaconda3\envs\pyqt\lib\site-packages (1.17.1)
Requirement already satisfied: pycparser in c:\users\qkkkwa\appdata\local\anaconda3\envs\pyqt\lib\site-packages (from cffi) (2.22)
Nuitka-Options: Used command line options: --standalone --output-dir=dist --follow-import-to=fish main.py --onefile --output-filename=fish --include-data-dir=assets=assets
Nuitka-Options: --include-data-dir=locales=locales --include-data-files=fish_audio_preprocess=fish_audio_preprocess/=**/*.py --windows-console-mode=disable --enable-plugins=pkg-resources
Nuitka-Options: --enable-plugins=pyqt6 --nofollow-import-to=mkl,click,scipy,pandas,matplotlib,pytest --include-qt-plugins=sensible,multimedia --show-memory --show-progress
Nuitka-Options: --windows-icon-from-ico=assets/favicon.ico
FATAL: Error, 'fish_audio_preprocess' does not match any files.

Oh, I forgot this...
You can firstly clone this repository by this command:
git clone https://github.com/AnyaCoder/audio-preprocess
Then copy the folder fish-audio-preprocess to the root of fish-speech-gui repository.

for the next person, Is it possible to update the instructions? or add this directory into this repo? I'm happy to do it, just tell me which you want.

for the next person, Is it possible to update the instructions? or add this directory into this repo? I'm happy to do it, just tell me which you want.

Yes, I think i need to add the folder, thanks for reminding me :)


Fix #2367 in a cleaner way, but with more refactoring

Modifies determineTheme usage, such that theme === undefined is also handled correctly.
This is another PR that fixes #2367, but does more refactoring as suggested in #2558.
I created this as a separate PR, so you can still easily merge #2558 if that is preferred in the end.

Just need a test and a changelog entry. Also a PR against canary as well if you could!

Done


Incompatible with the twilight forest

https://www.curseforge.com/minecraft/mc-mods/the-twilight-forest

Please add additional information.


From future import annotations deprecation postponed

FYI: https://bugs.python.org/issue38605
won't be automatically imported until python 3.11.
--py310-plus: annotations

should be
--py311-plus: annotations

this was already fixed: #163

Ack! I was confused since the documentation lists py10 in the readme.


Airdrop Error

[write something useful and descriptive here]
When I try to participate in Stellar airdrop, I get this error
my log id: 46c5904b5dab1357ac1a811c

me too

Related:

https://github.com/keybase/client/issues/15257#issuecomment-531395333
#19515
#19531
#19548
#19572
#19607
#19642
#19644
#19646
#19647

Solved: #19718

Hi, my error message was Keybase can't verify the github signature.
Is the file required keybase.md or keybase.md. (that's what the app displayed, with another dot after filename)? I tried after a few days creating both files and worked.
Are you able to clarify how do I tell if I am registered for the airdrop? (I saw the halt message 16th September). If I have Stellar address associated, is that enough? I understand it is necessary to fight scam, just want to clarify.
Thanks!

Are you able to clarify how do I tell if I am registered for the airdrop? (I saw the halt message 16th September). If I have Stellar address associated, is that enough? I understand it is necessary to fight scam, just want to clarify.

Open app, go to Wallet tab. If you don't see Airdrop section, then you're most likely not qualified.


Day9: working with dictionaries

Hey there,
Having a hard time following instructions for day 9.  Dictionaries are unsorted.  So printing out the nth dictionary entry doesn't make sense to me.  Since the dictionary is in alphabetical order in data.py, I assumed this means that is the "order" the instructions are referring to.  So I generated a new dictionary with the index as the key.
However, the last instruction says to replace the key in the nth position of the dictionary with the value from the nth position in the list.  However, that would create a duplicate key in the dictionary and doesn't work.
Please let me know if I'm completely missing something here!
Thanks very much!
-Blake

Hi Blake!
Thanks for pointing this out mate.
Firstly, correct! Dictionaries are unsorted, so the idea is to intentionally sort this dict by key and then  grab the nth key/value as per the instructions. Even though data.py is "sorted" in alphabetical key order, there's no guarantee that's the order you'll get when parsing it.
As for swapping the nth dict key with the nth list value... I've been over zealous so thank you (seriously) for raising this as an issue! I'm going to strip that out of the readme for now.
We're working on an additional Bite to add in for this which should make up for my oversight.
Keeping this issue open while we work on the Bite.
Thanks again mate!
Cheers,
Julian

Hey Julian,
Thanks for the feedback. Really enjoying the course! Keep up the great work!
-Blake

Hi Blake! Check out the readme now. We've left the manual steps but have created a new Bite on the codechalleng.es platform that's a good (better) replacement.
https://codechalleng.es/bites/promo/listvsdict
Hope that helps man!
Let us know if otherwise.
Thanks!
Julian


S2U-39 <IP_ADDRESS> Wiki: Add group support to Wiki pages - fix

This is linked with https://github.com/sakaiproject/sakai-reference/pull/209

The requested conversion scripts its here:

Could you check everything here @bgarciaentornos ? I've almost reviewed it completelly but there are DB changes.

Thanks for all the great work on this.


/dashboard "Work Type" Filter does not work

When choosing a filter on "Work Type" on the dashboard (like trees), all of the results should return cases with a tree. Either the filter does not work, or only returns one work_type.

Seems to work now.


Increase trait test coverage

We have low/no test coverage for the following traits:
github.com/apache/camel-k/pkg/trait/prometheus.go
github.com/apache/camel-k/pkg/trait/jolokia.go
github.com/apache/camel-k/pkg/trait/affinity.go
github.com/apache/camel-k/pkg/trait/istio.go
github.com/apache/camel-k/pkg/trait/pull_secret.go

We should add e2e tests for increasing test coverage.

If no one has started it yet, I can work on it.

Now covered all of the listed traits. Let's close it.

Now covered all of the listed traits. Let's close it.


CakeBuild Experimental mode (Rosyln C# 6) breaks WithLogLevel()

This is more as a Public Service Announcement than an issue.
If you enable Experimental mode in Cake to get some of lovely C# 6 features, you will get the following error for:
Npm.WithLogLevel(NpmLogLevel.Silent).Install();

error CS1061: 'INpmRunnerConfiguration' does not contain a definition for 'Install' and
no extension method 'Install' accepting a first argument of type 'INpmRunnerConfiguration'
could be found (are you missing a using directive or an assembly reference?)

Workaround, you need to cast the INpmRunnerConfiguration to NpmRunner.
((NpmRunner)Npm.WithLogLevel(NpmLogLevel.Silent)).Install();

Firstly apologies for the delay in replying to your issue, "real life" has been hectic the past few weeks.
After implementing the recent .WithLogLevel and .FromPath options I realised I wasnt correctly covering the possible usage very well, leading to this issue.  I am planning to find a way to update the addin while maintaining backwards compatibility.
In the mean time another workaround is to chain the .FromPath whenever using .WithLogLevel.
  Npm.WithLogLevel(NpmLogLevel.Silent).FromPath(".").Install();

@Philo no problem, "real life" is more important than this issue.
If you want help with fixing this, let me know. I'm happy to jump in.


False FC009 in package/yum/package for allow_downgrade attribute

Throws FC009 if in yum_package resource attribute allow_downgrade is used

What version of foodcritic are you running into this with?

The one that comes with chefdk 1.3.43 - 10.2.2

Can you paste the exact code that's failing?

Closing this out since we never got a response with failing code. If you want to open this back up with some example code I'll dig in and see what I can do


GPflow2 set_default_float and set_default_int accept tf dtypes but that breaks code

Some functions such as the Gauss-Hermite quadrature code call numpy_array.astype(default_float()), which fails if default_float() returns a tensorflow dtype such as tf.float64 instead of np.float64. However, gpflow.config.set_default_float() explicitly allows both numpy and tensorflow dtypes as arguments.

Also, it'd be really nice to have a config context-manager to be able to have localised changes to the config...


Can't get JS obfuscation working on IOS

Working on Android, but main.bundlejs remains unobfuscated : (

I'm trying to find a free obfuscation example for ios but so far iphone has no free obfuscators. And most start at $99 and other benefits obviously!


Bug fix, plus whitelist/blacklist from command line

Adding two things because they are small.

adds blacklist and whitelist file command line overrides
fix for my previous pull-request, where attempting to generate with a non-existent output directory resulted in an exception.  This appears to have been because of the open with "a" which does not appear to work with a non-existent directory.  In this case I just use os.path.isfile/1 as os.path already appears to be used in other areas of the script, to skip the initial attempt at creation, then use "wb" on the known non-existent file as that appears to create the directory.

I can split into two PR's if having these two in a single one is a problem, but they are both so small I figured it's probably okay.  Let me know if it's not.

Whitelist/Blacklist parts now in https://github.com/StevenBlack/hosts/pull/1227, closing this to refactor in a better way.


add new test suite

Adds new test suite
Adds tests for the following service integrations: clickhouse_postgresql, kafka_logs, kafka_connect
Adds a new action and renames an old make command: test -> test-ginko, new -> test

tests https://github.com/aiven/aiven-operator/actions/runs/4280889726

I'm testing it locally and getting strange results:

It runs really fast, so the test reports that it is done while services are not yet RUNNING on Aiven. How this can be so fast?

I have lots of panic's in the logs during runtime:

 unable to create or update aiven secret: Object default/kafka-secret is already owned by another Kafka controller test-k8s-0wqtydi-ks"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
        /home/ivan.savciuc/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
        /home/ivan.savciuc/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:234

And lots of errors on the start of the test:

1.6776915844250357e+09	ERROR	Reconciler error	{"controller": "kafka", "controllerGroup": "aiven.io", "controllerKind": "Kafka", "kafka": {"name":"test-k8s-xvqor1e-ks","namespace":"default"}, "namespace": "default", "name": "test-k8s-xvqor1e-ks", "reconcileID": "f2ff50bd-edbc-42cb-a435-b2f99e9f225e", "error": "unable to wait until instance is running: unable to create or update aiven secret: Object default/kafka-secret is already owned by another Kafka controller test-k8s-meteggi-ks"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/home/ivan.savciuc/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/home/ivan.savciuc/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:234

So all in all I have tests reporting: --- PASS: TestServiceIntegrationKafkaLogs (237.99s) after 3 min, I have 146 errors in the logs.

I have updated PR. There were racing secrets. Nice to know. I wonder if that racing right now in ginkgo. As to the timing: I have no idea what is going on. Right now I'm running the tests and it takes 236.730s.


error

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
``
Errors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
``

Expected Behavior
Environment Summary
Linux-4.15.0-1082-azure-x86_64-with-debian-stretch-sid
Python 3.6.5
Installer: DEB

azure-cli 2.5.1 *

Additional Context

Please share detailed command and related error info.

hi @satish61 could you pls share error detail for investigation?

This ticket can be closed. I opened it in another browser and it worked.
Sent from Outlook Mobilehttps://aka.ms/blhgte

From: Yunge Zhu<EMAIL_ADDRESS>Sent: Wednesday, June 3, 2020 8:58:41 PM
To: Azure/azure-cli<EMAIL_ADDRESS>Cc: Satish Deo<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/azure-cli] error (#13809)
hi @satish61https://github.com/satish61 could you pls share error detail for investigation?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-cli/issues/13809#issuecomment-638555215, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL6UOHLZ4B7DVWSQ6QVN6CLRU35VDANCNFSM4NR2SCBA.


WIP: Initial schema proposal

There are still some main discrepancies between the example benchmar-001.yaml and omni-schema.

Prameter: What about adding a values slot to Parameter and changing parameters to ParameterCollection?
Inputs: We do not use file paths for inputs in the current yaml file format, but indirectly infer them from the specified stage and types outputs. So we either need to separate IOFile for outputs and inputs or we change the yaml.
A possibility is also to extend the yaml towards a more explicit, but also verbose format for now?

Fixed discrepancies mentioned by @almutlue in order to have a functioning initial schema.

Parameter: I agree, I added a values slot, but modeled the content as a vector of strings. Raw parameter strings can be processed initially to get refined parameters input: e.g. "-a 0 -b 0.1" -> ["-a 0", "-b 0.1"]
Inputs: I made the IOFile extend IdentifiableEntity and so each has a unique id. As an input, we can then reference by id a specific IOFile. The IOFile itself represents the concept of an output from a previous step, not necessary the materalised output file. By linking the input to an output, we can then use the path (path format) to figure out the exact materialsed input file we need.

Proposed model looks like this, and it validates an example benchmark yaml.

Now, LinkML and this model will help us have a single source of truth in terms of domain model. The yaml schema can be exported as SQL, JSON, RDF and python classes.
However, the proposed starts_to_be_explicit.yaml is still a bit different than what the current schema can validate, Benchmark-001.yaml. How different? Well, let's compare:
--- starts_to_be_explicit.yaml
+++ Benchmark-001.yaml
@@ -1,4 +1,5 @@
 ---
+id: Benchmark-001
 name: starts_to_be_explicit
 description: simple benchmark, somewhat explicit, simple params
 platform: https://gitlab.renkulab.io/
@@ -6,72 +7,106 @@
   name: orchestrator
   url: https://gitlab.renkulab.io/omnibenchmark/test/orchestrator
 steps:
-  data:
+  - id: Step1
+    name: data
     initial: true
     members:
-      - name: D1
+      - id: D1
+        name: D1
         repo: omnibenchmark/test/D1
-      - name: D2
+      - id: D2
+        name: D2
         repo: omnibenchmark/test/D2
     outputs:
-      - counts: "{stage}/{module}/{params}/{name}.txt.gz"
-      - meta: "{stage}/{module}/{params}/{name}.meta.json"
-      - data_specific_params: "{stage}/{module}/{params}/{name}_params.txt"
-  process:
+      - id: Step1.counts
+        name: counts
+        path: "{stage}/{module}/{params}/{name}.txt.gz"
+      - id: Step1.meta
+        name: meta
+        path: "{stage}/{module}/{params}/{name}.meta.json"
+      - id: Step1.data_specific_params
+        name: data_specific_params
+        path: "{stage}/{module}/{params}/{name}_params.txt"
+
+  - id: Step2
+    name: process
     after:
       - data
     members:
-      - name: P1
+      - id: P1
+        name: P1
         repo: omnibenchmark/test/P1
         parameters:
-          - -a 0, -b 0.1
-          - -a 1 -b 0.1
-      - name: P2
+          - values: ["-a 0", "-b 0.1"]
+          - values: ["-a 1", "-b 0.1"]
+      - id: P2
+        name: P2
         repo: omnibenchmark/test/P2
         parameters:
-          - -a 0 -c 0
-          - -a 1 -c 0.1
+          - values: ["-a 0", "-c 0"]
+          - values: ["-a 1", "-c 0.1"]
     inputs:
-      - counts: data
-        meta: data
+      - entries: [
+          Step1.counts,
+          Step1.meta
+        ]
     outputs:
-      - filtered: "{input_dirname}/{stage}/{module}/{params}/{name}.txt.gz"
-  methods:
+      - id: Step2.filtered
+        name: filtered
+        path: "{input_dirname}/{stage}/{module}/{params}/{name}.txt.gz"
+
+  - id: Step3
+    name: methods
     after:
       - process
     members:
-      - name: M1
+      - id: M1
+        name: M1
         repo: benchmark/test/M1
-        exclude: D2
-      - name: M2
+        exclude: [ D2 ]
+      - id: M2
+        name: M2
         repo: omnibenchmark/test/M2
         parameters:
-          - -d1 -e1
-          - -d1 -e 2
+          - values: ["-d1", "-e 1"]
+          - values: ["-d1", "-e 2"]
         exclude:
           - D1
           - D2
     inputs:
-      - counts: data
-        meta: data
-        data_specific_params: data
-      - filtered: process
-        meta: data
-        data_specific_params: data
+      - entries: [
+          Step1.counts,
+          Step1.meta,
+          Step1.data_specific_params
+        ]
+      - entries: [
+          Step2.filtered,
+          Step1.meta,
+          Step1.data_specific_params
+        ]
     outputs:
-      - mapping: "{input_dirname}/{stage}/{module}/{params}/{name}.model.out.gz"
-  metrics:
+      - id: Step3.mapping
+        name: mapping
+        path: "{input_dirname}/{stage}/{module}/{params}/{name}.model.out.gz"
+
+  - id: Step4
+    name: metrics
     after:
       - methods
     terminal: true
     members:
-      - name: m1
+      - id: m1
+        name: m1
         repo: omnibenchmark/test/m1
-      - name: m2
+      - id: m2
+        name: m2
         repo: omnibenchmark/test/m2
-      - name: m3
+      - id: m3
+        name: m3
         repo: omnibenchmark/test/m3
     inputs:
-      - mapping: method
-        meta: data
-        data_specific_params: data
+      - entries: [
+          Step3.mapping,
+          Step1.meta,
+          Step1.data_specific_params
+        ]

Now there are multiple possibilities to mitigate this differences that I see fit:

Learn from the experience of designing the LinkML schema and update the original starts_to_be_explicit.yaml schema.
Update the LinkML omni_schema.yaml schema.
Map the benchmark definition data from the original format to the LinkML format on the fly. This will work since it involves only introducing some unique ids and straightforward transformations.

What are your suggestions about it? Does the data model make sense to you?

Great! Looks very good to me. Shall we merge?


Buggy mobile main menu

So, you can slide in the main menu but it's very buggy and too hard to slide.

Fixed in the v1.0.0-beta.3 update


[FLINK-13159] Prevent potential NPE of restored PojoSerializer when deserializing

What is the purpose of the change
Prevent potential NPE when PojoSerializer restored.
Brief change log

Ensure the classloader could be assigned when PojoSerializer restored.

Verifying this change
This change added tests and can be verified as follows:

Added test testRestoreSerializerDeserialize into SerializerTestBase to ensure all restored serializes could deserialize values as expected.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: yes
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@flinkbot approve all

@Myasuka thanks for the fast fix.
As discussed offline, I've reverted the changes to SerializerTestBase since the requirement of equality checks on the test data objects is out of scope of this fix, and would require a more proper discussion on how we want to do that.
On top of your fixes, I've extended the PojoSerializerMigrationTest to cover the NPE case.
Those tests fail without your fix, so that should confirm that the fix is correct.
Will merge once Travis is green:
https://github.com/tzulitai/flink/tree/FLINK-13159-premerge


Code completion on properties inherited from parent

On behalf of @clement-brodu
Code completion on a property inherited from the parent class shows entries coming from the current class.

Fixed


simplex-chat-desktop: 5.8.1 -> 6.0.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for simplex-chat-desktop is: Desktop application for SimpleX Chat
meta.homepage for simplex-chat-desktop is: https://simplex.chat
meta.changelog for simplex-chat-desktop is: https://github.com/simplex-chat/simplex-chat/releases/tag/v5.8.2
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.8.2 in filename of file in /nix/store/0b40v8z5klbnlprkv0q9mnzf8jy2rfrv-simplex-chat-desktop-5.8.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

simplex-chat-desktop

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0b40v8z5klbnlprkv0q9mnzf8jy2rfrv-simplex-chat-desktop-5.8.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A simplex-chat-desktop https://github.com/r-ryantm/nixpkgs/archive/15f73879ed3dd1ad37a650cca5a1ee43ebb18ee2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/15f73879ed3dd1ad37a650cca5a1ee43ebb18ee2#simplex-chat-desktop

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0b40v8z5klbnlprkv0q9mnzf8jy2rfrv-simplex-chat-desktop-5.8.2
ls -la /nix/store/0b40v8z5klbnlprkv0q9mnzf8jy2rfrv-simplex-chat-desktop-5.8.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

simplex-chat-desktop

Maintainer pings
cc @yuuyins for testing.

Exception in thread "main" java.lang.UnsatisfiedLinkError: /nix/store/r9d9w1qd4q8x8lfc7marshy5d0df3k91-simplex-chat-desktop-5.8.2-extracted/usr/lib/app/resources/libapp-lib.so: libffi.so.7: cannot open shared object file: No such file or directory

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for simplex-chat-desktop is: Desktop application for SimpleX Chat
meta.homepage for simplex-chat-desktop is: https://simplex.chat
meta.changelog for simplex-chat-desktop is: https://github.com/simplex-chat/simplex-chat/releases/tag/v6.0.1
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.0.1 in filename of file in /nix/store/7cr8zr67j8i40rn27qwq80f4jvyxpgbc-simplex-chat-desktop-6.0.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

simplex-chat-desktop

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7cr8zr67j8i40rn27qwq80f4jvyxpgbc-simplex-chat-desktop-6.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A simplex-chat-desktop https://github.com/r-ryantm/nixpkgs/archive/9fcc435e8ae10ec934e96ee0ea6600baa4ca34f5.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/9fcc435e8ae10ec934e96ee0ea6600baa4ca34f5#simplex-chat-desktop

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7cr8zr67j8i40rn27qwq80f4jvyxpgbc-simplex-chat-desktop-6.0.1
ls -la /nix/store/7cr8zr67j8i40rn27qwq80f4jvyxpgbc-simplex-chat-desktop-6.0.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

simplex-chat-desktop

Maintainer pings
cc @yuuyins for testing.

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

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for simplex-chat-desktop is: Desktop application for SimpleX Chat
meta.homepage for simplex-chat-desktop is: https://simplex.chat
meta.changelog for simplex-chat-desktop is: https://github.com/simplex-chat/simplex-chat/releases/tag/v6.0.3
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.0.3 in filename of file in /nix/store/fz4wjikpaw0vxy051cgwafqx9dyvzklg-simplex-chat-desktop-6.0.3

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

simplex-chat-desktop

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fz4wjikpaw0vxy051cgwafqx9dyvzklg-simplex-chat-desktop-6.0.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A simplex-chat-desktop https://github.com/r-ryantm/nixpkgs/archive/a852d3de67e7660446f61191739e88486eea9bed.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a852d3de67e7660446f61191739e88486eea9bed#simplex-chat-desktop

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fz4wjikpaw0vxy051cgwafqx9dyvzklg-simplex-chat-desktop-6.0.3
ls -la /nix/store/fz4wjikpaw0vxy051cgwafqx9dyvzklg-simplex-chat-desktop-6.0.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

simplex-chat-desktop

Maintainer pings
cc @yuuyins for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

@NixOS/nixpkgs-merge-bot merge

@NixOS/nixpkgs-merge-bot merge


Update swc_core to v0.90.10

Description
Update SWC crates, to apply https://github.com/swc-project/swc/pull/8647
Testing Instructions
See https://github.com/vercel/next.js/pull/62222. It's next.js counterpart.
Closes PACK-2530

Merging as https://github.com/vercel/next.js/pull/62222 is appoved


remove deprecated and unused visual studio plugins

Under visual studio plugins:

Code Contracts is a dead microsoft package and I think it should be removed
Developer assistant is a dead link.

I think these two should be removed since they aren't actively maintained.

PR ;)


Grove.io implementation

We added a service for Grove.io (IRC servers for companies). These are my first lines of Ruby ever so be careful.

@technoweenie Thanks for the merge. Any idea when could we see this going into production?


add lat lng to merchant.json

lat and lng is needed for google maps.

google is free until 28,500 requests per month
yahoo is free until 50,000 requests per day
kokudochiriin is free no limit!!

Test for kokudochiriin

guide: https://elsammit-beginnerblg.hatenablog.com/entry/2021/07/11/122916
uri: https://msearch.gsi.go.jp/address-search/AddressSearch?q=hogehoge
tested 3 addresses are good.

commit


Provide integration with Activity

Any plans to integrate with Activity.Current & new Activity()? (docs)

No plan as this is a basic alternative option. Microsoft provide support for using activities and tracing if people want more features than a basic correlation ID.


Auto save notes for every "x" seconds

Refer to the documentation of notes schema
Notes bloc is defined in lib/features/notes/presentation/bloc/notes. We need to emit the SaveNote event with a timer of "x" seconds.
Use Timer.periodic to emit this event in lib/features/notes/presentation/pages/note_create_page.dart.
Next step would be to make "x" configurable by taking an input from settings

@SankethBK Picking this up.


feat: add namespace for release

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


txn: don't protect rollback for BatchRollback

cherry-pick #7494 to release-3.0

Signed-off-by: Yilin Chen<EMAIL_ADDRESS>
What problem does this PR solve?
Issue Number: close #7490
Problem Summary: rollback calls cleanup and it writes protected rollback record for all non-exsitent keys which may causes performance regression in heavy contention workload with optimistic transaction. See #7435
What is changed and how it works?
What's Changed: Only cleanup or check_txn_status need to write the protected rollback record.
Related changes

Need to cherry-pick to the release branch

Check List
Tests

Unit test

Release note
Do not protect rollback records written by BatchRollback to improve performance when there are many write conflicts in optimistic transactions.

/merge

/merge

/run-all-tests