bootsnap 1.4.0-java → 1.4.1-java

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b52dcf497cc21a7ce9e7a90d1ce3356c90bfecb2dca0075e9ed18ccd5bd85f46
-  data.tar.gz: 848f3b1c68bc8aff09e7f33990d2d25d64fd0e4349ce5ba5ad99696b06eb69bd
+  metadata.gz: bbe2d60be7b9970d1b993f144e28071bf85ebb528f24df8afbc00e5f4a1df6da
+  data.tar.gz: 2cda0fdec14bcedf1c6e232e75380ee7cabbdec2953428912563a83c39bb9472
 SHA512:
-  metadata.gz: 68f89030acc8fca5f2abaf210ed33cb3cb6f02bf587197f87db2869421496dfc504e0ed1ab04dfc44b3ce1d6d0a5f60fbc4a4520082b833c3cc3d12dcc4751b3
-  data.tar.gz: e4fbeab4eae5e93bbde91b95274cb54521733a06780e1f6d677eb212124ae248370f29e941ed89bcb72cb4ffaa88e4c71a73572f6371376102bd97df89751a9c
+  metadata.gz: 1b8b3cb9986921f82c8c3489c37e33a576587d93ef09fc94b5c7e16e6682d86c54283b34bc659b2a5f1bb60f14d2c1ae272ef2e4a3089d623a36e6e4529c5629
+  data.tar.gz: 85efef308c58141634984fbda14d393f7555333456c57b99e10ae7f8ddc592c3623cbefd0ffc34c2217092407014667dad3744b4b86d367a0f91a82df3f9853c

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+# 1.4.1
+
+* Don't register change observers to frozen objects.
+
 # 1.4.0
 
 * When running in development mode, always fall back to a full path scan on LoadError, making

data/README.md

@@ -24,6 +24,10 @@ If you are using Rails, add this to `config/boot.rb` immediately after `require
 require 'bootsnap/setup'
 ```
 
+Note that bootsnap writes to `tmp/cache`, and that directory *must* be writable. Rails will fail to
+boot if it is not. If this is unacceptable (e.g. you are running in a read-only container and
+unwilling to mount in a writable tmpdir), you should remove this line or wrap it in a conditional.
+
 It's technically possible to simply specify `gem 'bootsnap', require: 'bootsnap/setup'`, but it's
 important to load Bootsnap as early as possible to get maximum performance improvement.
 
@@ -41,12 +45,14 @@ Bootsnap.setup(
   development_mode:     env == 'development', # Current working environment, e.g. RACK_ENV, RAILS_ENV, etc
   load_path_cache:      true,                 # Optimize the LOAD_PATH with a cache
   autoload_paths_cache: true,                 # Optimize ActiveSupport autoloads with cache
-  disable_trace:        true,                 # (Alpha) Set `RubyVM::InstructionSequence.compile_option = { trace_instruction: false }`
+  disable_trace:        true,                 # Set `RubyVM::InstructionSequence.compile_option = { trace_instruction: false }`
   compile_cache_iseq:   true,                 # Compile Ruby code into ISeq cache, breaks coverage reporting.
   compile_cache_yaml:   true                  # Compile YAML into a cache
 )
 ```
 
+**Note that `disable_trace` will break debuggers and tracing.**
+
 **Protip:** You can replace `require 'bootsnap'` with `BootLib::Require.from_gem('bootsnap',
 'bootsnap')` using [this trick](https://github.com/Shopify/bootsnap/wiki/Bootlib::Require). This
 will help optimize boot time further if you have an extremely large `$LOAD_PATH`.

data/lib/bootsnap/load_path_cache/change_observer.rb

@@ -53,6 +53,7 @@ module Bootsnap
       end
 
       def self.register(observer, arr)
+        return if arr.frozen? # can't register observer, but no need to.
         arr.instance_variable_set(:@lpc_observer, observer)
         arr.extend(ArrayMixin)
       end

data/lib/bootsnap/version.rb

@@ -1,3 +1,3 @@
 module Bootsnap
-  VERSION = "1.4.0"
+  VERSION = "1.4.1"
 end

data/shipit.rubygems.yml

@@ -1,4 +0,0 @@
-dependencies:
-  bundler:
-    without:
-      - development

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: bootsnap
 version: !ruby/object:Gem::Version
-  version: 1.4.0
+  version: 1.4.1
 platform: java
 authors:
 - Burke Libbey
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2019-02-11 00:00:00.000000000 Z
+date: 2019-02-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement