Ecosyste.ms: Issues

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

GitHub / arkency/http_event_store issues and pull requests

#27 - Add a note about event_store_client for 5.x.x.x version support

Pull Request - State: closed - Opened by swilgosz over 4 years ago - 1 comment

#26 - Does not support EventStore 4

Issue - State: open - Opened by BookOfGreg about 7 years ago

#25 - Exceptions are swallowed and `nil` is returned

Issue - State: open - Opened by paneq about 7 years ago

#24 - Reading $all stream is not possible with read_all_events_forward

Issue - State: open - Opened by paneq about 7 years ago - 1 comment

#23 - Possible bug in reading events direction

Issue - State: open - Opened by paneq about 7 years ago - 2 comments

#22 - Meta data

Pull Request - State: open - Opened by hallgren over 7 years ago - 1 comment

#21 - return events that don´t include any data

Pull Request - State: open - Opened by hallgren over 7 years ago - 3 comments

#20 - Save events with no event data

Pull Request - State: closed - Opened by hallgren over 7 years ago

#19 - some minor improvements

Pull Request - State: closed - Opened by mindreframer almost 8 years ago

#18 - Bilus/fix/append events to stream

Pull Request - State: closed - Opened by bilus about 8 years ago - 1 comment

#17 - Read projections, improve retries, surface more information

Pull Request - State: closed - Opened by litch over 8 years ago - 1 comment

#16 - Gem rename

Pull Request - State: closed - Opened by mpraglowski over 8 years ago

#15 - documenting creating multiple events

Pull Request - State: closed - Opened by hallgren over 8 years ago

#14 - Event Store version 3

Pull Request - State: closed - Opened by hallgren over 8 years ago - 1 comment

#12 - Add more than one event to stream in one request

Pull Request - State: closed - Opened by hallgren over 8 years ago

#12 - Add more than one event to stream in one request

Pull Request - State: closed - Opened by hallgren over 8 years ago

#11 - How to subscribe to stream ?

Issue - State: closed - Opened by revskill10 almost 9 years ago - 2 comments

#11 - How to subscribe to stream ?

Issue - State: closed - Opened by revskill10 almost 9 years ago - 2 comments

#10 - Add a Gitter chat badge to README.md

Pull Request - State: closed - Opened by gitter-badger about 9 years ago

#10 - Add a Gitter chat badge to README.md

Pull Request - State: closed - Opened by gitter-badger about 9 years ago

#9 - Created LICENSE

Pull Request - State: closed - Opened by wlk about 9 years ago - 4 comments

#9 - Created LICENSE

Pull Request - State: closed - Opened by wlk about 9 years ago - 4 comments

#8 - The created_time of an event is surfaced by the HTTP client

Pull Request - State: closed - Opened by litch over 9 years ago

#8 - The created_time of an event is surfaced by the HTTP client

Pull Request - State: closed - Opened by litch over 9 years ago

#7 - Read all stream events is not recursive so can read arbitrarily long streams

Pull Request - State: closed - Opened by litch over 9 years ago

#7 - Read all stream events is not recursive so can read arbitrarily long streams

Pull Request - State: closed - Opened by litch over 9 years ago

#6 - read_all_events_forward on a long stream blows up

Issue - State: closed - Opened by litch over 9 years ago

#6 - read_all_events_forward on a long stream blows up

Issue - State: closed - Opened by litch over 9 years ago

#5 - Tolerate reading stream events forward if they encounter deleted events

Pull Request - State: closed - Opened by litch over 9 years ago

#5 - Tolerate reading stream events forward if they encounter deleted events

Pull Request - State: closed - Opened by litch over 9 years ago

#4 - Merge pull request #1 from obsidian-btc/stream-positions

Pull Request - State: closed - Opened by litch over 9 years ago - 1 comment

#4 - Merge pull request #1 from obsidian-btc/stream-positions

Pull Request - State: closed - Opened by litch over 9 years ago - 1 comment

#3 - Status codes from GES do not always indicate what they are interpreted as

Issue - State: open - Opened by litch over 9 years ago - 1 comment

#3 - Status codes from GES do not always indicate what they are interpreted as

Issue - State: open - Opened by litch over 9 years ago - 1 comment

#2 - Stream positions

Pull Request - State: closed - Opened by litch over 9 years ago - 1 comment

#2 - Stream positions

Pull Request - State: closed - Opened by litch over 9 years ago - 1 comment

#1 - Stream name

Pull Request - State: closed - Opened by litch over 9 years ago

#1 - Stream name

Pull Request - State: closed - Opened by litch over 9 years ago