Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / threefoldtech/rmb_go issues and pull requests

#51 - Fix tests

Issue - State: closed - Opened by MarioBassem about 2 years ago

#50 - Updates docs and adds mocks

Pull Request - State: closed - Opened by MarioBassem about 2 years ago

#49 - tcp connections leaks

Issue - State: closed - Opened by xmonader about 2 years ago
Labels: type_bug

#48 - update substrate client imports

Issue - State: closed - Opened by xmonader about 2 years ago
Labels: type_bug

#47 - sort out the repo

Issue - State: closed - Opened by xmonader about 2 years ago
Labels: priority_critical

#46 - updates substrate client package import

Pull Request - State: closed - Opened by MarioBassem about 2 years ago

#45 - use a single substrate connection

Pull Request - State: closed - Opened by MarioBassem over 2 years ago

#44 - Update docs

Issue - State: closed - Opened by Mahmoud-Emad over 2 years ago

#43 - a message could be lost when handled by RMB Under certain circumstances

Issue - State: closed - Opened by sameh-farouk almost 3 years ago

#42 - Rmb for mainnet gridproxy can randomly fail

Issue - State: closed - Opened by LeeSmet almost 3 years ago
Labels: priority_major, type_bug

#41 - handle network/server issues when forwarding a reply over http

Issue - State: closed - Opened by sameh-farouk almost 3 years ago
Labels: type_bug

#40 - Connection with substrate causes lost replies

Issue - State: closed - Opened by OmarElawady almost 3 years ago

#38 - handle retry when message have multiple destinations not working correctly.

Issue - State: closed - Opened by sameh-farouk almost 3 years ago
Labels: type_bug

#37 - Development twin2

Pull Request - State: closed - Opened by EdwardKerckhof almost 3 years ago

#36 - reorder epoch validaion to avoid failing valid messages

Pull Request - State: closed - Opened by OmarElawady almost 3 years ago

#35 - Validate epoch before fetching the public key

Issue - State: closed - Opened by OmarElawady almost 3 years ago - 1 comment

#34 - document rmb_client

Issue - State: closed - Opened by despiegk almost 3 years ago

#33 - port evertyhing useful from RMB_GO server parts to RMB_V

Issue - State: closed - Opened by despiegk almost 3 years ago

#32 - remove server components from rmb_go

Issue - State: closed - Opened by despiegk almost 3 years ago
Labels: type_feature

#31 - verify reply messages in the proxy flow

Pull Request - State: closed - Opened by OmarElawady about 3 years ago

#30 - verify reply

Pull Request - State: closed - Opened by OmarElawady about 3 years ago

#29 - sign the message

Pull Request - State: closed - Opened by OmarElawady about 3 years ago

#28 - Error responses from rmb proxy is not valid json

Issue - State: closed - Opened by OmarElawady about 3 years ago - 1 comment
Labels: type_bug

#27 - v0.1.7

Pull Request - State: closed - Opened by dmahmouali about 3 years ago

#26 - handle messages in parallel

Pull Request - State: closed - Opened by dmahmouali about 3 years ago

#25 - rmb handles messages sequentially

Issue - State: closed - Opened by OmarElawady about 3 years ago
Labels: priority_major, type_bug

#24 - v0.1.6

Pull Request - State: closed - Opened by dmahmouali about 3 years ago

#23 - expire keys after 30 mins to avoid redis clutters

Pull Request - State: closed - Opened by waleedhammam about 3 years ago

#22 - rotate / clean rmb redis-keys

Issue - State: closed - Opened by waleedhammam about 3 years ago

#21 - Update substrate default url

Pull Request - State: closed - Opened by dmahmouali about 3 years ago

#20 - Coulnd't deploy useing v0.1.4 binary

Issue - State: closed - Opened by RafyAmgadBenjamin about 3 years ago - 1 comment

#19 - Update README

Pull Request - State: closed - Opened by dmahmouali about 3 years ago

#18 - Update docs with binaries link and how to build the project

Issue - State: closed - Opened by RafyAmgadBenjamin about 3 years ago

#17 - Update the README file

Pull Request - State: closed - Opened by dmahmouali about 3 years ago

#16 - init systemd configuration

Issue - State: closed - Opened by dmahmouali about 3 years ago

#15 - should have --local flag to skip the whole substrate flow

Issue - State: closed - Opened by dmahmouali over 3 years ago

#14 - Isolate the HTTP flow

Pull Request - State: closed - Opened by dmahmouali over 3 years ago

#13 - Create isolated flow for handling the HTTP requests

Issue - State: closed - Opened by dmahmouali over 3 years ago

#12 - Isolate the HTTP flow

Pull Request - State: closed - Opened by dmahmouali over 3 years ago

#11 - Update the README file

Issue - State: closed - Opened by dmahmouali over 3 years ago

#10 - remove all "content" from logs (even debug messages)

Issue - State: closed - Opened by muhamadazmy over 3 years ago

#9 - use standalone substrate client

Pull Request - State: closed - Opened by muhamadazmy over 3 years ago

#8 - cache twin ids, don't look up the same id each time from substrate

Issue - State: closed - Opened by muhamadazmy over 3 years ago

#7 - Allow submit messages via HTTP

Pull Request - State: closed - Opened by dmahmouali over 3 years ago

#6 - The retrying is done over all the original message destinations, not on the failed one only

Issue - State: closed - Opened by dmahmouali over 3 years ago - 1 comment

#5 - "all retries done" is very generic, should return also the errors that happened in the process.

Issue - State: closed - Opened by OmarElawady over 3 years ago - 1 comment

#4 - Allow direct http communication with the rmb

Issue - State: closed - Opened by OmarElawady over 3 years ago

#3 - security: currently twin starts with 'twin-id' while in fact it should start with the 'mnemonics'

Issue - State: closed - Opened by muhamadazmy over 3 years ago

#2 - better backend abstraction, error handling

Pull Request - State: closed - Opened by OmarElawady over 3 years ago

#1 - Testing

Pull Request - State: closed - Opened by dmahmouali over 3 years ago