Skip to content

[release] 20240509 #2400

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
May 9, 2024
Merged

[release] 20240509 #2400

merged 1 commit into from
May 9, 2024

Conversation

stwiname
Copy link
Collaborator

@stwiname stwiname commented May 9, 2024

No description provided.

@github-actions GitHub Actions
Copy link

github-actions bot commented May 9, 2024

Coverage report for .

Caution

Test run failed

St.❔
 Category Percentage Covered / Total
🟡 Statements
69.1% (-1.01% 🔻)
 19082/27617
🟡 Branches
77.43% (-0.87% 🔻)
 2075/2680
🟡 Functions
63.28% (+0.78% 🔼)
 908/1435
🟡 Lines
69.1% (-1.01% 🔻)
 19082/27617
Show new covered files 🐣
St.❔
 File Statements Branches Functions Lines
🟢
... / migrate.ts
 85.09% 10% 100% 85.09%
🟢
... / migrate-abis.controller.ts
 95% 87.5% 100% 95%
🟢
... / constants.ts
 100% 100% 100% 100%
🟢
... / index.ts
 100% 100% 100% 100%
🟢
... / ethereum.ts
 82.05% 83.33% 100% 82.05%
🟢
... / migrate-manifest.controller.ts
 88% 72.41% 88.89% 88%
🟢
... / migrate-mapping.controller.ts
 100% 100% 100% 100%
🟢
... / migrate-controller.ts
 92.31% 84.62% 100% 92.31%
🟢
... / migrate.fixtures.ts
 100% 100% 100% 100%
🟢
... / migrate-schema.controller.ts
 100% 100% 100% 100%
🔴
... / types.ts
 0% 0% 0% 0%
🟢
... / createProject.fixtures.ts
 90.16% 66.67% 100% 90.16%
🟢
... / networkFamily.ts
 92.59% 88.89% 100% 92.59%
🟢
... / dictionary.fixtures.ts
 100% 100% 100% 100%
🔴
... / sandbox.service.ts
 45.45% 50% 33.33% 45.45%
🔴
... / foreceClean.init.ts
 42.86% 100% 0% 42.86%
🔴
... / reindex.init.ts
 31.03% 100% 0% 31.03%
🔴
... / datasourceProcessors.ts
 0% 0% 0% 0%
Show files with reduced coverage 🔻
St.❔
 File Statements Branches Functions Lines
🔴
... / index.ts
26.14% (-56.82% 🔻)
100% (+33.33% 🔼)
0% (-50% 🔻)
26.14% (-56.82% 🔻)
🔴
... / index.ts
33.87% (-58.06% 🔻)
100% (+75% 🔼)
0% (-100% 🔻)
33.87% (-58.06% 🔻)
🔴
... / deploy.ts
18.97% (-2.17% 🔻)
 100% 0%
18.97% (-2.17% 🔻)
🔴
... / publish.ts
28% (-61.33% 🔻)
100% (+42.86% 🔼)
0% (-100% 🔻)
28% (-61.33% 🔻)
🔴
... / build-controller.ts
11.96% (-79.35% 🔻)
100% (+42.86% 🔼)
0% (-100% 🔻)
11.96% (-79.35% 🔻)
🟢
... / codegen-controller.ts
 89.39%
75% (-0.58% 🔻)
 100% 89.39%
🟢
... / generate-controller.ts
 97.65%
93.85% (-0.18% 🔻)
 100% 97.65%
🟡
... / init-controller.ts
72.89% (+2.4% 🔼)
54.55% (-13.45% 🔻)
61.11% (+7.78% 🔼)
72.89% (+2.4% 🔼)
🔴
... / publish-controller.ts
14.81% (-65.43% 🔻)
100% (+28.89% 🔼)
0% (-100% 🔻)
14.81% (-65.43% 🔻)
🟢 cli/src/types.ts
96.97% (-0.03% 🔻)
 100% 33.33%
96.97% (-0.03% 🔻)
🟡
... / build.ts
74.48% (-10.34% 🔻)
80% (+3.08% 🔼)
87.5% (-12.5% 🔻)
74.48% (-10.34% 🔻)
🟢
... / utils.ts
80.26% (-0.82% 🔻)
91.94% (+11.23% 🔼)
78.57% (+1.3% 🔼)
80.26% (-0.82% 🔻)
🔴
... / load.ts
52.04% (-7.14% 🔻)
38.46% (-17.09% 🔻)
50% (-16.67% 🔻)
52.04% (-7.14% 🔻)
🟢
... / ipfs-reader.ts
 85.71%
