Tree: ba8d74e914

bdk-0.11

bip39

burn-down-handle

chore/actor-names-in-logs

chore/bump-bdk-0.15

chore/bump-maia

chore/changelog-entries

chore/leaner-release-process

chore/remove-next-dependency

chore/sql-format

chore/use-esplora-backend

compile-for-aarch64

contact-taker-before-changing-cfd-state

debug-collab-settlement

debug-statements

dependabot/cargo/anyhow-1.0.52

dependabot/cargo/clap-3.0.0-rc.8

dependabot/cargo/reqwest-0.11.8

dependabot/github_actions/docker/login-action-1.12.0

dependabot/npm_and_yarn/taker-frontend/types/node-17.0.4

dependabot/npm_and_yarn/taker-frontend/types/react-17.0.38

dependabot/npm_and_yarn/taker-frontend/vite-2.7.6

failing-clippy

feature/actor-custom-derive

feature/concurrent-roll-over

feature/delete-wallet-cache-on-failure

feature/force-stop-button

feature/integration-tests

feature/reconnect-button

feature/rollover-event-sourcing

feature/supervised-connection

fix-bad-api-calls

fix-olivia-event-id

fix/incorrect-tracing-use

fix/sql-oddness

frontend-backend

heartbeat-event-source

hotfix/0.1.1

hotfix/0.3.1

initial-taker-ui

integrate-protocol-maker-side

maker-taker-cfd-setup-messaging

master

new-http-api

no-buy-button-while-setting-up-cfd

no-contract-setup-message

pAndLAndPayout

patch-1

patch-2

reconnect-to-maker

refactor/no-log-handler

release/0.3.1

release/0.3.2

remove-long-heartbeat-interval-in-debug-mode

resilient-broadcast

rollover-test

rollover-test-2

shutdown-taker-if-no-maker-present

staging

state-machine

temporary-fast-timelocks

test-force-close-without-fake-clock

testing

ui-rampup

update-blockstream-electrum-server-url

upload-correct-windows-binary

verify-transactions

0.1.0

0.1.1

0.1.2

0.2.0

0.3.0

0.3.1

0.3.2

preview

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'ba8d74e914'

${ noResults }

Commit Graph

2 Commits (ba8d74e914d88e1e087fefeef25739bdf0bbc7e5)

Author	SHA1	Message	Date
Philipp Hoenisch	0519b29951	Ensure we always know about Order::Term*events Fetching new events all over the place is cumbersome and it is likely that we will forget about doing so (e.g. atm we forgot doing this when receiving a roll-over request at the maker). Hence, we now fetch on a regular interval for a fixed timespan: When starting up we fetch oracle events for the next 24h. Afterwards we check every 5 minutes again if there is a new event to check. This should ensure that we always know about needed events.	3 years ago
Daniel Karzel	1b7239c944	Simple actor test showcasing how to write actor tests Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>	3 years ago