db_sucker 3.1.0 → 3.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1bad32bfbe4d3e2a24def83464a9bdce5c1c7f3158f558ed405d15967adc1b4e
-  data.tar.gz: b5518954de8c6633ac22979b53f225eb7ad1e609fc191931290287479da69547
+  metadata.gz: a5629ff79f3a0b48bf58f3a19c3f3f342082d76ae896ffca04d781e19de8959d
+  data.tar.gz: 0601cd98271331cd62ffbda5f7ae0c6ecd27333bad3598229b224d5bceef586b
 SHA512:
-  metadata.gz: aa025dc2bf4dac913e9e4a7295980d8030cb795cedb6edcd458d26783f8349499879bbb6520a2d09e9f1dc879e531656c7e639119fcee80e0b36df613748723c
-  data.tar.gz: 55f8415d7f31e16d6b6d8aec346c37ce8cd30112d4f5aaa516200dd2a75c92099ed31994d2691cba1e360f36807f93b638ae83a1c4fa367e02bfa8922b01d97f
+  metadata.gz: 2f856a743e274a0a4caf46aa614268d14e92ea40f63cc60f248d7561ddc421c260ddec37542b5a1095e8f6b1b654e8afc4616dd8191170251a48d67ba40645cf
+  data.tar.gz: 3a633a3ca67f10b3f0914b8a4b5c7fa6355d4b471a94dab1b8423135919b6b183b4accce904b2a350394e17601715dfa24410f43873e79cc839dd0367bfe3a55

data/CHANGELOG.md

@@ -1,3 +1,11 @@
+## 3.1.1
+
+### Fixes
+
+* Prevent a single task (running in main thread) to summon workers (and fail) when getting deferred
+
+-------------------
+
 ## 3.1.0
 
 ### Fixes

data/README.md

@@ -19,7 +19,7 @@ This tool is meant for pulling live data into your development environment. **It
 * independent parallel dump / download / import cycle for each table
 * verifies file integrity via SHA
 * flashy and colorful curses based interface with keyboard shortcuts
-* more status indications than you would ever want (even more if the remote has a somewhat recent `pv` (pipeviewer) installed)
+* more status indications than you would ever want (even more if the remote has `pv` (pipeviewer) >= 1.3.8 installed)
 * limit concurrency of certain type of tasks (e.g. limit downloads, imports, etc.)
 * uses more threads than any application should ever use (seriously it's a nightmare)
 
@@ -32,7 +32,7 @@ Currently `db_sucker` only handles the following data-flow constellation:
 
 On the local side you will need:
   - unixoid OS
-  - Ruby (>= 2.0, != 2.3.1 see gotchas)
+  - Ruby (>= 2.0, != 2.3.0 see [Caveats](#caveats---bugs))
   - mysql2 gem
   - MySQL client (`mysql` command will be used for importing)
 
@@ -42,6 +42,7 @@ On the remote side you will need:
   - any folder with write permissions (for the temporary dumps)
   - mysqldump executable
   - MySQL credentials :)
+  - Optional: Install "pv" aka pipeviewer with a version >= 1.3.8 for progress displays on remote tasks
 
 
 ## Installation
@@ -50,9 +51,13 @@ Simple as:
 
     $ gem install db_sucker
 
-At the moment you are advised to adjust the MaxSessions limit on your remote SSH server if you run into issues, see Caveats.
+You will need mysql2 as well (it's not a dependency as we might support other DBMS in the future):
 
-You will also need at least one configuration, see Configuration.
+    $ gem install mysql2
+
+At the moment you are advised to adjust the MaxSessions limit on your remote SSH server if you run into issues, see [Caveats](#caveats---bugs).
+
+You will also need at least one configuration, see [Configuration](#configuration-for-sucking---yaml-format).
 
 
 ## Usage
@@ -130,7 +135,7 @@ DbSucker has a lot of settings and other mechanisms which you can tweak and util
 
 ## Deferred import
 
-Tables with an uncompressed filesize of over 50MB will be queued up for import. Files smaller than 50MB will be imported concurrently with other tables. When all those have finished the large ones will import one after another. You can skip this behaviour with the `-n` resp. `--no-deffer` option. The threshold is changeable in your `config.rb`, see Configuration.
+Tables with an uncompressed filesize of over 50MB will be queued up for import. Files smaller than 50MB will be imported concurrently with other tables. When all those have finished the large ones will import one after another. You can skip this behaviour with the `-n` resp. `--no-deffer` option. The threshold is changeable in your `config.rb`, see [Configuration](#configuration-application---ruby-format).
 
 
 ## Importer
@@ -170,7 +175,7 @@ Under certain conditions the program might softlock when the remote unexpectedly
 If you get warnings that SSH errors occured (and most likely tasks fail), please do any of the following to prevent the issue:
 
   * Raise the MaxSession setting on the remote SSHd server if you can (recommended)
-  * Lower the amount of slots for concurrent downloads (see Configuration)
+  * Lower the amount of slots for concurrent downloads (see [Configuration](#configuration-application---ruby-format))
   * Lower the amount of consumers (not recommended, use slots instead)
 
 You can run basic SSH diagnosis tests with `db_sucker <config_identifier> -a sshdiag`.

data/VERSION

@@ -1 +1 @@
-3.1.0
+3.1.1

data/lib/db_sucker/application/sklaven_treiber/worker/routines.rb

@@ -247,7 +247,9 @@ module DbSucker
 
           def _l_wait_for_workers
             @perform << "l_import_file_deferred"
-            Thread.main.sync { Thread.main[:summon_workers] += 1 }
+            unless Thread.current[:managed_worker] == :main
+              Thread.main.sync { Thread.main[:summon_workers] += 1 }
+            end
             wait_defer_ready
           end
 

data/lib/db_sucker/version.rb

@@ -1,4 +1,4 @@
 module DbSucker
-  VERSION = "3.1.0"
+  VERSION = "3.1.1"
   UPDATE_URL = "https://raw.githubusercontent.com/2called-chaos/db_sucker/master/VERSION"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: db_sucker
 version: !ruby/object:Gem::Version
-  version: 3.1.0
+  version: 3.1.1
 platform: ruby
 authors:
 - Sven Pachnit
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-04-10 00:00:00.000000000 Z
+date: 2018-06-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: curses