Skip to content
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

Documentation updating #1052

Merged
merged 30 commits into from
Feb 23, 2022
Merged

Conversation

AmberKiso
Copy link
Contributor

@AmberKiso AmberKiso commented Feb 20, 2022

Summary

Update documentation for a few outstanding bugs
Fix #863
Fix #864
Fix #906

Testing Plan

Looked at the .md files on Github's rich diff.

Breaking Change

Is this a breaking change? If yes, add notes below on why this is breaking and
what additional work is required, if any.

[ ] Yes
[X] No

NullSoldier and others added 8 commits February 16, 2022 16:18
* Update to latest napi-rs to fix BigInt usage (iron-fish#1014)

* Update RpcClient routes to use ApiNamespace enum (iron-fish#1013)

Minor change to RpcClient to utilize the ApiNamespace enum for route definition. Since we have a non-stringly-typed enum already, using it here just minimizes the risk of a typo that breaks a route.

* Move telemetry tags to fields (iron-fish#1026)

We are doing this to reduce cardinality. Indexes are created from the
combination of measurement and tags. This means every node session ends
up getting it's own indexes which blows out our cardinality and causes
causes InfluxDB to stop processing data. You can read more about this
issue here:

https://docs.influxdata.com/influxdb/cloud/write-data/best-practices/resolve-high-cardinalityg

* Fix ordering issue in creating telemetry node id (iron-fish#1027)

The issue is that Node.Init() happens before the telemetry node id is
created for the first time. We simply move that up, and configure it on
the SDK itself which gets passed to the constructed node.

* fix miners:mined scanning status (iron-fish#994)

* Return a Buffer instead of a NativeNote from decryption functions (iron-fish#1025)

* feat(ironfish): Move metrics monitor inside telemetry (iron-fish#1029)

* feat(ironfish): Submit peer metrics in telemetry  (iron-fish#1030)

* feat(ironfish): Move metrics monitor inside telemetry

* feat(ironfish): Submit peer metrics in telemetry

* Bump version to 0.1.23 (iron-fish#1028)

Co-authored-by: Derek Guenther <dguenther9@gmail.com>
Co-authored-by: mat-if <97762857+mat-if@users.noreply.github.com>
Co-authored-by: wd021 <dannywitters@gmail.com>
Co-authored-by: Rohan Jadvani <5459049+rohanjadvani@users.noreply.github.com>
Remove test:slow
Add referencing bugs fixed in the PR description.
@AmberKiso AmberKiso marked this pull request as ready for review February 20, 2022 18:50
@AmberKiso AmberKiso requested a review from a team as a code owner February 20, 2022 18:50
README.md Show resolved Hide resolved
@NullSoldier NullSoldier changed the base branch from master to staging February 22, 2022 21:19
@NullSoldier
Copy link
Contributor

NullSoldier commented Feb 22, 2022

I just retargeted this to staging, can you rebase this on staging? We try not to merge things into master. You can use git pull -r origin staging

NullSoldier and others added 16 commits February 22, 2022 19:59
Minor change to RpcClient to utilize the ApiNamespace enum for route definition. Since we have a non-stringly-typed enum already, using it here just minimizes the risk of a typo that breaks a route.
We are doing this to reduce cardinality. Indexes are created from the
combination of measurement and tags. This means every node session ends
up getting it's own indexes which blows out our cardinality and causes
causes InfluxDB to stop processing data. You can read more about this
issue here:

https://docs.influxdata.com/influxdb/cloud/write-data/best-practices/resolve-high-cardinalityg
The issue is that Node.Init() happens before the telemetry node id is
created for the first time. We simply move that up, and configure it on
the SDK itself which gets passed to the constructed node.
* feat(ironfish): Move metrics monitor inside telemetry

* feat(ironfish): Submit peer metrics in telemetry
…ron-fish#1038)

* feat(ironfish): Update telemetry flush interval from 5s to 60s

* Update to 5m

* Update METRICS_INTERVAL
…iron-fish#1033)

* fix(ironfish): Pass in metrics and remove peer network from telemetry

* s/peersCount/p2p_PeersCount
Remove test:slow
Add referencing bugs fixed in the PR description.
@AmberKiso
Copy link
Contributor Author

AmberKiso commented Feb 23, 2022

@NullSoldier Ran the command line, then pushed origin.

For my current PRs, they all started with me branching from master. For future PR, should I branch from upstream\staging?
(GIthub desktop shows that branch as 4 days old versus a 1 month old staging.)

@dguenther
Copy link
Member

Yep, I think basing on upstream/staging should be right. It'll depend what the name of git remote corresponding to the ironfish repository is when you run git remote -v, but that's more than likely upstream.

@dguenther dguenther merged commit 80bfd4c into iron-fish:staging Feb 23, 2022
@AmberKiso AmberKiso deleted the more-documentation-fixing branch February 24, 2022 01:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
6 participants