H
Workflow 420-shared-hivemind-provider-s-pg-saa8f95d9-v1 completed on session-hivemind-simple. Merged to staging branch. Implementation: 4e7b19a8c20e7de196a047085437a82a746240b0 Final branch HEAD: 242cd0a55f4e95f66990e7e28a717f43593db1da (after auto-format) Advisory Acceptance criteria unmet (spec-coverage gate #15599). This change delivers 1/3 of the issue's acceptance criteria. Unmet: Under the updated PG_ACCESS, a connection to hivemind_shared as hivemind_shared_consumer from source…
H
Problem and intended result The shared hivemind provider (.aidev/shared-hivemind.compose.yml, served at 192.168.3.193:44149) refuses every tavern run from the Polish fleet hosts: FATAL: no pg_hba.conf entry for host "100.64.0.10", user "hivemind_shared_consumer", database "hivemind_shared", no encryption Seen by the #416 (closed) worker and again by the #418 (closed) worker (2026-10-25). Polish hosts reach the provider through a gateway that rewrites their source address to 100.64.0.10.…
H
AIDEV Production Bot (242cd0a5) at 26 Oct 10:14 Merge #420: Document the PL gateway source and how PG_ACCESS reache...
H
AIDEV Production Bot (242cd0a5) at 26 Oct 10:14 Merge #420: Document the PL gateway source and how PG_ACCESS reache... ... and 1 more commit
H
AIDEV Production Bot (4e7b19a8) at 26 Oct 10:05 Document the PL gateway source and how PG_ACCESS reaches a running ...
H
AIDEV Production Bot (a751721d) at 26 Oct 09:58 Merge #421: Trust the inter-site VPN range on the shared hivemind s... ... and 1 more commit
H
Retested on denser.discuss.peerverity.info Version: 0221e50d, 2026-10-26 (CET), guest4test2 signed in with a real Google Drive wallet that holds only the posting key (console: "Obtained Google Drive wallet … guest4test2 posting"). Desktop Chrome: ✅ Transfer 0.001 HIVE to guest4test1 with memo → "Key Not Found" → Cancel (10:36:59): the whole flow closed (confirm, memo dialog and form), no dialogs left. Console: one INFO line User cancelled operation in %s — no toast with transfer, no red errors,…
H
Summary account_history_api.get_transaction with include_reversible=true resolves a transaction from a reversible block in two steps that are not synchronized with block processing. If the block is popped between them, which every fork switch does to the blocks of the old branch, the call dereferences an empty block pointer and hived crashes. The same lookup path has four more defects, listed below. Only calls with include_reversible=true are affected. condenser_api.get_transaction and…
H
Update on the 09:55 failure: the same "Couldn't connect to chat." just happened in Firefox Focus on mobile (around 10:20 CET), and this time Try again fixed it. So it's probably not the Chrome Custom Tab; in Chrome, switching to a normal tab may simply have taken long enough. More likely the login-token rate limit: we'd signed in and switched between guest4test, guest4test1 and guest4test2 several times within a few minutes, on desktop and mobile. If so, the drawer showed the error instead of…
H
Retested the native chat drawer on denser.discuss.peerverity.info Version: 0221e50d, 2026-10-26 (times CET = UTC+1). Desktop Chrome + OPPO Reno 15 Pro 5G (Chrome 155.0.8059.79, Firefox Focus). Works Desktop, guest4test1 (Safe Storage), drawer warmed: messages shown 0.35 s after the click (09:37:33). Reload and open right away (before the idle warm-up): 1.16 s, only whoami, no new login token (#1317 (closed) ✅). New tab, warmed: 0.33 s, no mint. Send in General; live receive between users…
H
Context get_ops_in_block and get_transaction live in account_history_api because their data comes from the account history plugin. Before appbase they were part of database_api; aa8560b19 (2017-07-24, "Updated database_api to be db_api and moved account history specifc calls to account_history_api") moved them out for exactly that reason. #962 shows the cost: their results depend on the node's account history filter. This issue is about where these calls should live and how they relate to the…
H
Problem get_ops_in_block and get_transaction are block- and transaction-level queries: neither takes an account. On a node that runs account_history_rocksdb with account-history-rocksdb-track-account-range, account-history-rocksdb-whitelist-ops or account-history-rocksdb-blacklist-ops, both return results that depend on that node-local configuration, and nothing in the response says that anything was filtered. The shipped exchange configuration (scripts/exchange_instance.conf) is such a node:…
H
Summary The import report of account_history_rocksdb (printed every 10,000 blocks and at the end of a reindex: "N operations have been filtered out due to configured options", "M accounts have been filtered out due to configured options") shows wrong numbers whenever account-history-rocksdb-track-account-range is set. Stored data and API results are not affected, but this log is what an operator uses to check that the filter is configured correctly. Defects Inverted. _excludedAccountCount +=…
H
Summary account_history_rocksdb_plugin still contains history pruning (prunePotentiallyTooOldItems), but nothing can enable it: _prune is initialized to false and never assigned. The code has been unreachable since 2018 and has become wrong since then, so it should be removed rather than fixed. Details _prune is declared false (account_history_rocksdb_plugin.cpp:385); its only reader is the guard in buildAccountHistoryRecord (:987). How it got here: Commit Date Change 7e752a6a7 2018-02-07…
H
Retested on denser.discuss.peerverity.info Version: 0221e50d (2026-10-26, ~09:30 CET), desktop Chrome + OPPO Reno 15 Pro 5G (Chrome 155.0.8059.79, Firefox Focus). Logged out. ✅ All tab, six scrolls: 30 → 60 → 90 → 117 → 128 → 149 → 152 cards, all unique proposal ids. No duplicates on mobile either. ✅ No-match search (zzqxnomatch): no cards left on screen, "No loaded proposal matches your search." Same on both mobile browsers. ✅ Clearing the search brings back 152 unique cards starting at #373…
H
Ready for review: !415 applies the null / steem.dao clears in the balance, savings and rewards pipelines and closes this issue on merge. @mzander is the assignee and reviewer. The MR description covers how existing installs correct themselves at the next clear, so no backfill is needed.
H
Ready for review: !537 adds GET /hafbe-api/hardforks and GET /hafbe-api/hardforks/{block-num} and closes this issue on merge. @mzander is the assignee and reviewer. The MR was rebased onto develop on 2026-10-26.
H
mcfarhat (6a6b90e6) at 26 Oct 08:14 Hardforks: read the hafbe_app context's applied_hardforks_view (rev... ... and 7 more commits
H
Dima Rifai (77e68253) at 22 Oct 05:43 Issue #823 - Fix the ja/zh colon, Communities empty text and error ... ... and 1 more commit
H
Dima Rifai (571f620d) at 22 Oct 05:07 Issue #823 - Keep the Subscribers export progress visible during a ...
H
Live verification: working (integration 0ed11c2c on https://denser.discuss.peerverity.info, 2026-10-22) At 390px on /blog/@sagarkothari88/posts, the four HiveSuite 0.1.0 cards from #1280 (closed) now have single spaces between the joined blocks, still on 3 lines (60px box, line-clamp 3), 170 to 178 characters: "HiveSuite Development Snaps Feed Scroll Improvements Reliable Scroll-to-Top Behavior Improved the scroll-to-top experience acros…" "HiveSuite Hive Joiners Feed Improvements Infinite…
H
Workflow promote-session-denser-shakedown-1792641153 completed on session-denser-shakedown. Merged to staging branch. Merge commit: 0ed11c2cd60df964022170970e02d3c54be1dcc0
H
AIDEV Production Bot (0ed11c2c) at 22 Oct 03:54 Merge #1282: Collapse whitespace runs in body-derived post card sum... ... and 1 more commit
H
Problem and intended result Follow-up to #1280 (closed). A card summary produced by extractBodySummary in apps/blog/lib/post-summary.ts contains runs of several spaces where markdown blocks (headings, paragraphs, list items, emphasis) were joined. Because CardDescription in apps/blog/features/list-of-posts/summary.tsx is whitespace-pre-wrap, the runs show as wide gaps. Seen live at 390px on /blog/@sagarkothari88/posts on 2026-10-22: "HiveSuite Development Snaps Feed Scroll Improvements Reliable…
H
Workflow 1282-post-card-summaries-built-fro-sc0cae4ab-v1 completed on session-denser-shakedown. Merged to staging branch. Implementation: 9a1724fdedc5802908164d0600895dd5524bc87e Final branch HEAD: 0ed11c2cd60df964022170970e02d3c54be1dcc0 (after auto-format) Advisory Spec coverage not evaluated (#11829). spec coverage not evaluated — the issue declares no integration points. Declare them in an ## Integration points block (aidev integration-points propose --issue N drafts one from the prose).
H
AIDEV Production Bot (0ed11c2c) at 22 Oct 03:52 Merge #1282: Collapse whitespace runs in body-derived post card sum...
H
AIDEV Production Bot (0ed11c2c) at 22 Oct 03:52 Merge #1282: Collapse whitespace runs in body-derived post card sum... ... and 1 more commit
H
AIDEV Production Bot (9a1724fd) at 22 Oct 03:24 Collapse whitespace runs in body-derived post card summaries (#1282) ... and 77 more commits
H
renovate-bot (ea534e3a) at 22 Oct 03:10 chore(deps): Update python Docker tag to v3.15 ... and 5 more commits
H
This MR contains the following updates: Package Type Update Change python final digest f6a589d → 01ddf82 ⚠️ This updates CI infrastructure. Trigger manual image build jobs in this MR before merging to confirm it's working. Configuration 📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied. ♻️ Rebasing: Whenever MR becomes conflicted, or you tick the…