60% (-3.64% 🔻)
 83.33% 85.71%
🟡
... / reader.ts
63.16% (-26.32% 🔻)
33.33% (-41.67% 🔻)
 100%
63.16% (-26.32% 🔻)
🔴
... / utils.ts
50.63% (-12.07% 🔻)
91.67% (+18.5% 🔼)
48% (-8% 🔻)
50.63% (-12.07% 🔻)
🟢
... / ProjectUpgrade.service.ts
85.84% (-1.24% 🔻)
93.67% (+2.31% 🔼)
87.5% (-3.8% 🔻)
85.84% (-1.24% 🔻)
🟢
... / configure.module.ts
80% (-4.57% 🔻)
47.83% (-16.17% 🔻)
 100%
80% (-4.57% 🔻)
🟢
... / db.module.ts
 88.28%
62.5% (-20.83% 🔻)
 80% 88.28%
🟢
... / SchemaMigration.service.ts
 87.56%
80.65% (-0.6% 🔻)
 100% 87.56%
🟡
... / migration-helpers.ts
74.54% (-1.48% 🔻)
86.76% (+6.17% 🔼)
 90.91%
74.54% (-1.48% 🔻)
🔴
... / base-block-dispatcher.ts
46.62% (-0.73% 🔻)
 100%
5% (-5% 🔻)
46.62% (-0.73% 🔻)
🔴
... / block-dispatcher.ts
39.35% (-1.64% 🔻)
 66.67% 28.57%
39.35% (-1.64% 🔻)
🔴
... / worker-block-dispatcher.ts
48.92% (-1.29% 🔻)
 100% 27.27%
48.92% (-1.29% 🔻)
🟢
... / coreDictionary.ts
94.67% (-5.33% 🔻)
87.5% (-6.94% 🔻)
87.5% (-12.5% 🔻)
94.67% (-5.33% 🔻)
🟢
... / utils.ts
92.59% (-3.7% 🔻)
69.23% (-24.89% 🔻)
 100%
92.59% (-3.7% 🔻)
🟢
... / dictionaryV1.ts
89.8% (-3.43% 🔻)
75% (-3.26% 🔻)
 100%
89.8% (-3.43% 🔻)
🟢
... / dictionaryV2.ts
81.58% (-0.1% 🔻)
68% (+2.78% 🔼)
 100%
81.58% (-0.1% 🔻)
🔴
... / ds-processor.service.ts
42.08% (-20.01% 🔻)
73.33% (-1.67% 🔻)
63.64% (-23.86% 🔻)
42.08% (-20.01% 🔻)
🟢
... / dynamic-ds.service.ts
90.55% (+0.36% 🔼)
65% (-1.67% 🔻)
88.89% (+3.17% 🔼)
90.55% (+0.36% 🔼)
🔴
... / indexer.manager.ts
33.21% (+0% 🔼)
 100%
11.11% (-1.39% 🔻)
33.21% (+0% 🔼)
🟢
... / PoiBlock.ts
87.9% (-10.48% 🔻)
57.89% (-38.66% 🔻)
 100%
87.9% (-10.48% 🔻)
🟡
... / store.service.ts
65.57% (-0.48% 🔻)
 68.42% 57.14%
65.57% (-0.48% 🔻)
🔴
... / store.ts
30.59% (-1.62% 🔻)
 100% 0%
30.59% (-1.62% 🔻)
🟢
... / cacheMetadata.ts
 88.51%
73.81% (-1.75% 🔻)
 93.33% 88.51%
🟢
... / cacheModel.ts
87.78% (+2.71% 🔼)
82.67% (+4.35% 🔼)
75% (-1.19% 🔻)
87.78% (+2.71% 🔼)
🟢
... / setValueModel.ts
84.62% (+2.6% 🔼)
81.08% (-0.17% 🔻)
85.71% (+1.1% 🔼)
84.62% (+2.6% 🔼)
🟡
... / storeCache.service.ts
75.12% (-0.12% 🔻)
69.7% (+0.95% 🔼)
 81.25%
