Selecting the gateway randomly from 2 known good ones. #355
+44
−21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…lem with the config file in this commit though.
|
Should close #352 |
jstuczyn
added a commit
that referenced
this pull request
Sep 28, 2020
* Feature/wasm update (#341) * Split text and binary client apis * Very initial attempt at new serialization * Defined ser+de for Recipient and ReplySURB * Response errors * builds with changes * Working WS API + moved to separate crate * updated python examples * Fixed parsing bug * Updated go examples * Updated rust examples * formatting * Removed unused imports * dependency updates * Further dependency changes * nymsphinx exposingn framing only if not in wasm32 * Cargo lock changes before develop merge * Pending work * Actually sending and receiving websocket from rust! * more WIP * Initial wasm client + establishing shared key with gateway! * Splitting and sending a message! * WIP * WIP * Initial wasm-ification of the gateway client * Passing reconstruction result to js callback! * Initial WASM cleaning pass * Dependency pruning * Moved processing loop to received_processor + at least ack unwrappingn * Post merge fix * Kinda updated react example * Old print statement removed * Removed yarn.lock * Fixed building issue for other clients * Fixed travis test command * Updated wasm publishing instructions * Increased default presence and metrics sending interval (#354) * Defaulting to mix layer with fewest node if no argument provided (#353) * Defaulting to mix layer with fewest node if no argument provided * cargo fmt * Selecting the gateway randomly from 2 known good ones. (#355) * Selecting the gateway randomly from 2 known good ones. There's a problem with the config file in this commit though. * Saving value of chosen gateway * Removed duplicate printing of gateway being used Co-authored-by: jstuczyn <jedrzej.stuczynski@gmail.com> * More detailed error response on authentication/registration failure (#356) * Updated changelog * Updated version numbers Co-authored-by: Dave Hrycyszyn <futurechimp@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There's a problem with the config file in this commit though - the written file comes out with a blank
gateway_id. I don't completely understand how the config file overrides work, but my guess is that something is usingmatchesinstead ofgateway_id