Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / bitrich-info/xchange-stream issues and pull requests
#510 - XChange 4.4.1 has been released
Issue -
State: closed - Opened by pchertalev almost 5 years ago
- 16 comments
#510 - XChange 4.4.1 has been released
Issue -
State: closed - Opened by pchertalev almost 5 years ago
- 16 comments
#509 - handle duplicate subscriptions warning
Pull Request -
State: closed - Opened by mdvx almost 5 years ago
- 1 comment
#509 - handle duplicate subscriptions warning
Pull Request -
State: closed - Opened by mdvx almost 5 years ago
- 1 comment
#509 - handle duplicate subscriptions warning
Pull Request -
State: closed - Opened by mdvx almost 5 years ago
- 1 comment
#502 - [Kraken] KrakenStreamingService possible bug on switch loop
Issue -
State: open - Opened by makarid almost 5 years ago
- 25 comments
#502 - [Kraken] KrakenStreamingService possible bug on switch loop
Issue -
State: open - Opened by makarid almost 5 years ago
- 25 comments
#502 - [Kraken] KrakenStreamingService possible bug on switch loop
Issue -
State: open - Opened by makarid almost 5 years ago
- 25 comments
#502 - [Kraken] KrakenStreamingService possible bug on switch loop
Issue -
State: open - Opened by makarid almost 5 years ago
- 25 comments
#502 - [Kraken] KrakenStreamingService possible bug on switch loop
Issue -
State: open - Opened by makarid almost 5 years ago
- 25 comments
#502 - [Kraken] KrakenStreamingService possible bug on switch loop
Issue -
State: open - Opened by makarid almost 5 years ago
- 25 comments
#487 - Change update rate to 100ms for binance market data service
Pull Request -
State: closed - Opened by lepus almost 5 years ago
- 2 comments
Labels: awaiting_fixes
#487 - Change update rate to 100ms for binance market data service
Pull Request -
State: closed - Opened by lepus almost 5 years ago
- 2 comments
Labels: awaiting_fixes
#487 - Change update rate to 100ms for binance market data service
Pull Request -
State: closed - Opened by lepus almost 5 years ago
- 2 comments
Labels: awaiting_fixes
#487 - Change update rate to 100ms for binance market data service
Pull Request -
State: closed - Opened by lepus almost 5 years ago
- 2 comments
Labels: awaiting_fixes
#487 - Change update rate to 100ms for binance market data service
Pull Request -
State: closed - Opened by lepus almost 5 years ago
- 2 comments
Labels: awaiting_fixes
#487 - Change update rate to 100ms for binance market data service
Pull Request -
State: closed - Opened by lepus almost 5 years ago
- 2 comments
Labels: awaiting_fixes
#487 - Change update rate to 100ms for binance market data service
Pull Request -
State: closed - Opened by lepus almost 5 years ago
- 2 comments
Labels: awaiting_fixes
#487 - Change update rate to 100ms for binance market data service
Pull Request -
State: closed - Opened by lepus almost 5 years ago
- 2 comments
Labels: awaiting_fixes
#487 - Change update rate to 100ms for binance market data service
Pull Request -
State: closed - Opened by lepus almost 5 years ago
- 2 comments
Labels: awaiting_fixes
#487 - Change update rate to 100ms for binance market data service
Pull Request -
State: closed - Opened by lepus almost 5 years ago
- 2 comments
Labels: awaiting_fixes
#485 - Kraken websocket not working
Issue -
State: open - Opened by atiqkhan26 almost 5 years ago
- 6 comments
#485 - Kraken websocket not working
Issue -
State: open - Opened by atiqkhan26 almost 5 years ago
- 6 comments
#485 - Kraken websocket not working
Issue -
State: open - Opened by atiqkhan26 almost 5 years ago
- 6 comments
#485 - Kraken websocket not working
Issue -
State: open - Opened by atiqkhan26 almost 5 years ago
- 6 comments
#485 - Kraken websocket not working
Issue -
State: open - Opened by atiqkhan26 almost 5 years ago
- 6 comments
#485 - Kraken websocket not working
Issue -
State: open - Opened by atiqkhan26 almost 5 years ago
- 6 comments
#485 - Kraken websocket not working
Issue -
State: open - Opened by atiqkhan26 almost 5 years ago
- 6 comments
#485 - Kraken websocket not working
Issue -
State: open - Opened by atiqkhan26 almost 5 years ago
- 6 comments
#485 - Kraken websocket not working
Issue -
State: open - Opened by atiqkhan26 almost 5 years ago
- 6 comments
#485 - Kraken websocket not working
Issue -
State: open - Opened by atiqkhan26 almost 5 years ago
- 6 comments
#485 - Kraken websocket not working
Issue -
State: open - Opened by atiqkhan26 almost 5 years ago
- 6 comments
#477 - Log the channel when connecting / idle / failed
Pull Request -
State: closed - Opened by mdvx almost 5 years ago
#477 - Log the channel when connecting / idle / failed
Pull Request -
State: closed - Opened by mdvx almost 5 years ago
#477 - Log the channel when connecting / idle / failed
Pull Request -
State: closed - Opened by mdvx almost 5 years ago
#477 - Log the channel when connecting / idle / failed
Pull Request -
State: closed - Opened by mdvx almost 5 years ago
#477 - Log the channel when connecting / idle / failed
Pull Request -
State: closed - Opened by mdvx almost 5 years ago
#477 - Log the channel when connecting / idle / failed
Pull Request -
State: closed - Opened by mdvx almost 5 years ago
#477 - Log the channel when connecting / idle / failed
Pull Request -
State: closed - Opened by mdvx almost 5 years ago
#469 - Bump pubnub-gson from 4.25.0 to 4.29.2
Pull Request -
State: closed - Opened by dependabot-preview[bot] almost 5 years ago
- 3 comments
Labels: dependencies
#469 - Bump pubnub-gson from 4.25.0 to 4.29.2
Pull Request -
State: closed - Opened by dependabot-preview[bot] almost 5 years ago
- 3 comments
Labels: dependencies
#469 - Bump pubnub-gson from 4.25.0 to 4.29.2
Pull Request -
State: closed - Opened by dependabot-preview[bot] almost 5 years ago
- 3 comments
Labels: dependencies
#469 - Bump pubnub-gson from 4.25.0 to 4.29.2
Pull Request -
State: closed - Opened by dependabot-preview[bot] almost 5 years ago
- 3 comments
Labels: dependencies
#469 - Bump pubnub-gson from 4.25.0 to 4.29.2
Pull Request -
State: closed - Opened by dependabot-preview[bot] almost 5 years ago
- 3 comments
Labels: dependencies
#469 - Bump pubnub-gson from 4.25.0 to 4.29.2
Pull Request -
State: closed - Opened by dependabot-preview[bot] almost 5 years ago
- 3 comments
Labels: dependencies
#467 - Rename projects to avoid clashing with XChange
Pull Request -
State: closed - Opened by makarid almost 5 years ago
- 11 comments
Labels: on hold
#467 - Rename projects to avoid clashing with XChange
Pull Request -
State: closed - Opened by makarid almost 5 years ago
- 11 comments
Labels: on hold
#467 - Rename projects to avoid clashing with XChange
Pull Request -
State: closed - Opened by makarid almost 5 years ago
- 11 comments
Labels: on hold
#467 - Rename projects to avoid clashing with XChange
Pull Request -
State: closed - Opened by makarid almost 5 years ago
- 11 comments
Labels: on hold
#467 - Rename projects to avoid clashing with XChange
Pull Request -
State: closed - Opened by makarid almost 5 years ago
- 11 comments
Labels: on hold
#467 - Rename projects to avoid clashing with XChange
Pull Request -
State: closed - Opened by makarid almost 5 years ago
- 11 comments
Labels: on hold
#467 - Rename projects to avoid clashing with XChange
Pull Request -
State: closed - Opened by makarid almost 5 years ago
- 11 comments
Labels: on hold
#464 - All modules need renaming ahead of XChange merge
Issue -
State: closed - Opened by badgerwithagun almost 5 years ago
- 2 comments
Labels: help wanted, refactoring, required-for-xchange-merge
#464 - All modules need renaming ahead of XChange merge
Issue -
State: closed - Opened by badgerwithagun almost 5 years ago
- 2 comments
Labels: help wanted, refactoring, required-for-xchange-merge
#464 - All modules need renaming ahead of XChange merge
Issue -
State: closed - Opened by badgerwithagun almost 5 years ago
- 2 comments
Labels: help wanted, refactoring, required-for-xchange-merge
#464 - All modules need renaming ahead of XChange merge
Issue -
State: closed - Opened by badgerwithagun almost 5 years ago
- 2 comments
Labels: help wanted, refactoring, required-for-xchange-merge
#464 - All modules need renaming ahead of XChange merge
Issue -
State: closed - Opened by badgerwithagun almost 5 years ago
- 2 comments
Labels: help wanted, refactoring, required-for-xchange-merge
#464 - All modules need renaming ahead of XChange merge
Issue -
State: closed - Opened by badgerwithagun almost 5 years ago
- 2 comments
Labels: help wanted, refactoring, required-for-xchange-merge
#462 - Add coveo-fmt plugin
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 1 comment
Labels: on hold
#462 - Add coveo-fmt plugin
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 1 comment
Labels: on hold
#462 - Add coveo-fmt plugin
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 1 comment
Labels: on hold
#462 - Add coveo-fmt plugin
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 1 comment
Labels: on hold
#462 - Add coveo-fmt plugin
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 1 comment
Labels: on hold
#462 - Add coveo-fmt plugin
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 1 comment
Labels: on hold
#462 - Add coveo-fmt plugin
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 1 comment
Labels: on hold
#462 - Add coveo-fmt plugin
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 1 comment
Labels: on hold
#461 - [BitMex] Bug Fix For Parsing Incoming Bitmex Messages
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 4 comments
#461 - [BitMex] Bug Fix For Parsing Incoming Bitmex Messages
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 4 comments
#461 - [BitMex] Bug Fix For Parsing Incoming Bitmex Messages
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 4 comments
#461 - [BitMex] Bug Fix For Parsing Incoming Bitmex Messages
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 4 comments
#461 - [BitMex] Bug Fix For Parsing Incoming Bitmex Messages
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 4 comments
#461 - [BitMex] Bug Fix For Parsing Incoming Bitmex Messages
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 4 comments
#461 - [BitMex] Bug Fix For Parsing Incoming Bitmex Messages
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 4 comments
#461 - [BitMex] Bug Fix For Parsing Incoming Bitmex Messages
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 4 comments
#461 - [BitMex] Bug Fix For Parsing Incoming Bitmex Messages
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 4 comments
#461 - [BitMex] Bug Fix For Parsing Incoming Bitmex Messages
Pull Request -
State: closed - Opened by badgerwithagun almost 5 years ago
- 4 comments
#460 - Add connection idle to public API
Pull Request -
State: closed - Opened by davidjirovec almost 5 years ago
#460 - Add connection idle to public API
Pull Request -
State: closed - Opened by davidjirovec almost 5 years ago
#460 - Add connection idle to public API
Pull Request -
State: closed - Opened by davidjirovec almost 5 years ago
#460 - Add connection idle to public API
Pull Request -
State: closed - Opened by davidjirovec almost 5 years ago
#460 - Add connection idle to public API
Pull Request -
State: closed - Opened by davidjirovec almost 5 years ago
#448 - [kraken] Exchange orderbook timestamp parse incorrect!
Issue -
State: open - Opened by sudo168 about 5 years ago
- 5 comments
Labels: bug, required-for-xchange-merge
#448 - [kraken] Exchange orderbook timestamp parse incorrect!
Issue -
State: open - Opened by sudo168 about 5 years ago
- 5 comments
Labels: bug, required-for-xchange-merge
#448 - [kraken] Exchange orderbook timestamp parse incorrect!
Issue -
State: open - Opened by sudo168 about 5 years ago
- 5 comments
Labels: bug, required-for-xchange-merge
#448 - [kraken] Exchange orderbook timestamp parse incorrect!
Issue -
State: open - Opened by sudo168 about 5 years ago
- 5 comments
Labels: bug, required-for-xchange-merge
#448 - [kraken] Exchange orderbook timestamp parse incorrect!
Issue -
State: open - Opened by sudo168 about 5 years ago
- 5 comments
Labels: bug, required-for-xchange-merge
#446 - [bitstamp] API v2 not getting trades
Issue -
State: open - Opened by jurepetrovic about 5 years ago
- 16 comments
Labels: bug, required-for-xchange-merge
#446 - [bitstamp] API v2 not getting trades
Issue -
State: open - Opened by jurepetrovic about 5 years ago
- 16 comments
Labels: bug, required-for-xchange-merge
#446 - [bitstamp] API v2 not getting trades
Issue -
State: open - Opened by jurepetrovic about 5 years ago
- 16 comments
Labels: bug, required-for-xchange-merge
#446 - [bitstamp] API v2 not getting trades
Issue -
State: open - Opened by jurepetrovic about 5 years ago
- 16 comments
Labels: bug, required-for-xchange-merge
#446 - [bitstamp] API v2 not getting trades
Issue -
State: open - Opened by jurepetrovic about 5 years ago
- 16 comments
Labels: bug, required-for-xchange-merge
#446 - [bitstamp] API v2 not getting trades
Issue -
State: open - Opened by jurepetrovic about 5 years ago
- 16 comments
Labels: bug, required-for-xchange-merge
#446 - [bitstamp] API v2 not getting trades
Issue -
State: open - Opened by jurepetrovic about 5 years ago
- 16 comments
Labels: bug, required-for-xchange-merge
#446 - [bitstamp] API v2 not getting trades
Issue -
State: open - Opened by jurepetrovic about 5 years ago
- 16 comments
Labels: bug, required-for-xchange-merge
#441 - Apply Google style guide
Issue -
State: closed - Opened by jkolobok about 5 years ago
- 1 comment
Labels: refactoring, required-for-xchange-merge
#441 - Apply Google style guide
Issue -
State: closed - Opened by jkolobok about 5 years ago
- 1 comment
Labels: refactoring, required-for-xchange-merge
#441 - Apply Google style guide
Issue -
State: closed - Opened by jkolobok about 5 years ago
- 1 comment
Labels: refactoring, required-for-xchange-merge
#441 - Apply Google style guide
Issue -
State: closed - Opened by jkolobok about 5 years ago
- 1 comment
Labels: refactoring, required-for-xchange-merge
#441 - Apply Google style guide
Issue -
State: closed - Opened by jkolobok about 5 years ago
- 1 comment
Labels: refactoring, required-for-xchange-merge
#441 - Apply Google style guide
Issue -
State: closed - Opened by jkolobok about 5 years ago
- 1 comment
Labels: refactoring, required-for-xchange-merge