Skip to content
Snippets Groups Projects

Repository graph

You can move around the graph by using the arrow keys.
Select Git revision
  • 127-eliminate-more-references-to-hive_posts_view
  • 221-vacuum-hivemind-tables
  • 267-rebased-onto-develop
  • 267-update-notification-cache
  • 676-as-tiny-assets
  • 72-postgres-warning-about-wrong-collation-in-recursive_deps-2
  • abw_ecv_op_experiment
  • abw_max_retries
  • abw_post_delete_fix
  • abw_rshares_experiment
  • add-git-to-requirements
  • add-vote-info
  • arc-get-content-deleted
  • as-tmp-to-remove
  • asuch-limit-follows
  • asuch-postgrest-fixing-problems
  • asuch-replace-python-with-sql-get-follow-count
  • asuch-tmp-wip-condenser-get-blog
  • autoexplain-python
  • bridge_api.get_ranked_posts_fixes
  • 1.27.11rc3 protected
  • 1.27.11rc2 protected
  • 1.27.11rc1 protected
  • 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
40 results
Created with Raphaël 2.2.018Dec1716151411109875432130Nov282726252423222120191817161413121312111098765432Eliminated unstable ordering during update_notification_cache call.Fixed notification_cache identity restart problems.branch 'mi_notification_cache_id' of gitlab.syncad.com:hive/hivemind into mi_notification_cache_idNotification autoinrement ID shall be reset on each notification cache table truncation.Updated upgrade procedure to enforce notification cache refill.Notification autoinrement ID shall be reset on each notification cache table truncation.notification cache use autoincrement idMerge branch 'bw_notification_fix2' into 'develop'Another temp. fix related to ID generation.Merge branch 'bw_notification_id_fix' into 'develop'notification id generation fixRemove a few packagesdockerfile-upda…dockerfile-update-fixUpdate Dockerfile with some fixes to make sure we don't get "Python.h not found" or "limits.h not found" - some packages might be redundant, however, I can't pinpoint what was the exact issue, so think of this as a duct tape measure.Mock blocks moved forvard. Removed not needed data from mock blocks. Updated tests.Rebase to current developAdd mock file to comand line parameterTemporarily set RUNNER_HIVEMIND_SYNC_MAX_BLOCK inside script to new valueOptimized bridge_api.get_follow_list. Anyway code still needs to be refactored and redesigned.Merge branch 'bw_post_initial_sync_fixes' into 'develop'Merge branch 'abw_get_discussions_by_feed_fixes' into 'develop'Supplemented commit revision for runtime migration.Fixed delete operation support for scenario: reblog/delete/reblog in the same pack of blocks. Added mock data for tests.- Fixed bug causing to leave all old reputation data (which shall be truncated)[ABW]: removed tabsMerge branch 'abw_get_discussions_by_feed_fixes' of gitlab.syncad.com:hive/hivemind into abw_get_discussions_by_feed_fixes[ABW]: fexed validation of author in bridge.get_account_posts/feed and condenser_api.get_discussions_by_feedunused functions removedadd comment for tracking internal query of bridge_get_account_posts_by_replies in pgheroOptimize bridge_get_account_posts_by_replies further by using a sub select.Optimize bridge_get_account_posts_by_replies by moving "ORDER BY ar.id DESC" out of inner query so that optimizer doesn't think it should do a sequential scan of hive_posts (the LIMIT + ORDER BY seems to have led it astray). Previous code was too slow when the author didn't have any posts that could be replied to.Sortable table in report html fileSet basepython=python3. Just in cas if user has python 2.x installedRebase to current developRebase to current developTests updateMerge branch 'dk-sql-file-list' of gitlab.syncad.com:hive/hivemind into dk-sql-file-listfollow mock with mute and follow_mute for condenser_api/get_discussions testsMerge branch 'bw_get_account_posts_by_replies_perf_fix' into 'develop'Eliminated hack preventing Postgres from using bad index during query. Seems working correctly now without it.Added generated constants file
Loading