get_discussions_by_blog to filter resteems - #678
Merged
mvandeberg merged 1 commit intoDec 14, 2016
Merged
Conversation
Contributor
|
@jcalfee Are these changes to |
Contributor
|
@mvandeberg yes. The goal is to allow us to fetch either a pure blog or pure resteemed feed while maintaining backwards-compatibility. |
|
@mvandeberg I think it is a great idea to split up blogs and resteems this gives authors some freedom to re-steem a lot and still lets users easily find their personal material. I'm going to have to build this branch before I understand the changes though. |
Contributor
Author
|
Correct, this implementation maintains backwards compatibility. A get_state @user and get_discussions_by_blog functions as it used to. For 6 examples of various usage, see the related steemit post. |
mvandeberg
pushed a commit
that referenced
this pull request
Dec 19, 2016
… a more extensible approach and favors numeric comparison to string comparison #678
On1x
added a commit
to VIZ-Blockchain/viz-cpp-node
that referenced
this pull request
Aug 20, 2026
…#678) service_lazy_withdraw_queue() drained the whole FIFO withdraw queue on every call — up to 150M rows when free_balance was large — and it was called from six places, four of them inside evaluators, so one capital-return transaction could consume unbounded per-block work (one row minted per partial withdrawal for as little as 1 raw, no floor). - service_lazy_withdraw_queue(db, row_limit) returns how many rows it processed and stops after row_limit. - Per-transaction call-sites pass 1 (pay the FIFO head; the bulk is drained by the cron). - New cron section 9 drains the queue up to the shared per-block pm_settle_rows_per_block row budget whenever pending_withdrawals > 0, charging row_budget honestly. This is the liveness backstop: the queue keeps progressing even when no capital returns to free_balance. Test lazy_withdraw_queue_row_budget_spans_blocks: 250 one-raw rows against a 100-row budget span several blocks at <= budget/block, FIFO preserved, free >= 0, pending -> 0. The honest control (pre-fix unbounded drain) fails the per-block bound. No layout change -> no testnet redeploy. docs: settlement-work-bounds 4.8 (queue budget) + lazy-pool guide (the queue now progresses every block via the cron, not only on capital returns).
On1x
added a commit
to VIZ-Blockchain/viz-cpp-node
that referenced
this pull request
Aug 20, 2026
…/LP fixes) Bring the docs-only PR for master up to date with the pm-branch docs, which now carry the steemit#678/steemit#681 documentation: - settlement-work-bounds.md (new, en-only design note): per-block work bounds of PM settlement, GC, void refund, batch-queue and ban sweeps. - specification.md (en/ru/zh-CN): liquidity_fee_earned is a post-hoc counter written in settle_liquidity, not a subtraction in the fee-pool formula; early-exit LPs earn no commission; void markets earn zero bonus. - guides/active-lp.md (en/ru/zh-CN): early exit = principal only, void = zero income, pm_min_liquidity floor applies to top-ups. - guides/lazy-pool.md: FIFO withdraw queue is drained per block; the §9 cron section shares the row budget. No node code. Docs tree identical to pm. Docs build verified (26 PM pages).
On1x
added a commit
to VIZ-Blockchain/viz-cpp-node
that referenced
this pull request
Aug 20, 2026
* docs: bring prediction-market documentation to master (en/ru/zh-CN) * docs: sync docs-pm with current pm docs (settlement-work-bounds, spec/LP fixes) Bring the docs-only PR for master up to date with the pm-branch docs, which now carry the steemit#678/steemit#681 documentation: - settlement-work-bounds.md (new, en-only design note): per-block work bounds of PM settlement, GC, void refund, batch-queue and ban sweeps. - specification.md (en/ru/zh-CN): liquidity_fee_earned is a post-hoc counter written in settle_liquidity, not a subtraction in the fee-pool formula; early-exit LPs earn no commission; void markets earn zero bonus. - guides/active-lp.md (en/ru/zh-CN): early exit = principal only, void = zero income, pm_min_liquidity floor applies to top-ups. - guides/lazy-pool.md: FIFO withdraw queue is drained per block; the §9 cron section shares the row budget. No node code. Docs tree identical to pm. Docs build verified (26 PM pages). * docs(pm): sync settlement-work-bounds §4.11–4.12 (cron §6 idle fast-path, deferred-claim purge + phase-1/5 loud signals) * docs(pm): add Russian translations for early-exit-deferred-claim, parlay-spec, settlement-work-bounds * docs(pm): add Chinese (zh-CN) translations for early-exit-deferred-claim, parlay-spec, settlement-work-bounds
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For issue #581
Post: https://steemit.com/steemit/@bitcoiner/resteemed-tab-has-been-developed-with-steemd-backend-change