querysub 0.416.0 → 0.417.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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/tempnotes.txt +0 -9
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "querysub",
3
- "version": "0.416.0",
3
+ "version": "0.417.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",
package/tempnotes.txt CHANGED
@@ -2,18 +2,9 @@
2
2
 
3
3
  Local CYOA + Local FunctionRunner works
4
4
 
5
- 1) Deploy
6
- 2) Verify this works
7
-
8
- 1) verify this warning is no longer in our logs "Node list is missing nodes, resyncing node"
9
- - We should check the logs. I'm assuming what happened is that at some point some server thought it was the wrong node ID and deleted it?
10
- - It's generally the same ones, except new ones get added.
11
-
12
-
13
5
  -1) A lot of API calls are getting locked up and never finishing. We need to fix this. What the fuck is happening? It happens a lot with audio calls, as we make a lot of audio calls, but we can probably replicate it with non-audio calls. I think it happened with some embeddings, although we did create a lot of embeddings, and it only happened at the end. If it's only an audio thing, that's different, but we still need some kind of timeout. But I don't think it's an audio thing, I think it's not actually starting.
14
6
 
15
7
 
16
-
17
8
  0) SHARD THE FUNCTION RUNNER!
18
9
  - And secondary sharding for backup...
19
10
  - First shard locally