Ws server refactor #13
Merged
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
added 3 commits
June 22, 2020 16:20
… the worker main event loop to prevent race conditions with on state/chain_relay access.
|
seems not to work. tried on devsgx03 |
|
did you update the client as well? |
|
must've been the old client. works now. |
brenzi
pushed a commit
that referenced
this pull request
Sep 8, 2020
* changed ws_server completely. Requests from client are now handled in the worker main event loop to prevent race conditions with on state/chain_relay access. * [ws_server] remove unwrap and send instead "invalid_client_request" to client
brenzi
pushed a commit
that referenced
this pull request
Sep 8, 2020
* changed ws_server completely. Requests from client are now handled in the worker main event loop to prevent race conditions with on state/chain_relay access. * [ws_server] remove unwrap and send instead "invalid_client_request" to client
brenzi
added a commit
that referenced
this pull request
Nov 3, 2020
* [enclave] ! fix: init-shard if it does not exist * back up chain relay db before update in case of file corruption * clean up chain relay sync logging * Ws server refactor (#13) * changed ws_server completely. Requests from client are now handled in the worker main event loop to prevent race conditions with on state/chain_relay access. * [ws_server] remove unwrap and send instead "invalid_client_request" to client * updating block number in stf state * [enclave/chain_relay] store only hashes of the headers instead of the headers themselves * enclave: patch log and env_logger to mesalock * worker should panic if it can't write to shard * add public getters for unpermissioned statistics (#16) * don't request key provisioning form other worker. assume its there or generate new (dangerous!) * bump version to 0.6.11 like encointer reference release Co-authored-by: clangenb <37865735+clangenb@users.noreply.github.com> Co-authored-by: Marcel Frei <marcel.frei@electronix.ch> Co-authored-by: Christian Langenbacher <christian.langenbacher91@gmail.com>
brenzi
added a commit
that referenced
this pull request
Nov 3, 2020
* automatic-shard-joining-and-per-shard-updates-on-block (integritee-network#160) * [enclave] update_map contains options. This is needed if a storage value needs to be deleted in the STF [enclave, stf] perform state updates per shard, auto join new shards * [worker] only feed 100 blocks at a time into the chain relay. Improved logging while syncing to keep track of sync status * [WorkerApi] Remove default protocol ws. * update ipfs version (integritee-network#165) Co-authored-by: bwty <whalelephant@users.noreply.github.com> * Implement Ipfs read and write with verification in enclave this implements gitcoin bounty integritee-network#70 Co-authored-by: bwty <whalelephant@users.noreply.github.com> * Encointer contributions upstreaming (integritee-network#174) * [enclave] ! fix: init-shard if it does not exist * back up chain relay db before update in case of file corruption * clean up chain relay sync logging * Ws server refactor (#13) * changed ws_server completely. Requests from client are now handled in the worker main event loop to prevent race conditions with on state/chain_relay access. * [ws_server] remove unwrap and send instead "invalid_client_request" to client * updating block number in stf state * [enclave/chain_relay] store only hashes of the headers instead of the headers themselves * enclave: patch log and env_logger to mesalock * worker should panic if it can't write to shard * add public getters for unpermissioned statistics (#16) * don't request key provisioning form other worker. assume its there or generate new (dangerous!) * bump version to 0.6.11 like encointer reference release Co-authored-by: clangenb <37865735+clangenb@users.noreply.github.com> Co-authored-by: Marcel Frei <marcel.frei@electronix.ch> Co-authored-by: Christian Langenbacher <christian.langenbacher91@gmail.com> * fix integritee-network#176 and update some dependiencies * upgrade to upstream 2.0.0-rc5 fix .dispatch filtering introduced in paritytech/substrate#6318 depend on tag version for sgx-runtime * Upgrade upstream 2.0.0 (integritee-network#182) * enclave builds * worker and client builds * fix metadata module index * successfully tested shielding-unshielding example * fix merge. builds and demo works Co-authored-by: clangenb <37865735+clangenb@users.noreply.github.com> Co-authored-by: bwty <18553484+whalelephant@users.noreply.github.com> Co-authored-by: bwty <whalelephant@users.noreply.github.com> Co-authored-by: bwty <email-me@belsy.space> Co-authored-by: Marcel Frei <marcel.frei@electronix.ch> Co-authored-by: Christian Langenbacher <christian.langenbacher91@gmail.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.
ClientRequestenum