LBRYCommunity/lbrycrd

Fork

You've already forked lbrycrd

Code Issues 29 Pull requests 1 Projects Releases 32 Packages Wiki Activity

block creation rate on testnet is broken; fix it #252

New issue

Closed

opened 2019-02-06 20:27:44 +01:00 by BrannonKing · 0 comments

BrannonKing commented

2019-02-06 20:27:44 +01:00

(Migrated from github.com)

Copy link

We currently have 900k+ blocks on testnet. This isn't right. There is some logic there to allow a rapid decline in required work effort (as testers come and go in a group). There is likely some bug with this mechanism.

No Branch/Tag specified

Branches Tags

master

mergemine_hf

block_info_fix

block_info_fix_try2

v19_master

hash_bit_seq

v17_master

finance

static_link

small_takeover_experiment

dont_force_segwit

add_signature_test

cache_nth_trie_children

v12_master

experimental_use_basho_leveldb

experimental_separate_dbs

experimental_use_bdb_for_claimtrie

experimental_prefix_node_pool

experimental_sqlite_kvps

move_to_gitlab_ci

get_activations_in_block

add_claim_import_scripts

v0.17.3.3

v0.19.1.3

v0.17.4.6

v0.19.1.2

v0.17.4.5

v0.19.1.1

v0.17.4.4

v0.17.4.3

v0.17.4.2

v0.17.4.1

v0.17.3.2

v0.17.3.1

v0.17.3.0rc1

v0.17.2.1

v0.17.2.0

v0.17.1.0

v0.12.4.1

v0.12.4.0

v0.12.3.1

v0.12.3.0

v0.12.2.3

v0.12.2.2

v0.12.2.1

v0.12.2.0

v0.12.1.2

v0.12.1.1

v0.12.1.0

v0.12.0.6

v0.12.0.5

getclaimbyid_1

v0.12.0.4

v0.12.0.3

v0.12.0.2

v0.3.16

v0.3.15

0.13.0

test-win-release

v0.12.99

v0.3-osx

v0.2-alpha

v0.1-alpha-os-x

v0.1-alpha

Labels

Clear labels

Work is part of a proposal

consider soon

Discuss this issue at the next planning meeting, then remove this label

Epic

good first issue

hacktoberfest

Welcome to Hacktoberfest

No knowledge of the existing code required

level: 2

Some knowledge of the existing code is recommended

level: 3

Significant knowledge of the existing code is recommended

level: 4

Intimate knowledge of the existing code is recommended

needs: exploration

Solution unclear, needs research

needs: grooming

Issue needs to be groomed before work can start

needs: priority

Priority level needs to be defined

needs: repro

Issue needs step-by-step instructions on how to reproduce in latest code

needs: tech design

Needs technical design signoff before implementation can begin

on hold

Temporarily paused

priority: blocker

Issue is blocking release, do ASAP

priority: high

Work needs to be moved into sprint ASAP

priority: low

Work should be done but can stay in the backlog for now

priority: medium

Work needs to be done within 2-3 sprints

Existing functionality is wrong or broken

type: discussion

A conversation. No specific changes requested

type: improvement

Existing (or partially existing) functionality needs to be changed

type: new feature

New functionality that does not exist yet

type: refactor

Minimal user-visible changes, but significant internal work

type: task

Either work that's not related to the code, or a small chore that does not fit into other categories

type: testing

Solution needs additional user testing

unplanned

Work that was not planned into the spirnt, took priority over planned work

work in progress

The proposed solution is still incomplete.

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbrycrd#252

Reference in a new issue

Repository

LBRYCommunity/lbrycrd

Title

Body

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?