-
Notifications
You must be signed in to change notification settings - Fork 4
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
ci: merge staging to master #379
Commits on Jun 8, 2022
-
fix: adding dependencies for
async-locks
,db
,resources
and `er……rors` Updating dependencies to bring in new libraries such as locks, resources and errors. Some domains have been updated to use this change.
Configuration menu - View commit details
-
Copy full SHA for 0649851 - Browse repository at this point
Copy the full SHA 0649851View commit details -
Updated pkgs.nix to a5774e76bb8c3145eac524be62375c937143b80c Updated node2nix to 1.11.0 and loading directly from GitHub Updated pkg to 5.6.0 and using pkg-fetch 3.3 base binaries Updated to TypeScript 4.5+ Updated @types/node to 16.11.7 Updated node-gyp-build to 4.4.0 Updated typedoc to 0.22.15, the .nojekyll generation is automatic Changed to target ES2021 as node 16 supports it Bin executable duct-tape in default.nix because node2nix no longer generates bin executables Updated pkg builds hashes to v16.14.2 and specified target node range
Configuration menu - View commit details
-
Copy full SHA for b8598ed - Browse repository at this point
Copy the full SHA b8598edView commit details -
build: updating core libraries
Updated js-async-init from 1.6.0 to 1.7.1 Updated js-async-locks from 2.0.0 to 2.2.0 Updated js-db from 3.2.0 to 3.2.3 Updating js-workers from 1.2.5 to 1.3.1
Configuration menu - View commit details
-
Copy full SHA for 69d42f9 - Browse repository at this point
Copy the full SHA 69d42f9View commit details -
feat: static descriptions and exit codes for all errors
The `data` POJO that was originally supplied in the constructor as the second parameter is now part of the `options` parameter and most places in the code have been updated to match this. #304
Configuration menu - View commit details
-
Copy full SHA for b45be10 - Browse repository at this point
Copy the full SHA b45be10View commit details -
feat: using
cause
property to establish error chainWhen any error is thrown as the result of another error occurring, the original error is now contained within the `cause` property of the new error. #304
Configuration menu - View commit details
-
Copy full SHA for 1d2af00 - Browse repository at this point
Copy the full SHA 1d2af00View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7ac6653 - Browse repository at this point
Copy the full SHA 7ac6653View commit details -
feat: error serialisation/deserialisation over gRPC incorporating err…
…or chaining Our gRPC `toError` and `fromError` utils are now able to serialise and deserialise Polykey and non-Polykey errors (as well as non-errors), including the entire error chain if this exists. Also includes the ability to filter out sensitive data, for example when the error is being sent to another agent. Errors sent over the network in this way are now additionally wrapped on the receiving side in an `ErrorPolykeyRemote` to make the source of the error more clear. #304
Configuration menu - View commit details
-
Copy full SHA for 72263c5 - Browse repository at this point
Copy the full SHA 72263c5View commit details -
feat: added logger to service handlers
All of the agent and client service handlers are now passed a shared logger that is used to log errors to stderr. #304
Configuration menu - View commit details
-
Copy full SHA for e5dfadb - Browse repository at this point
Copy the full SHA e5dfadbView commit details -
Configuration menu - View commit details
-
Copy full SHA for 631a670 - Browse repository at this point
Copy the full SHA 631a670View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4478a06 - Browse repository at this point
Copy the full SHA 4478a06View commit details -
Configuration menu - View commit details
-
Copy full SHA for 74b390d - Browse repository at this point
Copy the full SHA 74b390dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 91aeb73 - Browse repository at this point
Copy the full SHA 91aeb73View commit details -
Configuration menu - View commit details
-
Copy full SHA for abe1c3b - Browse repository at this point
Copy the full SHA abe1c3bView commit details -
fix: integrating db changes into Notifications
Note that the `transaction` and `_transaction` methods still need te removed.
Configuration menu - View commit details
-
Copy full SHA for 8c8f5af - Browse repository at this point
Copy the full SHA 8c8f5afView commit details -
fix: integrating db changes into
Discovery
I opted not to use transactions for the most part. Adding things to the queue has to be handled with locking anyway so I opted to rely on that istead. This still bears testing though.
Configuration menu - View commit details
-
Copy full SHA for fc962a1 - Browse repository at this point
Copy the full SHA fc962a1View commit details -
Configuration menu - View commit details
-
Copy full SHA for d33fc5a - Browse repository at this point
Copy the full SHA d33fc5aView commit details
Commits on Jun 9, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 26dddde - Browse repository at this point
Copy the full SHA 26ddddeView commit details -
Configuration menu - View commit details
-
Copy full SHA for ef8baf5 - Browse repository at this point
Copy the full SHA ef8baf5View commit details -
Configuration menu - View commit details
-
Copy full SHA for 16d0361 - Browse repository at this point
Copy the full SHA 16d0361View commit details -
Configuration menu - View commit details
-
Copy full SHA for 98a3c75 - Browse repository at this point
Copy the full SHA 98a3c75View commit details -
Configuration menu - View commit details
-
Copy full SHA for bfa77d0 - Browse repository at this point
Copy the full SHA bfa77d0View commit details -
Configuration menu - View commit details
-
Copy full SHA for aa62069 - Browse repository at this point
Copy the full SHA aa62069View commit details -
fix: fix for
GRPCServer
http2Servers
hackThis was throwing an error because the expected object structure changed. The typing is brittle here since we're going around typescript's back to get a private property.
Configuration menu - View commit details
-
Copy full SHA for 225d311 - Browse repository at this point
Copy the full SHA 225d311View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2afa473 - Browse repository at this point
Copy the full SHA 2afa473View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5e2ea88 - Browse repository at this point
Copy the full SHA 5e2ea88View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1e1f5e5 - Browse repository at this point
Copy the full SHA 1e1f5e5View commit details -
Configuration menu - View commit details
-
Copy full SHA for 68412c7 - Browse repository at this point
Copy the full SHA 68412c7View commit details -
fix: added locking back into sigchain
Sequence numbers and claim ids needed locking due to serialisation concerns
Configuration menu - View commit details
-
Copy full SHA for 497583f - Browse repository at this point
Copy the full SHA 497583fView commit details -
fix: added locking back into notifications
Notifications have strict ordering in the DB, therefore locking is required.
Configuration menu - View commit details
-
Copy full SHA for c2de660 - Browse repository at this point
Copy the full SHA c2de660View commit details -
Configuration menu - View commit details
-
Copy full SHA for 73e3891 - Browse repository at this point
Copy the full SHA 73e3891View commit details -
Configuration menu - View commit details
-
Copy full SHA for 845d7e4 - Browse repository at this point
Copy the full SHA 845d7e4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 69e7d3a - Browse repository at this point
Copy the full SHA 69e7d3aView commit details -
fix: fixing vaultManager tests
There are still some tests failing due to cloning and pulling. Seems like a problem with the HTTP API for cloning.
Configuration menu - View commit details
-
Copy full SHA for 1aa9044 - Browse repository at this point
Copy the full SHA 1aa9044View commit details -
Configuration menu - View commit details
-
Copy full SHA for aaf158c - Browse repository at this point
Copy the full SHA aaf158cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 607c126 - Browse repository at this point
Copy the full SHA 607c126View commit details -
Configuration menu - View commit details
-
Copy full SHA for e71c536 - Browse repository at this point
Copy the full SHA e71c536View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0ef9299 - Browse repository at this point
Copy the full SHA 0ef9299View commit details -
Configuration menu - View commit details
-
Copy full SHA for 09b83a3 - Browse repository at this point
Copy the full SHA 09b83a3View commit details -
There was a bug with the `fromJSON` method where it couldn't deserialise an error with an undefined cause (because this is removed by the replacer).
Configuration menu - View commit details
-
Copy full SHA for 18a4d77 - Browse repository at this point
Copy the full SHA 18a4d77View commit details -
Configuration menu - View commit details
-
Copy full SHA for 97beee9 - Browse repository at this point
Copy the full SHA 97beee9View commit details -
Configuration menu - View commit details
-
Copy full SHA for fbf13a0 - Browse repository at this point
Copy the full SHA fbf13a0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3e19974 - Browse repository at this point
Copy the full SHA 3e19974View commit details -
feat: updated
NodeConnectionManager
's resourceAcquire to handle err……ors properly Making use of the updated API to use the error provided to the resourceRelease.
Configuration menu - View commit details
-
Copy full SHA for e56f79e - Browse repository at this point
Copy the full SHA e56f79eView commit details -
feat: updated
NodeConnectionManager
to useLockBox
for object map…… locking Using `LockBox` allowed us to greatly simplify using the object map and creating connections.
Configuration menu - View commit details
-
Copy full SHA for 055c526 - Browse repository at this point
Copy the full SHA 055c526View commit details -
feat: updated
VaultManager
to useLockBox
for object map lockingUsing `LockBox` allowed us to greatly simplify using the object map and creating vaults.
Configuration menu - View commit details
-
Copy full SHA for c256620 - Browse repository at this point
Copy the full SHA c256620View commit details -
feat: format json affects error logging
Specifying `--format=json` will cause errors to be logged in json format. ErrorPolykeyRemote errors also now contain additional metadata about the origin node of the error. #323
Configuration menu - View commit details
-
Copy full SHA for 5dda0a4 - Browse repository at this point
Copy the full SHA 5dda0a4View commit details -
Had to fix `expectProcessError` to work with the raw JSON forms of the errors rather than attempting to parse the errors. This is due to the bin CLI errors being separate from the normal errors and the reviver being unable to revive them. I also had to fix how the `ErrorPolykeyRemote` converted the metadata with toJSON/fromJSON.
Configuration menu - View commit details
-
Copy full SHA for 19e9b3e - Browse repository at this point
Copy the full SHA 19e9b3eView commit details -
fix: added logic check to
NotificationsManager.readNotifications
There was a bug with the DB that is getting fixed. This just throws a clear error when a notification can't be read despite it being in the list of all notifications.
Configuration menu - View commit details
-
Copy full SHA for e528d9f - Browse repository at this point
Copy the full SHA e528d9fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 0a6442c - Browse repository at this point
Copy the full SHA 0a6442cView commit details -
test: fixed broken proxy tests
Problem was with the tests themselves so i've fixed the tests. If there are any similar issues crop up later, then we can explore the underlying cause in depth. However, it is low priority for now.
Configuration menu - View commit details
-
Copy full SHA for 600aa36 - Browse repository at this point
Copy the full SHA 600aa36View commit details -
Configuration menu - View commit details
-
Copy full SHA for f6339aa - Browse repository at this point
Copy the full SHA f6339aaView commit details -
There were places where ClientMetadata was not being provided to grpc calls (`{} as ClientMetadata`) however this information is required in order to construct ErrorPolykeyRemote. Where metadata is needed in tests it is either now taken from constants used in the tests or mocked. There was also an issue with error descriptions not being serialised/deserialised which is now fixed. Also some brittle test cases for error messages were removed.
Configuration menu - View commit details
-
Copy full SHA for 51c26a2 - Browse repository at this point
Copy the full SHA 51c26a2View commit details -
Configuration menu - View commit details
-
Copy full SHA for d0f82dd - Browse repository at this point
Copy the full SHA d0f82ddView commit details -
Configuration menu - View commit details
-
Copy full SHA for 16ff937 - Browse repository at this point
Copy the full SHA 16ff937View commit details -
Configuration menu - View commit details
-
Copy full SHA for bd95bc8 - Browse repository at this point
Copy the full SHA bd95bc8View commit details -
feat: updating
@matrixai/db
to^4.0.1
Had to fix the usage in 5 domains.
Configuration menu - View commit details
-
Copy full SHA for 52755ec - Browse repository at this point
Copy the full SHA 52755ecView commit details -
Configuration menu - View commit details
-
Copy full SHA for d88278c - Browse repository at this point
Copy the full SHA d88278cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2127b0d - Browse repository at this point
Copy the full SHA 2127b0dView commit details -
tests: fixed odd internal error for one test
It was just a problem with trying to connect to '0.0.0.0' with the UTP socket.
Configuration menu - View commit details
-
Copy full SHA for 8ec9cdb - Browse repository at this point
Copy the full SHA 8ec9cdbView commit details -
Configuration menu - View commit details
-
Copy full SHA for 58d3616 - Browse repository at this point
Copy the full SHA 58d3616View commit details -
Configuration menu - View commit details
-
Copy full SHA for 12250b0 - Browse repository at this point
Copy the full SHA 12250b0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7543a3c - Browse repository at this point
Copy the full SHA 7543a3cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 934bbd8 - Browse repository at this point
Copy the full SHA 934bbd8View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8a5f8b2 - Browse repository at this point
Copy the full SHA 8a5f8b2View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3ba04db - Browse repository at this point
Copy the full SHA 3ba04dbView commit details -
refactor: moving
ClientMetadata
to GRPC domainHaving `ClientMetadata` in the top-level types caused an import loop. By moving it and `ErrorPolykeyRemote` to the grpc domain this loop is resolved. This was the best option since now all usage of `ClientMetadata` is inside the grpc domain.
Configuration menu - View commit details
-
Copy full SHA for a11fc55 - Browse repository at this point
Copy the full SHA a11fc55View commit details -
Configuration menu - View commit details
-
Copy full SHA for b6c30b8 - Browse repository at this point
Copy the full SHA b6c30b8View commit details -
feat: filtering error logging in service handlers
We only want to log out server errors on the server side, so we now apply filters on errors before logging them.
Configuration menu - View commit details
-
Copy full SHA for 6e20915 - Browse repository at this point
Copy the full SHA 6e20915View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6efc963 - Browse repository at this point
Copy the full SHA 6efc963View commit details -
Configuration menu - View commit details
-
Copy full SHA for a01c7ea - Browse repository at this point
Copy the full SHA a01c7eaView commit details -
Configuration menu - View commit details
-
Copy full SHA for 9730e5a - Browse repository at this point
Copy the full SHA 9730e5aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 9c2bdea - Browse repository at this point
Copy the full SHA 9c2bdeaView commit details -
fix: service handlers check for client error chains
Sometimes an error is only considered a client error when part of the chain of another error (for example ErrorPolykeyRemote) so it is now possible to specify this array. #304
Configuration menu - View commit details
-
Copy full SHA for 4cd91b2 - Browse repository at this point
Copy the full SHA 4cd91b2View commit details
Commits on Jun 14, 2022
-
feat: added
nodesGetAll
bin command and service handlerRetrieves all buckets from the NodeGraph
Configuration menu - View commit details
-
Copy full SHA for 6185c23 - Browse repository at this point
Copy the full SHA 6185c23View commit details -
- added getBuckets test for distance and lastUpdated order - resetting buckets work - changing utility names
Configuration menu - View commit details
-
Copy full SHA for 9b53a0a - Browse repository at this point
Copy the full SHA 9b53a0aView commit details -
feat: added
NodeGraph.getClosestNodes()
Implemented `getClosestNodes()` and relevant tests in `NodeGraph.test.ts`. Relates to #212
Configuration menu - View commit details
-
Copy full SHA for d08bbe9 - Browse repository at this point
Copy the full SHA d08bbe9View commit details -
fix:
NodeManager.setNode
Properly handles adding new node when buck……et is full Logic of adding nodes has been split between `NodeManager` and `NodeGraph`. The `NodeGraph.setNode` just handles adding a node to the bucket where the `NodeManager.setNode` contains the logic of when to add the node Relates #359
Configuration menu - View commit details
-
Copy full SHA for a43851b - Browse repository at this point
Copy the full SHA a43851bView commit details -
Configuration menu - View commit details
-
Copy full SHA for dc4ec33 - Browse repository at this point
Copy the full SHA dc4ec33View commit details -
feat: added
connectionEstablishedCallback
toProxy
Added a callback to the `Proxy` that is called when a `ForwardConnection` or `ReverseConnection` is established and authenticated. It is called with the following connection information; `remoteNodeId`, `remoteHost`, `remotePort` and `type`. They type signifies if it was a forward or reverse connection. Note that this is only triggered by composed connections. Added a test for if the callback was called when a `ReverseConnection` is established. Relates #332 Relates #344
Configuration menu - View commit details
-
Copy full SHA for ea32dc7 - Browse repository at this point
Copy the full SHA ea32dc7View commit details -
feat:
Proxy
trigger adding nodes toNodegraph
Added an event to the `EventBus` that is triggered by the `Proxy`'s `connectionEstablishedCallback`. this adds the node to the `NodeGraph`. Related #344
Configuration menu - View commit details
-
Copy full SHA for a36cd3a - Browse repository at this point
Copy the full SHA a36cd3aView commit details -
feat: added optional timeout timers to
NodeConnectionManager
methodsIn some cases we want to specify how long we attempt to connect to a node on a per-connection basis. Related #363
Configuration menu - View commit details
-
Copy full SHA for cb47f8b - Browse repository at this point
Copy the full SHA cb47f8bView commit details -
refactor: updated implementation of
nodePing
Added `nodePing` command to `NodeConnectionManager` and `NodeManager.nodePing` calls that now. the new `nodePing` command essentially attempts to create a connection to the target node. In this process we authenticate the connection and check that the nodeIds match. If no address is provided it will default to trying to find the node through kademlia. Related #322
Configuration menu - View commit details
-
Copy full SHA for fa39cd5 - Browse repository at this point
Copy the full SHA fa39cd5View commit details -
feat:
NodeManager.setNode
authenticates the added node`setNode` now authenticates the node you are trying to add. Added a flag for skipping this authentication as well as a timeout timer for the authentication. this is shared between authentication new node and the old node if the bucket is full. Related #322
Configuration menu - View commit details
-
Copy full SHA for e925034 - Browse repository at this point
Copy the full SHA e925034View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7815b2e - Browse repository at this point
Copy the full SHA 7815b2eView commit details -
fix: squash into ping node changes.
Updated `NodeConnectionManager.pingNode` to just use the proxy connection. #322
Configuration menu - View commit details
-
Copy full SHA for 9505e20 - Browse repository at this point
Copy the full SHA 9505e20View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0e34a17 - Browse repository at this point
Copy the full SHA 0e34a17View commit details -
feat: setNode concurrently pings multiple nodes
`setNode` now pings 3 nodes concurrently, updating ones that respond and removing ones that don't. If there is room in the bucket afterwards then we add the new node. #322
Configuration menu - View commit details
-
Copy full SHA for 9764213 - Browse repository at this point
Copy the full SHA 9764213View commit details -
Configuration menu - View commit details
-
Copy full SHA for a02cfea - Browse repository at this point
Copy the full SHA a02cfeaView commit details -
feat: async queueing for setting nodes
`setNode` now has a `blocking` flag that defaults to false. If it encounters a full bucket when adding a node then it will add the operation to the queue and asynchronously trys a blocking `setNode` in the background. `setNode`s will only be added to the queue if the bucket was full. #322
Configuration menu - View commit details
-
Copy full SHA for 4460779 - Browse repository at this point
Copy the full SHA 4460779View commit details -
feat: establishing a
NodeConnection
adds the node to the nodeGraph`NodeConnectionManager` now takes `NodeGraph` in the `nodeConnectionManager.start` method. It has to be part of the start method since they are co-dependent. `NodeConnectionManager` cals `NodeManager.setNode()` when a connection is established. This fulfills the condition of adding a node to the graph during a forward connection. Fixed up tests that were failing in relation to the `NodeManager` `StartStop` conversion. #322
Configuration menu - View commit details
-
Copy full SHA for aa7c4bc - Browse repository at this point
Copy the full SHA aa7c4bcView commit details -
feat: implemented
NodeManager.refreshBucket()
This method preforms the kademlia `refreshBucket` operation. It selects a random node within the bucket and preforms a search for that node. The process exchanges node information with any nodes it connects to. #345
Configuration menu - View commit details
-
Copy full SHA for 04091f2 - Browse repository at this point
Copy the full SHA 04091f2View commit details -
feat: implemented no activity timers and queuing for
refreshBucket
Added queuing for `refreshBucket`. This means that buckets will be refreshed one at a time sequentially. This is to avoid doing a lot of costly refreshing all at once. Added no activity for buckets. If a bucket hasn't been touched for a while, 1 hour by default, it will add a refresh bucket operation to the queue. Timers are disabled for buckets already in the queue. Only 1 timer is used for all buckets since only one of them can have the shortest timer and that's all we really care about. #345
Configuration menu - View commit details
-
Copy full SHA for 4dec90b - Browse repository at this point
Copy the full SHA 4dec90bView commit details -
feat: refreshing buckets when entering network
`nodeConnectionManager.syncNodeGraph` now refreshes all buckets above the closest node as per the kademlia spec. This means adding a lot of buckets to the refresh bucket queue when an agent is started. #345
Configuration menu - View commit details
-
Copy full SHA for ee53cfa - Browse repository at this point
Copy the full SHA ee53cfaView commit details -
feat: abort controller support for
NodeManager.refreshBucket
Added support to cancel out of a `refreshBucket` operation. This is to allow faster stopping of the `NodeManager` by aborting out of a slow `refreshBucket` operation. This has been implemented with the `AbortController`/`AbortSignal` API. This is not fully supported by Node14 so we're using the `node-abort-controller` to provide functionality for now. #345
Configuration menu - View commit details
-
Copy full SHA for 6302b0d - Browse repository at this point
Copy the full SHA 6302b0dView commit details -
Configuration menu - View commit details
-
Copy full SHA for c88bb81 - Browse repository at this point
Copy the full SHA c88bb81View commit details -
feat: generic
SetNodeQueue
class for queuingsetNode
operations`NodeManager.setNode` and `NodeConnectionManager.syncNodeGraph` now utilise a single, shared queue to asynchronously add nodes to the node graph without blocking the main loop. These methods are both blocking by default but can be made non-blocking by setting the `block` parameter to false. #322
Configuration menu - View commit details
-
Copy full SHA for 17396ab - Browse repository at this point
Copy the full SHA 17396abView commit details -
Configuration menu - View commit details
-
Copy full SHA for 8deddc5 - Browse repository at this point
Copy the full SHA 8deddc5View commit details -
refactor: renamed
SetNodeQueue
toQueue
Renamed `queueStart` and `queuePush` since `Queue` is its own class now Simplified some logic using the `promise` utility
Configuration menu - View commit details
-
Copy full SHA for 2782d8b - Browse repository at this point
Copy the full SHA 2782d8bView commit details -
tests: general fixes for failing tests
This contains fixes for failing tests as well as fixes for tests failing to exit when finished.
Configuration menu - View commit details
-
Copy full SHA for 40809b8 - Browse repository at this point
Copy the full SHA 40809b8View commit details -
syntax: added
@typescript-eslint/await-thenable
linting ruleThis checks if we await things that are not promises. This is not a problem per se, but we generally don't want to await random things.
Configuration menu - View commit details
-
Copy full SHA for 4a78c17 - Browse repository at this point
Copy the full SHA 4a78c17View commit details -
Configuration menu - View commit details
-
Copy full SHA for d1c803c - Browse repository at this point
Copy the full SHA d1c803cView commit details -
tests: added test to check if nodes are properly added to the seed no…
…des when entering the network This tests for if the Seed node contains the new nodes when they are created. It also checks if the new nodes discover each other after being created. Includes a change to `findNode`. It will no longer throw an error when failing to find the node. This will have to be thrown by the caller now. This was required by `refreshBucket` since it's very likely that we can't find the random node it is looking for.
Configuration menu - View commit details
-
Copy full SHA for f7aae95 - Browse repository at this point
Copy the full SHA f7aae95View commit details -
tests: Added agent service tests for
nodesChainDataGet
, `nodesClose……stLocalNode` and `nodesHolePunchMessage`
Configuration menu - View commit details
-
Copy full SHA for 22423a6 - Browse repository at this point
Copy the full SHA 22423a6View commit details -
DB and type changes using new transactions Linting Fixing timeouts
Configuration menu - View commit details
-
Copy full SHA for 0d277e8 - Browse repository at this point
Copy the full SHA 0d277e8View commit details -
Exports moved to end of the file as part of the `export {}` block Cleaned up TODOs and FIXMEs Fixed index and other incorrect imports Type fixes in utils
Configuration menu - View commit details
-
Copy full SHA for 2a0498d - Browse repository at this point
Copy the full SHA 2a0498dView commit details -
build: removing
node-abort-controller
polyfillAbort controller functionality is included in node now.
Configuration menu - View commit details
-
Copy full SHA for 17b5f6e - Browse repository at this point
Copy the full SHA 17b5f6eView commit details -
Configuration menu - View commit details
-
Copy full SHA for dac96be - Browse repository at this point
Copy the full SHA dac96beView commit details -
fix:
NodeConnectionManager.syncNodeGraph
now pings nodesNeed to ensure validity of nodes by pinging them before adding them to the node graph. #322
Configuration menu - View commit details
-
Copy full SHA for a522de3 - Browse repository at this point
Copy the full SHA a522de3View commit details -
Configuration menu - View commit details
-
Copy full SHA for b3766b6 - Browse repository at this point
Copy the full SHA b3766b6View commit details -
tests: expanding tests for root keypair changing
Added some tests to check that a root keyPair change propagates properly. Also added tests for the change for existing and new node connections. #317
Configuration menu - View commit details
-
Copy full SHA for 19f4796 - Browse repository at this point
Copy the full SHA 19f4796View commit details -
Configuration menu - View commit details
-
Copy full SHA for 551b7b6 - Browse repository at this point
Copy the full SHA 551b7b6View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9900d7a - Browse repository at this point
Copy the full SHA 9900d7aView commit details -
Configuration menu - View commit details
-
Copy full SHA for fcfaa01 - Browse repository at this point
Copy the full SHA fcfaa01View commit details -
nix: fixed building node2nix attribute in utils.nix
The package-lock.json was corrupted or not parseable by node2nix After destroying the `node_modules` directory and deleting the `package-lock.json`, we were able to recreate a working `package-lock.json` file If this occurs again, just destroy the `package-lock.json` and `node_modules` directory and regenerate.
Configuration menu - View commit details
-
Copy full SHA for fdae3d1 - Browse repository at this point
Copy the full SHA fdae3d1View commit details
Commits on Jun 15, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 60f5363 - Browse repository at this point
Copy the full SHA 60f5363View commit details -
Configuration menu - View commit details
-
Copy full SHA for cb6be2a - Browse repository at this point
Copy the full SHA cb6be2aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 6d43d47 - Browse repository at this point
Copy the full SHA 6d43d47View commit details
Commits on Jun 17, 2022
-
fix: issue with ts-node causing increased test times in bin tests
`ts-node` needs to be fixed to 10.7.0 for now, as 10.8.1 causes many bin tests (those using `pkSpawn`) to timeout. Also reduced test timeouts back to what they originally were now that the timeout problem is resolved.
Configuration menu - View commit details
-
Copy full SHA for 8c191ca - Browse repository at this point
Copy the full SHA 8c191caView commit details
Commits on Jun 22, 2022
-
Configuration menu - View commit details
-
Copy full SHA for b1eabeb - Browse repository at this point
Copy the full SHA b1eabebView commit details
Commits on Jun 23, 2022
-
fix: added
tslib
topkg
assetsThis is to fix a problem where `tslib` was not getting included during the packaging process resulting in an error.
Configuration menu - View commit details
-
Copy full SHA for 7fd16a6 - Browse repository at this point
Copy the full SHA 7fd16a6View commit details -
Configuration menu - View commit details
-
Copy full SHA for 89beb41 - Browse repository at this point
Copy the full SHA 89beb41View commit details
Commits on Jun 24, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 18437ce - Browse repository at this point
Copy the full SHA 18437ceView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2110634 - Browse repository at this point
Copy the full SHA 2110634View commit details -
feat: better logging for service handler errors
If an error was logged out by a service handler it would previously appear as `createClientService:`, which was too vague. The logger will now state the name of the handler.
Configuration menu - View commit details
-
Copy full SHA for 8cf52a4 - Browse repository at this point
Copy the full SHA 8cf52a4View commit details -
Configuration menu - View commit details
-
Copy full SHA for fc365b4 - Browse repository at this point
Copy the full SHA fc365b4View commit details -
Configuration menu - View commit details
-
Copy full SHA for eebeee3 - Browse repository at this point
Copy the full SHA eebeee3View commit details -
tests: fixes from testnet changes
The testnet PR brought in some changes that affect the NAT tests, so they needed to be modified slightly. - Adding a node to the node graph pings the node by default. We want to disable this in the NAT tests so we have more control over the pings. - Nodes add the details of any node that pings them. We can now remove some additional `nodes add` calls that were required to imitate this previously missing functionality.
Configuration menu - View commit details
-
Copy full SHA for ed2973e - Browse repository at this point
Copy the full SHA ed2973eView commit details -
Configuration menu - View commit details
-
Copy full SHA for a0adb35 - Browse repository at this point
Copy the full SHA a0adb35View commit details -
feat: removing
edmSimple
configurationNow that nodes add the details of a node that contacts them, we no longer need the `edmSimple` configuration to do this manually.
Configuration menu - View commit details
-
Copy full SHA for 8fdde54 - Browse repository at this point
Copy the full SHA 8fdde54View commit details -
style: linting and other style fixes
General linting, using capitals for constants in NAT utils, and lowercase test descriptions
Configuration menu - View commit details
-
Copy full SHA for 9800c4a - Browse repository at this point
Copy the full SHA 9800c4aView commit details -
fix: relay node for hole punch message now re-writes proxy address
A relay node for a hole punch message was previously not modifying the proxy address in the message (which is the "return address" used to contact the source node). For nodes behind a NAT, who do not know their own public address, they rely on this overwriting so that nodes do not try to contact them on their private, inaccessible address.
Configuration menu - View commit details
-
Copy full SHA for 4f8d17e - Browse repository at this point
Copy the full SHA 4f8d17eView commit details -
feat: added ability to pause
refreshBucketQueue
This will allow us to disable the queue for testing.
Configuration menu - View commit details
-
Copy full SHA for 1095f8f - Browse repository at this point
Copy the full SHA 1095f8fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 520b799 - Browse repository at this point
Copy the full SHA 520b799View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1e35180 - Browse repository at this point
Copy the full SHA 1e35180View commit details -
Configuration menu - View commit details
-
Copy full SHA for 856388b - Browse repository at this point
Copy the full SHA 856388bView commit details -
fix: async bug with composing connections
the composed flag was set at the beginning of the compose function causing another function to throw an error due to an undefined property if it was called at the same time.
Configuration menu - View commit details
-
Copy full SHA for 7c91ace - Browse repository at this point
Copy the full SHA 7c91aceView commit details -
Merge pull request #381 from MatrixAI/feature-nat-testing
Tests for NAT-Traversal and Hole-Punching
Configuration menu - View commit details
-
Copy full SHA for d60ab44 - Browse repository at this point
Copy the full SHA d60ab44View commit details
Commits on Jun 28, 2022
-
build: fix for
integration:nix
CI/CD jobProblem was to do with the `nix-build` process not patching the shebangs of the `polykey.js` script. this resulted in it failing to run due to not finding node in it's environment. The fix was to make `src/bin/polykey.js` and `src/bin/polykey-agent.ts` executable.
Configuration menu - View commit details
-
Copy full SHA for 0bc3af5 - Browse repository at this point
Copy the full SHA 0bc3af5View commit details