-
Notifications
You must be signed in to change notification settings - Fork 25
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
feat: add gems #168
feat: add gems #168
Conversation
Description --- Adds authentication connection with the airdrop site. Generates a temporary uuid (which would expire after 5 minutes) After triggering the log in button it checks for tokens using this generated UUID This flow avoids the use of deeplinking Motivation and Context --- We need a way to connect miners to their airdrop accounts in order to get rewards How Has This Been Tested? --- Manually, this is a partial integration at the moment logging the tokens What process can a PR reviewer use to test or verify this change? --- Check in the console if their auth tokens are being displayed after sign in <!-- Checklist --> <!-- 1. Is the title of your PR in the form that would make nice release notes? The title, excluding the conventional commit tag, will be included exactly as is in the CHANGELOG, so please think about it carefully. --> Breaking Changes --- - [x] None - [ ] Requires data directory on base node to be deleted - [ ] Requires hard fork - [ ] Other - Please specify <!-- Does this include a breaking change? If so, include this line as a footer --> <!-- BREAKING CHANGE: Description what the user should do, e.g. delete a database, resync the chain --> --------- Co-authored-by: Erika <[email protected]> Co-authored-by: stringhandler <[email protected]> Co-authored-by: Marcin Papież <[email protected]> Co-authored-by: stringhandler <[email protected]>
Description Update gems branch --- Motivation and Context --- How Has This Been Tested? --- What process can a PR reviewer use to test or verify this change? --- <!-- Checklist --> <!-- 1. Is the title of your PR in the form that would make nice release notes? The title, excluding the conventional commit tag, will be included exactly as is in the CHANGELOG, so please think about it carefully. --> Breaking Changes --- - [x] None - [ ] Requires data directory on base node to be deleted - [ ] Requires hard fork - [ ] Other - Please specify <!-- Does this include a breaking change? If so, include this line as a footer --> <!-- BREAKING CHANGE: Description what the user should do, e.g. delete a database, resync the chain --> --------- Co-authored-by: Erika <[email protected]> Co-authored-by: stringhandler <[email protected]>
## Description - Adds heartbeat signal for metrics data. Further details are described in issue: #158 --- Motivation and Context --- How Has This Been Tested? --- What process can a PR reviewer use to test or verify this change? --- <!-- Checklist --> <!-- 1. Is the title of your PR in the form that would make nice release notes? The title, excluding the conventional commit tag, will be included exactly as is in the CHANGELOG, so please think about it carefully. --> Breaking Changes --- - [x] None - [ ] Requires data directory on base node to be deleted - [ ] Requires hard fork - [ ] Other - Please specify <!-- Does this include a breaking change? If so, include this line as a footer --> <!-- BREAKING CHANGE: Description what the user should do, e.g. delete a database, resync the chain --> --------- Co-authored-by: Erika <[email protected]> Co-authored-by: stringhandler <[email protected]> Co-authored-by: Misieq01 <[email protected]>
Description --- Motivation and Context --- How Has This Been Tested? --- What process can a PR reviewer use to test or verify this change? --- <!-- Checklist --> <!-- 1. Is the title of your PR in the form that would make nice release notes? The title, excluding the conventional commit tag, will be included exactly as is in the CHANGELOG, so please think about it carefully. --> Breaking Changes --- - [x] None - [ ] Requires data directory on base node to be deleted - [ ] Requires hard fork - [ ] Other - Please specify <!-- Does this include a breaking change? If so, include this line as a footer --> <!-- BREAKING CHANGE: Description what the user should do, e.g. delete a database, resync the chain -->
Description --- Integration for token set and refresh Motivation and Context --- How Has This Been Tested? --- What process can a PR reviewer use to test or verify this change? --- <!-- Checklist --> <!-- 1. Is the title of your PR in the form that would make nice release notes? The title, excluding the conventional commit tag, will be included exactly as is in the CHANGELOG, so please think about it carefully. --> Breaking Changes --- - [x] None - [ ] Requires data directory on base node to be deleted - [ ] Requires hard fork - [ ] Other - Please specify <!-- Does this include a breaking change? If so, include this line as a footer --> <!-- BREAKING CHANGE: Description what the user should do, e.g. delete a database, resync the chain -->
} | ||
|
||
#[derive(Debug, Deserialize, Serialize)] | ||
pub enum TelemetryNetwork { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Why not use the full name and just use serde(lowercase)
?
} | ||
}); | ||
|
||
if telemetry_collection_enabled { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: perhaps do this before checking the JWT above, otherwise, every loop it will decode the jwt
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch
src-tauri/src/telemetry_manager.rs
Outdated
} | ||
|
||
async fn send_telemetry_data(data: TelemetryData, airdrop_access_token: Option<String>) { | ||
debug!("Telemetry data being sent: {:?}", data); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logs must have a LOG_TARGET so that they go into the correct file
abfe85a
to
d35bf20
Compare
- Reverts button config changes to match the design system
Removes duplicate code from the Settings component after merge synchronization with the main branch.
Working feature branch for adding gems