-
Notifications
You must be signed in to change notification settings - Fork 0
All issues
Issue creation is restricted in this repository
- #49 · renovate opened
on Mar 19, 2026 2
Issues
is:issue state:open
is:issue state:open
Search results
Replication: table created by replication is treated as locally schema-defined, so later attributes from the source are rejected (error per attribute per message)
area:replicationReplication, cluster sync, peer connectionsReplication, cluster sync, peer connectionsbugSomething isn't workingSomething isn't workingP2Priority: P2Status: Open.Freshly cloned node's workers have empty
server.nodesfor minutes — replicated operations silently reach zero peersarea:clusteringClustering, sharding, replication topologyClustering, sharding, replication topologyarea:replicationReplication, cluster sync, peer connectionsReplication, cluster sync, peer connectionsbugSomething isn't workingSomething isn't workingP1Priority: P1Status: Open.oxlint config does not inherit core's no-restricted-imports, so the node:assert/strict ban is unenforced in Pro
area:ciCI workflows, GitHub Actions, release automationCI workflows, GitHub Actions, release automationtestsMostly focused on tests, testing infrastructure, etc.Mostly focused on tests, testing infrastructure, etc.Status: Open.#736 In HarperFast/harper-pro;Four replication config knobs are silently inert: env.get resolves only names registered in CONFIG_PARAMS
bugSomething isn't workingSomething isn't workingStatus: Open.#734 In HarperFast/harper-pro;Replication receive path: the inbound frame queue is unbounded — one worker retained 43 GB of raw WS frames at the inbound line rate and OOM-cycled the node
area:replicationReplication, cluster sync, peer connectionsReplication, cluster sync, peer connectionsbugSomething isn't workingSomething isn't workingStatus: Open.#733 In HarperFast/harper-pro;- Status: Open.#730 In HarperFast/harper-pro;
- Status: Open.#729 In HarperFast/harper-pro;
Published Dockerfiles set ENV NODE_HOSTNAME=localhost, silently disabling replication after an in-place 4.x→5.x upgrade
bugSomething isn't workingSomething isn't workingStatus: Open.#728 In HarperFast/harper-pro;- Status: Open.#727 In HarperFast/harper-pro;
add_ssh_key: durable writes precede an untimed api.github.com fetch, so a concurrent delete_ssh_key leaves a revoked key live on every peer
bugSomething isn't workingSomething isn't workingStatus: Open.#724 In HarperFast/harper-pro;add_ssh_key generate=true: a minted key is unusable on peers with different secret custody, and same-name generates diverge — both reported as success
area:replicationReplication, cluster sync, peer connectionsReplication, cluster sync, peer connectionsbugSomething isn't workingSomething isn't workingStatus: Open.#723 In HarperFast/harper-pro;ssh/config is written without a lock by parallel threads: a corrupt config disables every deploy key on the node
area:clusteringClustering, sharding, replication topologyClustering, sharding, replication topologybugSomething isn't workingSomething isn't workingStatus: Open.#722 In HarperFast/harper-pro;