75.12% (-0.12% 🔻)
🟡
... / worker.builder.ts
78.85% (-0.33% 🔻)
 65.38%
75% (-5% 🔻)
78.85% (-0.33% 🔻)
🔴
... / worker.service.ts
44.14% (-0.5% 🔻)
 100% 0%
44.14% (-0.5% 🔻)
🟢
... / worker.store.service.ts
80% (-2.61% 🔻)
 100% 50%
80% (-2.61% 🔻)
🔴
... / worker.ts
41.86% (-0.59% 🔻)
 100% 0%
41.86% (-0.59% 🔻)
🟡
... / worker.unfinalizedBlocks.service.ts
64.44% (-35.56% 🔻)
 100%
0% (-100% 🔻)
64.44% (-35.56% 🔻)
🔴
... / reindex.service.ts
32.8% (-0.53% 🔻)
 100% 0%
32.8% (-0.53% 🔻)
🟡
... / blocks.ts
77.78% (-22.22% 🔻)
 88.89%
66.67% (-33.33% 🔻)
77.78% (-22.22% 🔻)
🟡
... / project.ts
66.34% (-7.04% 🔻)
58.49% (-16.09% 🔻)
 77.78%
66.34% (-7.04% 🔻)
🟢
... / promise.ts
94.92% (+3.15% 🔼)
100% (+13.64% 🔼)
83.33% (-2.38% 🔻)
94.92% (+3.15% 🔼)
🔴
... / reindex.ts
33.33% (-0.71% 🔻)
 100% 0%
33.33% (-0.71% 🔻)
🟢
... / SubqueryProject.ts
93.33% (-2.19% 🔻)
42.86% (-39.5% 🔻)
 85.71%
93.33% (-2.19% 🔻)
🟡
... / apiPromise.connection.ts
67.36% (-1.72% 🔻)
75% (-5% 🔻)
 42.86%
67.36% (-1.72% 🔻)
🟢
... / substrateDictionary.service.ts
98.06% (+7.49% 🔼)
69.23% (-3.5% 🔻)
100% (+20% 🔼)
98.06% (+7.49% 🔼)
🟢
... / substrateDictionaryV1.ts
85.05% (-0.43% 🔻)
70.45% (+0.69% 🔼)
 83.33%
85.05% (-0.43% 🔻)
🟡
... / substrateDictionaryV2.ts
73.03% (-2.48% 🔻)
 75% 33.33%
73.03% (-2.48% 🔻)
🟢
... / fetch.module.ts
90.4% (-1.47% 🔻)
50% (-25% 🔻)
 100%
90.4% (-1.47% 🔻)
🔴
... / indexer.manager.ts
57% (-0.55% 🔻)
 100%
11.11% (+2.02% 🔼)
57% (-0.55% 🔻)
🟢
... / runtimeService.ts
94.29% (+2.08% 🔼)
80% (-8.89% 🔻)
100% (+20% 🔼)
94.29% (+2.08% 🔼)
🟢
... / project.ts
88.81% (-0.08% 🔻)
 68.18% 87.5%
88.81% (-0.08% 🔻)
🟢
... / buffer.ts
90.24% (-9.76% 🔻)
90.91% (-9.09% 🔻)
85.71% (+1.5% 🔼)
90.24% (-9.76% 🔻)
🟢
... / entities.ts
87.23% (-1.09% 🔻)
80% (-6.09% 🔻)
 100%
87.23% (-1.09% 🔻)
🟡
... / logger.ts
70.2% (+0.6% 🔼)
52.38% (-2.62% 🔻)
 75%
70.2% (+0.6% 🔼)

Test suite run failed

