Skip to content
Snippets Groups Projects
Select Git revision
  • cherry-pick-5dd1da34
  • master protected
  • develop default protected
  • 267-update-notification-cache
  • follow-redesign
  • follow-redesign-speedups
  • follow-redesign-tests
  • follow-deltas
  • kbotor/docker-image-rename
  • mi/new_doc
  • remove-notification-id
  • dn-autovacuum
  • kudmich/documentation-update
  • mi/haf#272_remove_rowid
  • mi/haf#259_slow_processing_alarm
  • mi/back_forking_hivemind
  • get-discussion-experiment
  • 221-vacuum-hivemind-tables
  • kudmich/delete-PGRST_DB_ROOT_SPEC-env
  • kudmich/move-nginx-to-postgrest-container
  • 1.27.10 protected
  • 1.27.9 protected
  • 1.27.8 protected
  • 1.27.7rc16 protected
  • 1.27.7rc15 protected
  • 1.27.7rc14 protected
  • 1.27.7rc13 protected
  • 1.27.7rc12 protected
  • 1.27.7rc11 protected
  • 1.27.7rc10 protected
  • 1.27.6rc9 protected
  • 1.27.6rc8 protected
  • 1.27.6rc7 protected
  • 1.27.6rc6 protected
  • 1.27.6rc5 protected
  • 1.27.6rc3 protected
  • 1.27.5 protected
  • 1.27.5rc9 protected
  • 1.27.5rc8 protected
  • 1.27.5.0.0rc7 protected
40 results
Compare
Marcin Ickiewicz's avatar
correctly break sync when test-max-block is used
Marcin authored 
Previously first app_next_block after reaching the limit was commited,
what moves hivemind context to the next block after the limit without
processing it
265b107a
History
Marcin Ickiewicz's avatar 265b107a
History
Name Last commit Last update