Skip to content

Monitor service #2402

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.

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

Merged
merged 4 commits into from
Jun 5, 2024
Merged

Monitor service #2402

merged 4 commits into from
Jun 5, 2024

Conversation

jiqiang90
Copy link
Contributor

@jiqiang90 jiqiang90 commented May 14, 2024

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

TODO:

  • add service to other place ,and write data
  • ideally this should add from main threat, but we need handle workers with this service
  • part of Admin api

Fixes # (issue)

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist

  • I have tested locally
  • I have performed a self review of my changes
  • Updated any relevant documentation
  • Linked to any relevant issues
  • I have added tests relevant to my changes
  • Any dependent changes have been merged and published in downstream modules
  • My code is up to date with the base branch
  • I have updated relevant changelogs. We suggest using chan

Copy link

github-actions bot commented May 14, 2024

Coverage report for .

Caution

Test run failed

St.
Category Percentage Covered / Total
🟡 Statements
64.39% (-5.72% 🔻)
18418/28605
🟢 Branches
80.05% (+1.76% 🔼)
2383/2977
🟡 Functions
65.68% (+3.18% 🔼)
1024/1559
🟡 Lines
64.39% (-5.72% 🔻)
18418/28605
Show new covered files 🐣
St.
File Statements Branches Functions Lines
🟢
... / migrate.ts
85.09% 18.18% 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% 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%
🟢
... / admin.controller.ts
100% 96.55% 100% 100%
🟢
... / blockRange.ts
100% 100% 100% 100%
🔴
... / index.ts
0% 0% 0% 0%
🟢
... / dictionary.fixtures.ts
100% 100% 100% 100%
🟡
... / monitor.service.ts
69.35% 86.75% 93.94% 69.35%
🔴
... / sandbox.service.ts
33.33% 50% 25% 33.33%
🔴
... / worker.monitor.service.ts
41.46% 100% 0% 41.46%
🔴
... / process.ts
55.56% 100% 40% 55.56%
🔴
... / foreceClean.init.ts
47.62% 100% 0% 47.62%
🔴
... / reindex.init.ts
34.48% 100% 0% 34.48%
🟢
... / string.ts
100% 100% 100% 100%
🔴
... / admin.module.ts
0% 0% 0% 0%
🔴
... / 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% 🔼)
50%
26.14% (-56.82% 🔻)
🔴
... / index.ts
33.87% (-58.06% 🔻)
100% (+75% 🔼)
50% (-50% 🔻)
33.87% (-58.06% 🔻)
🔴
... / deploy.ts
19.39% (-1.76% 🔻)
100%
50% (+50% 🔼)
19.39% (-1.76% 🔻)
🔴
... / publish.ts
28% (-61.33% 🔻)
100% (+42.86% 🔼)
50% (-50% 🔻)
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%
🔴
... / deploy-controller.ts
32.49% (-4.98% 🔻)
100% (+22.22% 🔼)
12.5% (-12.5% 🔻)
32.49% (-4.98% 🔻)
🟢
... / generate-controller.ts
97.65%
93.85% (-0.18% 🔻)
100% 97.65%
🟡
... / init-controller.ts
76.21% (+5.73% 🔼)
63.64% (-4.36% 🔻)
61.11% (+7.78% 🔼)
76.21% (+5.73% 🔼)
🔴
... / project-controller.ts
17.81% (-79.45% 🔻)
100% (+40% 🔼)
0% (-100% 🔻)
17.81% (-79.45% 🔻)
🔴
... / publish-controller.ts
14.81% (-65.43% 🔻)
100% (+28.89% 🔼)
0% (-100% 🔻)
14.81% (-65.43% 🔻)
🟡
... / build.ts
74.48% (-10.34% 🔻)
80% (+3.08% 🔼)
87.5% (-12.5% 🔻)
74.48% (-10.34% 🔻)
🟢
... / utils.ts
80.26% (-0.82% 🔻)
91.8% (+11.1% 🔼)
78.57% (+1.3% 🔼)
80.26% (-0.82% 🔻)
🟡
... / load.ts
79.41% (-8.82% 🔻)
66.67% (-19.05% 🔻)
100%
79.41% (-8.82% 🔻)
🔴
... / models.ts
53.33% (-46.11% 🔻)
94.44% (+2.14% 🔼)
38.46% (-61.54% 🔻)
53.33% (-46.11% 🔻)
🟢
... / ProjectManifestVersioned.ts
82.19% (-2.74% 🔻)
88.89% (-11.11% 🔻)
61.54% (+3.21% 🔼)
82.19% (-2.74% 🔻)
🟢
... / model.ts
93.14% (-4.57% 🔻)
100%
73.33% (+1.9% 🔼)
93.14% (-4.57% 🔻)
🔴
... / models.ts
47.06% (-52.94% 🔻)
100%
0% (-100% 🔻)
47.06% (-52.94% 🔻)
🔴
... / load.ts
54.08% (-5.1% 🔻)
56.25% (+0.69% 🔼)
50% (-16.67% 🔻)
54.08% (-5.1% 🔻)
🟡
... / github-reader.ts
60.71% (-28.57% 🔻)
75%
71.43% (-11.9% 🔻)
60.71% (-28.57% 🔻)
🟡
... / ipfs-reader.ts
60.32% (-25.4% 🔻)
63.64%
71.43% (-11.9% 🔻)
60.32% (-25.4% 🔻)
🟡
... / local-reader.ts
60.47% (-25.58% 🔻)
62.5%
83.33% (-16.67% 🔻)
60.47% (-25.58% 🔻)
🟢
... / reader.ts
81.58% (-7.89% 🔻)
57.14% (-17.86% 🔻)
100%
81.58% (-7.89% 🔻)
🔴
... / utils.ts
54.75% (-7.95% 🔻)
76.67% (+3.5% 🔼)
48% (-8% 🔻)
54.75% (-7.95% 🔻)
🔴
... / base.ts
43.43% (-54.57% 🔻)
100%
40% (-40% 🔻)
43.43% (-54.57% 🔻)
🔴
... / models.ts
25.32% (-74.68% 🔻)
100%
0% (-100% 🔻)
25.32% (-74.68% 🔻)
🟢
... / NodeConfig.ts
89.09% (+0.48% 🔼)
79.31% (-0.32% 🔻)
86.96% (+0.91% 🔼)
89.09% (+0.48% 🔼)
🟡
... / ProjectUpgrade.service.ts
73.91% (-13.16% 🔻)
93.67% (+2.31% 🔼)
84% (-7.3% 🔻)
73.91% (-13.16% 🔻)
🟢
... / configure.module.ts
80.57% (-4% 🔻)
47.83% (-16.17% 🔻)
100%
80.57% (-4% 🔻)
🟢
... / db.module.ts
89.06% (+0.78% 🔼)
62.5% (-20.83% 🔻)
80%
89.06% (+0.78% 🔼)
🟡
... / migration-helpers.ts
74.54% (-1.48% 🔻)
86.76% (+6.17% 🔼)
90.91%
74.54% (-1.48% 🔻)
🔴
... / benchmark.service.ts
43.36% (-11.89% 🔻)
66.67%
36.36% (-3.64% 🔻)
43.36% (-11.89% 🔻)
🔴
... / base-block-dispatcher.ts
19% (-28.35% 🔻)
100%
4.35% (-5.65% 🔻)
19% (-28.35% 🔻)
🔴
... / block-dispatcher.ts
26.98% (-14.01% 🔻)
66.67%
25% (-3.57% 🔻)
26.98% (-14.01% 🔻)
🔴
... / worker-block-dispatcher.ts
36.17% (-14.04% 🔻)
100%
25% (-2.27% 🔻)
36.17% (-14.04% 🔻)
🔴
... / coreDictionary.ts
45.33% (-54.67% 🔻)
87.5% (-6.94% 🔻)
77.78% (-22.22% 🔻)
45.33% (-54.67% 🔻)
🟡
... / dictionary.service.ts
67.01% (-18.14% 🔻)
82.35% (-3.36% 🔻)
83.33% (-7.58% 🔻)
67.01% (-18.14% 🔻)
🟡
... / dictionaryV1.ts
71.43% (-21.8% 🔻)
73.81% (-4.45% 🔻)
91.67% (-8.33% 🔻)
71.43% (-21.8% 🔻)
🟡
... / dictionaryV2.ts
78.42% (-3.25% 🔻)
71.88% (+6.66% 🔼)
88.89% (-11.11% 🔻)
78.42% (-3.25% 🔻)
🔴
... / ds-processor.service.ts
39.37% (-22.72% 🔻)
75%
58.33% (-29.17% 🔻)
39.37% (-22.72% 🔻)
🔴
... / dynamic-ds.service.ts
59.84% (-30.35% 🔻)
65% (-1.67% 🔻)
80% (-5.71% 🔻)
59.84% (-30.35% 🔻)
🟢
... / inMemoryCache.service.ts
86.21% (-13.79% 🔻)
100%
75% (-25% 🔻)
86.21% (-13.79% 🔻)
🔴
... / indexer.manager.ts
16.13% (-17.08% 🔻)
100%
10% (-2.5% 🔻)
16.13% (-17.08% 🔻)
🟡
... / PoiBlock.ts
73.39% (-25% 🔻)
57.89% (-38.66% 🔻)
75% (-25% 🔻)
73.39% (-25% 🔻)
🔴
... / poi.service.ts
56.64% (+32.71% 🔼)
55.56% (-44.44% 🔻)
80% (+51.43% 🔼)
56.64% (+32.71% 🔼)
🔴
... / poiModel.ts
40% (-23.64% 🔻)
71.43%
44.44% (-12.7% 🔻)
40% (-23.64% 🔻)
🔴
... / poiSync.service.ts
55.88% (-31% 🔻)
77.61% (+1.05% 🔼)
88.89% (-3.42% 🔻)
55.88% (-31% 🔻)
🟡
... / project.service.ts
66.45% (-13.55% 🔻)
71.93% (+1.75% 🔼)
80.77% (-3.23% 🔻)
66.45% (-13.55% 🔻)
🟡
... / sandbox.ts
60.49% (-7.49% 🔻)
57.14%
57.14% (-4.4% 🔻)
60.49% (-7.49% 🔻)
🔴
... / smartBatch.service.ts
10.43% (-13.91% 🔻)
100%
12.5% (-1.79% 🔻)
10.43% (-13.91% 🔻)
🟡
... / store.service.ts
65.91% (-0.14% 🔻)
69.23% (+0.81% 🔼)
58.62% (+1.48% 🔼)
65.91% (-0.14% 🔻)
🔴
... / entity.ts
19.23% (-42.31% 🔻)
100% 0%
19.23% (-42.31% 🔻)
🔴
... / store.ts
13.11% (-19.09% 🔻)
100% 0%
13.11% (-19.09% 🔻)
🟢
... / cacheModel.ts
84.76% (-0.31% 🔻)
87.67% (+9.36% 🔼)
76.19%
84.76% (-0.31% 🔻)
🟡
... / cachePoi.ts
75.53% (-18.09% 🔻)
88.89%
71.43% (-11.9% 🔻)
75.53% (-18.09% 🔻)
🟢
... / cacheable.ts
89.66% (-0.97% 🔻)
75% 100%
89.66% (-0.97% 🔻)
🟡
... / csvStore.service.ts
76.92% (-14.1% 🔻)
80%
80% (-20% 🔻)
76.92% (-14.1% 🔻)
🟢
... / test.runner.ts
94.67% (-4.67% 🔻)
73.33%
66.67% (-33.33% 🔻)
94.67% (-4.67% 🔻)
🔴
... / testing.service.ts
12% (-16.57% 🔻)
100% 0%
12% (-16.57% 🔻)
🟡
... / unfinalizedBlocks.service.ts
63.19% (-20.79% 🔻)
96.72%
88% (-3.67% 🔻)
63.19% (-20.79% 🔻)
🔴
... / worker.builder.ts
59.83% (-19.36% 🔻)
65.38% 80%
59.83% (-19.36% 🔻)
🔴
... / worker.cache.service.ts
48.78% (-9.76% 🔻)
100% 0%
48.78% (-9.76% 🔻)
🔴
... / worker.connectionPoolState.manager.ts
38.21% (-22.76% 🔻)
100% 0%
38.21% (-22.76% 🔻)
🔴
... / worker.dynamic-ds.service.ts
44.44% (-17.78% 🔻)
100% 0%
44.44% (-17.78% 🔻)
🔴
... / worker.service.ts
20.35% (-24.29% 🔻)
100% 0%
20.35% (-24.29% 🔻)
🟢
... / worker.store.service.ts
80% (-2.61% 🔻)
100% 50%
80% (-2.61% 🔻)
🔴
... / worker.ts
41.82% (-0.63% 🔻)
100% 0%
41.82% (-0.63% 🔻)
🔴
... / worker.unfinalizedBlocks.service.ts
33.33% (-66.67% 🔻)
100%
0% (-100% 🔻)
33.33% (-66.67% 🔻)
🔴
... / logger.ts
44.74% (-19.74% 🔻)
33.33%
40% (+20% 🔼)
44.74% (-19.74% 🔻)
🔴
... / event.listener.ts
43.43% (-37.37% 🔻)
100%
23.08% (-1.92% 🔻)
43.43% (-37.37% 🔻)
🔴
... / health.controller.ts
37.93% (-17.24% 🔻)
100%
33.33% (-16.67% 🔻)
37.93% (-17.24% 🔻)
🔴
... / health.service.ts
26.03% (-31.51% 🔻)
100%
16.67% (-3.33% 🔻)
26.03% (-31.51% 🔻)
🔴
... / meta.service.ts
23.81% (-45.71% 🔻)
100% (+20% 🔼)
27.27% (-12.73% 🔻)
23.81% (-45.71% 🔻)
🔴
... / ready.controller.ts
34.78% (-21.74% 🔻)
100%
33.33% (-16.67% 🔻)
34.78% (-21.74% 🔻)
🔴
... / ready.service.ts
54.17% (-37.5% 🔻)
100%
50% (-16.67% 🔻)
54.17% (-37.5% 🔻)
🔴
... / forceClean.service.ts
22.08% (-4.24% 🔻)
100% 0%
22.08% (-4.24% 🔻)
🔴
... / reindex.service.ts
14.73% (-18.6% 🔻)
100% 0%
14.73% (-18.6% 🔻)
🟡
... / autoQueue.ts
60.3% (-28.09% 🔻)
85.11%
73.08% (-6.09% 🔻)
60.3% (-28.09% 🔻)
🟡
... / blocks.ts
77.78% (-22.22% 🔻)
88.89%
66.67% (-33.33% 🔻)
77.78% (-22.22% 🔻)
🟢
... / promise.ts
86.44% (-5.32% 🔻)
100% (+13.64% 🔼)
71.43% (-14.29% 🔻)
86.44% (-5.32% 🔻)
🔴
... / yargs.ts
44.38% (-1.11% 🔻)
100% 14.29%
44.38% (-1.11% 🔻)
🟢
... / SubqueryProject.ts
95.38% (-0.14% 🔻)
83.33% (+0.98% 🔼)
87.5% (+1.79% 🔼)
95.38% (-0.14% 🔻)
🟡
... / apiPromise.connection.ts
77.08% (+8% 🔼)
50% (-30% 🔻)
62.5% (+19.64% 🔼)
77.08% (+8% 🔼)
🔴
... / worker-block-dispatcher.service.ts
24.64% (-12.32% 🔻)
100% 0%
24.64% (-12.32% 🔻)
🟢
... / substrateDictionary.service.ts
98.06% (+7.49% 🔼)
71.43% (-1.3% 🔻)
100% (+20% 🔼)
98.06% (+7.49% 🔼)
🟢
... / substrateDictionaryV1.ts
85.05% (-0.43% 🔻)
71.11% (+1.34% 🔼)
84.62% (+1.28% 🔼)
85.05% (-0.43% 🔻)
🟡
... / substrateDictionaryV2.ts
73.03% (-2.48% 🔻)
75% 33.33%
73.03% (-2.48% 🔻)
🟢
... / fetch.module.ts
90% (-1.88% 🔻)
50% (-25% 🔻)
100%
90% (-1.88% 🔻)
🔴
... / indexer.manager.ts
56.35% (-1.2% 🔻)
100%
20% (+10.91% 🔼)
56.35% (-1.2% 🔻)
🟢
... / runtimeService.ts
94.29% (+2.08% 🔼)
81.82% (-7.07% 🔻)
100% (+20% 🔼)
94.29% (+2.08% 🔼)
🔴
... / http.ts
49.03% (-30.89% 🔻)
40%
28.57% (-2.2% 🔻)
49.03% (-30.89% 🔻)
🟢
... / 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% 🔻)
🟢
... / builder.ts
92.77%
82.14% (-0.62% 🔻)
100% 92.77%
🟡
... / logger.ts
70.2% (+0.6% 🔼)
54.55% (-0.45% 🔻)
76.92% (+1.92% 🔼)
70.2% (+0.6% 🔼)

