comments
Gitea Actions Demo / Explore-Gitea-Actions (push) Failing after 34s
Details
Gitea Actions Demo / Explore-Gitea-Actions (push) Failing after 34s
Details
This commit is contained in:
parent
073f6e61aa
commit
2790c9262b
|
@ -107,9 +107,7 @@ const evaluateMatrixPoolOutcome = async (postId) => {
|
|||
// TODO: If there's no batch worker, we should stake our availability
|
||||
// and then submit the batch immediately.
|
||||
await submitBatchPost(batchItems);
|
||||
}
|
||||
|
||||
if (batchWorker === await wallet.getAddress()) {
|
||||
} else if (batchWorker === await wallet.getAddress()) {
|
||||
// TODO: If we are the batch worker, we should wait an appropriate amout of time /
|
||||
// number of matrix pools before submitting a batch.
|
||||
}
|
||||
|
@ -212,6 +210,8 @@ const start = async () => {
|
|||
registerMatrixEventHandler(async (client, roomId, event) => {
|
||||
switch (event.type) {
|
||||
case 'io.dgov.pool.start': {
|
||||
// Note that matrix pools are identified by the postId to which they pertain.
|
||||
// This means that for a given post there can only be one matrix pool at a time.
|
||||
const { postId, sender, ...params } = event.content;
|
||||
// We can use LevelDB to store information about validation pools
|
||||
const eventId = event.event_id;
|
||||
|
|
Loading…
Reference in New Issue