Failed tests: 14/497. Failed suites: 7/94. 
  ● CLI codegen:generate › extract from TS manifest

    expect(received).toMatch(expected)

    Expected substring: "approve(address spender, uint256 rawAmount)"
    Received string:    "0x095ea7b3"

      684 |     );
      685 |     // TODO expected to fail, due to unable to skip comments
    > 686 |     expect(v.function).toMatch('approve(address spender, uint256 rawAmount)');
          |                        ^
      687 |     expect(v.topics[0]).toMatch('Transfer(address indexed from, address indexed to, uint256 amount)');
      688 |     expect(v.endpoint[0]).toMatch('https://eth.api.onfinality.io/public');
      689 |   });

      at Object.<anonymous> (packages/cli/src/controller/generate-controller.spec.ts:686:24)


  ● Test suite failed to run

    Your test suite must contain at least one test.

      at onResult (node_modules/@jest/core/build/TestScheduler.js:133:18)
      at node_modules/@jest/core/build/TestScheduler.js:254:19
      at node_modules/emittery/index.js:363:13
          at Array.map (<anonymous>)
      at Emittery.emit (node_modules/emittery/index.js:361:23)


  ● Cli can create project (mocked) › Ensure prepareManifest and preparePackage correctness for project.ts

    expect(received).toStrictEqual(expected) // deep equality

    Expected: ["https://zzz", "https://bbb"]
    Received: null

      190 |       endpoint: ENDPOINT_REG,
      191 |     });
    > 192 |     expect(extractedValues.endpoint).toStrictEqual(project.endpoint);
          |                                      ^
      193 |     expect(originalManifest).not.toBe(updatedManifest.toString());
      194 |     expect(originalPackage).not.toBe(packageData.toString());
      195 |   });

      at Object.<anonymous> (packages/cli/src/controller/init-controller.spec.ts:192:38)


  ● CLI deploy, delete, promote › Deploy to Hosted Service and Delete

    Failed to validate IPFS CID: An invalid response was received from the upstream server

      88 | export function errorHandle(e: any, msg: string): Error {
      89 |   if (axios.isAxiosError(e) && e?.response?.data) {
    > 90 |     throw new Error(`${msg} ${e.response.data.message ?? e.response.data}`);
         |           ^
      91 |   }
      92 |
      93 |   throw new Error(`${msg} ${e.message}`);

      at errorHandle (packages/cli/src/utils/utils.ts:90:11)
      at ipfsCID_validate (packages/cli/src/controller/deploy-controller.ts:169:16)
      at Object.<anonymous> (packages/cli/src/controller/deploy-controller.spec.ts:110:23)

  ● CLI deploy, delete, promote › should return true for valid ipfsCID

    Failed to validate IPFS CID: An invalid response was received from the upstream server

      88 | export function errorHandle(e: any, msg: string): Error {
      89 |   if (axios.isAxiosError(e) && e?.response?.data) {
    > 90 |     throw new Error(`${msg} ${e.response.data.message ?? e.response.data}`);
         |           ^
      91 |   }
      92 |
      93 |   throw new Error(`${msg} ${e.message}`);

      at errorHandle (packages/cli/src/utils/utils.ts:90:11)
      at ipfsCID_validate (packages/cli/src/controller/deploy-controller.ts:169:16)
      at Object.<anonymous> (packages/cli/src/controller/deploy-controller.spec.ts:139:23)

  ● CLI deploy, delete, promote › to throw error for invalid ipfsCID

    expect(received).rejects.toThrow(expected)

    Expected substring: "Failed to validate IPFS CID: fake is not a valid subquery deployment id!"
    Received message:   "Failed to validate IPFS CID: An invalid response was received from the upstream server"

          88 | export function errorHandle(e: any, msg: string): Error {
          89 |   if (axios.isAxiosError(e) && e?.response?.data) {
        > 90 |     throw new Error(`${msg} ${e.response.data.message ?? e.response.data}`);
             |           ^
          91 |   }
          92 |
          93 |   throw new Error(`${msg} ${e.message}`);

      at errorHandle (packages/cli/src/utils/utils.ts:90:11)
      at ipfsCID_validate (packages/cli/src/controller/deploy-controller.ts:169:16)
      at Object.<anonymous> (packages/cli/src/controller/deploy-controller.spec.ts:144:5)
      at Object.toThrow (node_modules/expect/build/index.js:210:22)
      at Object.<anonymous> (packages/cli/src/controller/deploy-controller.spec.ts:144:80)

  ● CLI deploy, delete, promote › get DictEndpoint - polkadot

    Failed to validate IPFS CID: An invalid response was received from the upstream server

      88 | export function errorHandle(e: any, msg: string): Error {
      89 |   if (axios.isAxiosError(e) && e?.response?.data) {
    > 90 |     throw new Error(`${msg} ${e.response.data.message ?? e.response.data}`);
         |           ^
      91 |   }
      92 |
      93 |   throw new Error(`${msg} ${e.message}`);

      at errorHandle (packages/cli/src/utils/utils.ts:90:11)
      at ipfsCID_validate (packages/cli/src/controller/deploy-controller.ts:169:16)
      at Object.<anonymous> (packages/cli/src/controller/deploy-controller.spec.ts:150:23)

  ● CLI deploy, delete, promote › reDeploy to Hosted Service

    Failed to validate IPFS CID: An invalid response was received from the upstream server

      88 | export function errorHandle(e: any, msg: string): Error {
      89 |   if (axios.isAxiosError(e) && e?.response?.data) {
    > 90 |     throw new Error(`${msg} ${e.response.data.message ?? e.response.data}`);
         |           ^
      91 |   }
      92 |
      93 |   throw new Error(`${msg} ${e.message}`);

      at errorHandle (packages/cli/src/utils/utils.ts:90:11)
      at ipfsCID_validate (packages/cli/src/controller/deploy-controller.ts:169:16)
      at Object.<anonymous> (packages/cli/src/controller/deploy-controller.spec.ts:160:23)


  ● Cli can create project › prepare correctly applies project details

    expect(received).toEqual(expected) // deep equality

    Expected: null
    Received: ["wss://rpc.polkadot.io/public-ws"]

      128 |     //spec version is  not returned from readDefaults
      129 |     //expect(projectSpec.specVersion).toEqual(specVersion);
    > 130 |     expect(projectSpec.endpoint).toEqual(endpoint);
          |                                  ^
      131 |     expect(projectSpec.author).toEqual(author);
      132 |     expect(projectSpec.description).toEqual(description);
      133 |     await promisify(rimraf)(tempPath);

      at Object.<anonymous> (packages/cli/src/controller/init-controller.test.ts:130:34)


  ● Cli publish › should upload appropriate project to IPFS

    Command failed: npm i
    npm ERR! code ERESOLVE
    npm ERR! ERESOLVE unable to resolve dependency tree
    npm ERR! 
    npm ERR! While resolving: mocked_starter@1.0.0
    npm ERR! Found: @polkadot/api@10.13.1
    npm ERR! node_modules/@polkadot/api
    npm ERR!   dev @polkadot/api@"^10" from the root project
    npm ERR! 
    npm ERR! Could not resolve dependency:
    npm ERR! peer @polkadot/api@"^11" from @subql/types@3.6.0
    npm ERR! node_modules/@subql/types
    npm ERR!   dev @subql/types@"latest" from the root project
    npm ERR! 
    npm ERR! Fix the upstream dependency conflict, or retry
    npm ERR! this command with --force or --legacy-peer-deps
    npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
    npm ERR! 
    npm ERR! 
    npm ERR! For a full report see:
    npm ERR! /home/runner/.npm/_logs/2024-05-09T04_50_48_353Z-eresolve-report.txt

    npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/2024-05-09T04_50_48_353Z-debug-0.log

      53 |
      54 |   // Install dependencies
    > 55 |   childProcess.execSync(`npm i`, {cwd: projectDir});
         |                ^
      56 |
      57 |   await Codegen.run(['-l', projectDir]);
      58 |   await Build.run(['-f', projectDir]);

      at createTestProject (packages/cli/src/createProject.fixtures.ts:55:16)
      at Object.<anonymous> (packages/cli/src/controller/publish-controller.spec.ts:22:18)

  ● Cli publish › convert to deployment and removed descriptive field

    Command failed: npm i
    npm ERR! code ERESOLVE
    npm ERR! ERESOLVE unable to resolve dependency tree
    npm ERR! 
    npm ERR! While resolving: mocked_starter@1.0.0
    npm ERR! Found: @polkadot/api@10.13.1
    npm ERR! node_modules/@polkadot/api
    npm ERR!   dev @polkadot/api@"^10" from the root project
    npm ERR! 
    npm ERR! Could not resolve dependency:
    npm ERR! peer @polkadot/api@"^11" from @subql/types@3.6.0
    npm ERR! node_modules/@subql/types
    npm ERR!   dev @subql/types@"latest" from the root project
    npm ERR! 
    npm ERR! Fix the upstream dependency conflict, or retry
    npm ERR! this command with --force or --legacy-peer-deps
    npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
    npm ERR! 
    npm ERR! 
    npm ERR! For a full report see:
    npm ERR! /home/runner/.npm/_logs/2024-05-09T04_50_48_353Z-eresolve-report.txt

    npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/2024-05-09T04_50_48_353Z-debug-0.log

      53 |
      54 |   // Install dependencies
    > 55 |   childProcess.execSync(`npm i`, {cwd: projectDir});
         |                ^
      56 |
      57 |   await Codegen.run(['-l', projectDir]);
      58 |   await Build.run(['-f', projectDir]);

      at createTestProject (packages/cli/src/createProject.fixtures.ts:55:16)
      at Object.<anonymous> (packages/cli/src/controller/publish-controller.spec.ts:22:18)

  ● Cli publish › convert js object to JSON object

    Command failed: npm i
    npm ERR! code ERESOLVE
    npm ERR! ERESOLVE unable to resolve dependency tree
    npm ERR! 
    npm ERR! While resolving: mocked_starter@1.0.0
    npm ERR! Found: @polkadot/api@10.13.1
    npm ERR! node_modules/@polkadot/api
    npm ERR!   dev @polkadot/api@"^10" from the root project
    npm ERR! 
    npm ERR! Could not resolve dependency:
    npm ERR! peer @polkadot/api@"^11" from @subql/types@3.6.0
    npm ERR! node_modules/@subql/types
    npm ERR!   dev @subql/types@"latest" from the root project
    npm ERR! 
    npm ERR! Fix the upstream dependency conflict, or retry
    npm ERR! this command with --force or --legacy-peer-deps
    npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
    npm ERR! 
    npm ERR! 
    npm ERR! For a full report see:
    npm ERR! /home/runner/.npm/_logs/2024-05-09T04_50_48_353Z-eresolve-report.txt

    npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/2024-05-09T04_50_48_353Z-debug-0.log

      53 |
      54 |   // Install dependencies
    > 55 |   childProcess.execSync(`npm i`, {cwd: projectDir});
         |                ^
      56 |
      57 |   await Codegen.run(['-l', projectDir]);
      58 |   await Build.run(['-f', projectDir]);

      at createTestProject (packages/cli/src/createProject.fixtures.ts:55:16)
      at Object.<anonymous> (packages/cli/src/controller/publish-controller.spec.ts:22:18)


  ● Intergration test - Publish › overwrites any exisiting CID files

    Command failed: npm i
    npm ERR! code ERESOLVE
    npm ERR! ERESOLVE unable to resolve dependency tree
    npm ERR! 
    npm ERR! While resolving: mocked_starter@1.0.0
    npm ERR! Found: @polkadot/api@10.13.1
    npm ERR! node_modules/@polkadot/api
    npm ERR!   dev @polkadot/api@"^10" from the root project
    npm ERR! 
    npm ERR! Could not resolve dependency:
    npm ERR! peer @polkadot/api@"^11" from @subql/types@3.6.0
    npm ERR! node_modules/@subql/types
    npm ERR!   dev @subql/types@"latest" from the root project
    npm ERR! 
    npm ERR! Fix the upstream dependency conflict, or retry
    npm ERR! this command with --force or --legacy-peer-deps
    npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
    npm ERR! 
    npm ERR! 
    npm ERR! For a full report see:
    npm ERR! /home/runner/.npm/_logs/2024-05-09T04_50_58_874Z-eresolve-report.txt

    npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/2024-05-09T04_50_58_874Z-debug-0.log

      53 |
      54 |   // Install dependencies
    > 55 |   childProcess.execSync(`npm i`, {cwd: projectDir});
         |                ^
      56 |
      57 |   await Codegen.run(['-l', projectDir]);
      58 |   await Build.run(['-f', projectDir]);

      at createTestProject (packages/cli/src/createProject.fixtures.ts:55:16)
      at Object.<anonymous> (packages/cli/src/commands/publish.test.ts:16:18)

  ● Intergration test - Publish › create ipfsCID file stored in local with dictiory path

    Command failed: npm i
    npm ERR! code ERESOLVE
    npm ERR! ERESOLVE unable to resolve dependency tree
    npm ERR! 
    npm ERR! While resolving: mocked_starter@1.0.0
    npm ERR! Found: @polkadot/api@10.13.1
    npm ERR! node_modules/@polkadot/api
    npm ERR!   dev @polkadot/api@"^10" from the root project
    npm ERR! 
    npm ERR! Could not resolve dependency:
    npm ERR! peer @polkadot/api@"^11" from @subql/types@3.6.0
    npm ERR! node_modules/@subql/types
    npm ERR!   dev @subql/types@"latest" from the root project
    npm ERR! 
    npm ERR! Fix the upstream dependency conflict, or retry
    npm ERR! this command with --force or --legacy-peer-deps
    npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
    npm ERR! 
    npm ERR! 
    npm ERR! For a full report see:
    npm ERR! /home/runner/.npm/_logs/2024-05-09T04_50_58_874Z-eresolve-report.txt

    npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/2024-05-09T04_50_58_874Z-debug-0.log

      53 |
      54 |   // Install dependencies
    > 55 |   childProcess.execSync(`npm i`, {cwd: projectDir});
         |                ^
      56 |
      57 |   await Codegen.run(['-l', projectDir]);
      58 |   await Build.run(['-f', projectDir]);

      at createTestProject (packages/cli/src/createProject.fixtures.ts:55:16)
      at Object.<anonymous> (packages/cli/src/commands/publish.test.ts:16:18)

  ● Intergration test - Publish › file name consistent with manfiest file name, if -f <manifest path> is used

    Command failed: npm i
    npm ERR! code ERESOLVE
    npm ERR! ERESOLVE unable to resolve dependency tree
    npm ERR! 
    npm ERR! While resolving: mocked_starter@1.0.0
    npm ERR! Found: @polkadot/api@10.13.1
    npm ERR! node_modules/@polkadot/api
    npm ERR!   dev @polkadot/api@"^10" from the root project
    npm ERR! 
    npm ERR! Could not resolve dependency:
    npm ERR! peer @polkadot/api@"^11" from @subql/types@3.6.0
    npm ERR! node_modules/@subql/types
    npm ERR!   dev @subql/types@"latest" from the root project
    npm ERR! 
    npm ERR! Fix the upstream dependency conflict, or retry
    npm ERR! this command with --force or --legacy-peer-deps
    npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
    npm ERR! 
    npm ERR! 
    npm ERR! For a full report see:
    npm ERR! /home/runner/.npm/_logs/2024-05-09T04_50_58_874Z-eresolve-report.txt

    npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/2024-05-09T04_50_58_874Z-debug-0.log

      53 |
      54 |   // Install dependencies
    > 55 |   childProcess.execSync(`npm i`, {cwd: projectDir});
         |                ^
      56 |
      57 |   await Codegen.run(['-l', projectDir]);
      58 |   await Build.run(['-f', projectDir]);

      at createTestProject (packages/cli/src/createProject.fixtures.ts:55:16)
      at Object.<anonymous> (packages/cli/src/commands/publish.test.ts:16:18)

Report generated by 🧪jest coverage report action from c47b950

@stwiname stwiname merged commit 53a035e into main May 9, 2024
2 of 3 checks passed
jiqiang90 added a commit that referenced this pull request Jun 4, 2024
@jiqiang90
init monitor service
e6c4d58 
add init test

fix bug

Update packages/node-core/src/indexer/monitor.service.ts

Co-authored-by: Scott Twiname <skott.twiname@gmail.com>

address comments 1

use cache file stats

tidy up

address comments

worker write

improve logs, forceclean reindex and fix tests

fix inject

Fix block height not being applied to certain historical queries (#2398)

* Fix block height not being applied to certain historical queries

* Update changelog

* Update snapshot

[SKIP CI] Prerelease

[release] 20240509 (#2400)

Move cache clear after tx committed (#2386)

* Move cache clear after tx committed

* Always flush with a block height and remove flushAll option

* Update changelog

---------

Co-authored-by: Scott Twiname <skott.twiname@gmail.com>

[SKIP CI] Prerelease

Escape commit message (#2403)

fix load chainTypes sandbox missing modules (#2404)

* fix load chainTypes sandbox missing modules

* export SANDBOX_DEFAULT_BUILTINS

[SKIP CI] Prerelease

make monitorService optional

tidy up

fix bug

address comments

tidy up

update default monitorFileSize to 0

Admin api (#2415)

* draft

* rewind

* poi

* add tests

* add test for stop poi stop sync

* Update packages/node-core/src/indexer/blockDispatcher/base-block-dispatcher.ts

Co-authored-by: Scott Twiname <skott.twiname@gmail.com>

* address comment

* monitor service add exit

* Update packages/node-core/src/process.ts

Co-authored-by: Scott Twiname <skott.twiname@gmail.com>

* address comments

* change write

* update

* improve exit error

* fix rewind height issue

---------

Co-authored-by: Scott Twiname <skott.twiname@gmail.com>

set default monitor size to 200

adjust monitor file logic

address comments

add monitor log for project upgrade, unique monitor file name
jiqiang90 added a commit that referenced this pull request Jun 4, 2024
@jiqiang90
init monitor service
f7cbeb6 
add init test

fix bug

Update packages/node-core/src/indexer/monitor.service.ts

Co-authored-by: Scott Twiname <skott.twiname@gmail.com>

address comments 1

use cache file stats

tidy up

address comments

worker write

improve logs, forceclean reindex and fix tests

fix inject

Fix block height not being applied to certain historical queries (#2398)

* Fix block height not being applied to certain historical queries

* Update changelog

* Update snapshot

[SKIP CI] Prerelease

[release] 20240509 (#2400)

Move cache clear after tx committed (#2386)

* Move cache clear after tx committed

* Always flush with a block height and remove flushAll option

* Update changelog

---------

Co-authored-by: Scott Twiname <skott.twiname@gmail.com>

[SKIP CI] Prerelease

Escape commit message (#2403)

fix load chainTypes sandbox missing modules (#2404)

* fix load chainTypes sandbox missing modules

* export SANDBOX_DEFAULT_BUILTINS

[SKIP CI] Prerelease

make monitorService optional

tidy up

fix bug

address comments

tidy up

update default monitorFileSize to 0

Admin api (#2415)

* draft

* rewind

* poi

* add tests

* add test for stop poi stop sync

* Update packages/node-core/src/indexer/blockDispatcher/base-block-dispatcher.ts

Co-authored-by: Scott Twiname <skott.twiname@gmail.com>

* address comment

* monitor service add exit

* Update packages/node-core/src/process.ts

Co-authored-by: Scott Twiname <skott.twiname@gmail.com>

* address comments

* change write

* update

* improve exit error

* fix rewind height issue

---------

Co-authored-by: Scott Twiname <skott.twiname@gmail.com>

set default monitor size to 200

adjust monitor file logic

address comments

add monitor log for project upgrade, unique monitor file name
stwiname pushed a commit that referenced this pull request Jun 5, 2024
@jiqiang90
Monitor service (#2402)
8bd8354 
* init monitor service

add init test

fix bug

Update packages/node-core/src/indexer/monitor.service.ts

Co-authored-by: Scott Twiname <skott.twiname@gmail.com>

address comments 1

use cache file stats

tidy up

address comments

worker write

improve logs, forceclean reindex and fix tests

fix inject

Fix block height not being applied to certain historical queries (#2398)

* Fix block height not being applied to certain historical queries

* Update changelog

* Update snapshot

[SKIP CI] Prerelease

[release] 20240509 (#2400)

Move cache clear after tx committed (#2386)

* Move cache clear after tx committed

* Always flush with a block height and remove flushAll option

* Update changelog

---------

Co-authored-by: Scott Twiname <skott.twiname@gmail.com>

[SKIP CI] Prerelease

Escape commit message (#2403)

fix load chainTypes sandbox missing modules (#2404)

* fix load chainTypes sandbox missing modules

* export SANDBOX_DEFAULT_BUILTINS

[SKIP CI] Prerelease

make monitorService optional

tidy up

fix bug

address comments

tidy up

update default monitorFileSize to 0

Admin api (#2415)

* draft

* rewind

* poi

* add tests

* add test for stop poi stop sync

* Update packages/node-core/src/indexer/blockDispatcher/base-block-dispatcher.ts

Co-authored-by: Scott Twiname <skott.twiname@gmail.com>

* address comment

* monitor service add exit

* Update packages/node-core/src/process.ts

Co-authored-by: Scott Twiname <skott.twiname@gmail.com>

* address comments

* change write

* update

* improve exit error

* fix rewind height issue

---------

Co-authored-by: Scott Twiname <skott.twiname@gmail.com>

set default monitor size to 200

adjust monitor file logic

address comments

add monitor log for project upgrade, unique monitor file name

* tidy up

* tidy up

* fix tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jiqiang90 jiqiang90 jiqiang90 approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@stwiname @jiqiang90