Test suite run failed

Failed tests: 9/545. Failed suites: 5/98.
  ● Store cache upper threshold › waits for flushing when threshold is met

    expect(received).toBeGreaterThanOrEqual(expected)

    Expected: >= 1000
    Received:    999

      288 |
      289 |     // Should be more than 1s, we set the db tx.commit to take 1s
    > 290 |     expect(end - start).toBeGreaterThanOrEqual(1000);
          |                         ^
      291 |   });
      292 | });
      293 |

      at Object.<anonymous> (packages/node-core/src/indexer/storeCache/storeCache.service.spec.ts:290:25)


  ● 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)


  ● Codegen can generate schema › Should dedupe enums

    ENOENT: no such file or directory, open '/home/runner/work/subql/subql/packages/cli/test/schemaTest/src/types/models/foo.ts'




  ● Cli publish › should upload appropriate project to IPFS

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

    npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-06-05T01_31_48_016Z-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 error code ERESOLVE
    npm error ERESOLVE unable to resolve dependency tree
    npm error
    npm error While resolving: mocked_starter@1.0.0
    npm error Found: @polkadot/api@10.13.1
    npm error node_modules/@polkadot/api
    npm error   dev @polkadot/api@"^10" from the root project
    npm error
    npm error Could not resolve dependency:
    npm error peer @polkadot/api@"^11" from @subql/types@3.6.0
    npm error node_modules/@subql/types
    npm error   dev @subql/types@"latest" from the root project
    npm error
    npm error Fix the upstream dependency conflict, or retry
    npm error this command with --force or --legacy-peer-deps
    npm error to accept an incorrect (and potentially broken) dependency resolution.
    npm error
    npm error
    npm error For a full report see:
    npm error /home/runner/.npm/_logs/2024-06-05T01_31_48_016Z-eresolve-report.txt

    npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-06-05T01_31_48_016Z-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 error code ERESOLVE
    npm error ERESOLVE unable to resolve dependency tree
    npm error
    npm error While resolving: mocked_starter@1.0.0
    npm error Found: @polkadot/api@10.13.1
    npm error node_modules/@polkadot/api
    npm error   dev @polkadot/api@"^10" from the root project
    npm error
    npm error Could not resolve dependency:
    npm error peer @polkadot/api@"^11" from @subql/types@3.6.0
    npm error node_modules/@subql/types
    npm error   dev @subql/types@"latest" from the root project
    npm error
    npm error Fix the upstream dependency conflict, or retry
    npm error this command with --force or --legacy-peer-deps
    npm error to accept an incorrect (and potentially broken) dependency resolution.
    npm error
    npm error
    npm error For a full report see:
    npm error /home/runner/.npm/_logs/2024-06-05T01_31_48_016Z-eresolve-report.txt

    npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-06-05T01_31_48_016Z-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 error code ERESOLVE
    npm error ERESOLVE unable to resolve dependency tree
    npm error
    npm error While resolving: mocked_starter@1.0.0
    npm error Found: @polkadot/api@10.13.1
    npm error node_modules/@polkadot/api
    npm error   dev @polkadot/api@"^10" from the root project
    npm error
    npm error Could not resolve dependency:
    npm error peer @polkadot/api@"^11" from @subql/types@3.6.0
    npm error node_modules/@subql/types
    npm error   dev @subql/types@"latest" from the root project
    npm error
    npm error Fix the upstream dependency conflict, or retry
    npm error this command with --force or --legacy-peer-deps
    npm error to accept an incorrect (and potentially broken) dependency resolution.
    npm error
    npm error
    npm error For a full report see:
    npm error /home/runner/.npm/_logs/2024-06-05T01_31_54_401Z-eresolve-report.txt

    npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-06-05T01_31_54_401Z-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 error code ERESOLVE
    npm error ERESOLVE unable to resolve dependency tree
    npm error
    npm error While resolving: mocked_starter@1.0.0
    npm error Found: @polkadot/api@10.13.1
    npm error node_modules/@polkadot/api
    npm error   dev @polkadot/api@"^10" from the root project
    npm error
    npm error Could not resolve dependency:
    npm error peer @polkadot/api@"^11" from @subql/types@3.6.0
    npm error node_modules/@subql/types
    npm error   dev @subql/types@"latest" from the root project
    npm error
    npm error Fix the upstream dependency conflict, or retry
    npm error this command with --force or --legacy-peer-deps
    npm error to accept an incorrect (and potentially broken) dependency resolution.
    npm error
    npm error
    npm error For a full report see:
    npm error /home/runner/.npm/_logs/2024-06-05T01_31_54_401Z-eresolve-report.txt

    npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-06-05T01_31_54_401Z-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 error code ERESOLVE
    npm error ERESOLVE unable to resolve dependency tree
    npm error
    npm error While resolving: mocked_starter@1.0.0
    npm error Found: @polkadot/api@10.13.1
    npm error node_modules/@polkadot/api
    npm error   dev @polkadot/api@"^10" from the root project
    npm error
    npm error Could not resolve dependency:
    npm error peer @polkadot/api@"^11" from @subql/types@3.6.0
    npm error node_modules/@subql/types
    npm error   dev @subql/types@"latest" from the root project
    npm error
    npm error Fix the upstream dependency conflict, or retry
    npm error this command with --force or --legacy-peer-deps
    npm error to accept an incorrect (and potentially broken) dependency resolution.
    npm error
    npm error
    npm error For a full report see:
    npm error /home/runner/.npm/_logs/2024-06-05T01_31_54_401Z-eresolve-report.txt

    npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-06-05T01_31_54_401Z-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 eca2872

Copy link
Collaborator

@stwiname stwiname left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of suggestions:

  • Make the montior service an optional dependency, this will clean up some tests
  • Another option to simplify integration, would be to use event emitter to write, to the monitor service, that way we don't need to inject the service everywhere

Copy link
Collaborator

@stwiname stwiname left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need to log the block hash being indexed.

@stwiname
Copy link
Collaborator

I think POI being enabled needs to set the size to non-zero. But we should determine the size based on the network project

@jiqiang90 jiqiang90 force-pushed the monitor-service-2 branch from 340105e to e6c4d58 Compare June 4, 2024 05:26
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 jiqiang90 force-pushed the monitor-service-2 branch from e6c4d58 to f7cbeb6 Compare June 4, 2024 05:31
@stwiname stwiname merged commit 8bd8354 into main Jun 5, 2024
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants