Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Preparation for subscribing with multiple accounts and test that confirms current issues #1516
Preparation for subscribing with multiple accounts and test that confirms current issues #1516
Changes from 8 commits
ec63a73
c47655c
385b634
8e4aeee
8b9c5c9
167c1e2
13ca18b
55032a8
35378ec
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
The commented out code should be removed. It's generally not a good practice to leave large blocks of commented out code in the codebase. If this code is not being used, it should be removed. If it's needed for future reference, it should be documented elsewhere (e.g., in a design document or a separate branch).
Check failure on line 26 in integration/obscurogateway/gateway_user.go
GitHub Actions / lint
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.
The
NewUser
function creates an HTTP and a WebSocket client by dialing the server addresses. However, there is no error handling or retry logic in case the dialing fails. This could lead to a situation where the function returns aGatewayUser
with a nil HTTP or WebSocket client, which could cause runtime errors later on. Consider adding retry logic and/or returning an error if the dialing fails.Committable suggestion (Beta)
Check failure on line 48 in integration/obscurogateway/gateway_user.go
GitHub Actions / lint
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.
The
RegisterAccounts
function registers each wallet in theWallets
slice with the Obscuro Gateway. However, it does not handle any errors that might occur during the registration process. Consider adding error handling to this function.Committable suggestion (Beta)
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.
As per the previous comment, the
PrintUserAccountsBalances
function is directly printing the balance of each account to the console. This might not be desirable in a production environment. Consider returning the balances to the caller instead, so they can decide how to handle it.Committable suggestion (Beta)