querysub 0.369.0 → 0.370.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/bin/movelogs.js CHANGED
@@ -1,4 +1,7 @@
1
1
  #!/usr/bin/env node
2
2
 
3
+ process.argv.push("--nobreak");
4
+ process.argv.push("--public");
5
+
3
6
  require("typenode");
4
7
  require("../src/diagnostics/logs/IndexedLogs/moveLogsEntry");
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "querysub",
3
- "version": "0.369.0",
3
+ "version": "0.370.0",
4
4
  "main": "index.js",
5
5
  "license": "MIT",
6
6
  "note1": "note on node-forge fork, see https://github.com/digitalbazaar/forge/issues/744 for details",
@@ -23,6 +23,7 @@ import { green, magenta } from "socket-function/src/formatting/logColors";
23
23
  import { parseFilterSelector } from "../misc/filterable";
24
24
  import path from "path";
25
25
  import { Querysub } from "../4-querysub/QuerysubController";
26
+ import { IndexedLogs } from "../diagnostics/logs/IndexedLogs/IndexedLogs";
26
27
 
27
28
  async function main() {
28
29
  Error.stackTraceLimit = 20;
@@ -39,6 +40,10 @@ async function main() {
39
40
 
40
41
  await Querysub.hostService("PathFunctionRunnerMain");
41
42
 
43
+ if (!isPublic()) {
44
+ IndexedLogs.runLogMoveLoop();
45
+ }
46
+
42
47
  // Use a fairly high stick time (the default is 10s), because having wait to sync data is very slow,
43
48
  // and the function runner SHOULD have more memory than the clients, and much faster network speeds
44
49
  // (it should be on the same local network as the path value authorities).
@@ -19,19 +19,12 @@ IMPORTANT! Now I am properly calling shutdown, so none of the streamed logs shou
19
19
 
20
20
 
21
21
 
22
- 0) Deploy again
23
- 1) Verify isPublic searching works (from our local machine)
24
-
25
-
26
- 1) Deploy our changes
27
-
28
22
 
29
23
  2) Create lot of remote server logs
30
24
  - Via our refresh loop
31
25
 
32
-
33
- 3) Create and deploy service for movelogs
34
- 3.0) Update preferred entrypoint to be the movelogs entrypoint
26
+ 3) Deploy service for movelogs
27
+ "yarn movelogs"
35
28
 
36
29
  0) Run move logs in function runner, in development, just so we don't get too far behind
37
30