weixin_39598941的博客

Any update on this?

Having a consistent ordering would be helpful to eliminate production-only surprises, but I think there's still a fundamental underlying issue. Having multiple reference.conf files that define the same property is not really a valid configuration, and even if the order were deterministic, it might not be what a particular application wants. The ambiguity needs to be detected and resolved in application.conf.

I think it would be helpful to detect and warn or fail on an overwrite within the same "layer".

Right now, conflicts can sometimes work by coincidence depending on the classpath order, and then fail in production in a surprising way because of an incidental change in classpath order.

I'm getting:

Fri, 24 Nov 2017 03:51:17 GMT | starting dump Fri, 24 Nov 2017 03:51:17 GMT | got 1 objects from source elasticsearch (offset: 0) Fri, 24 Nov 2017 03:51:19 GMT | Error Emitted => "Content-Type header [application/octet-stream] is not supported" Fri, 24 Nov 2017 03:51:19 GMT | Total Writes: 0 Fri, 24 Nov 2017 03:51:19 GMT | dump ended with error (set phase) => Content-Type header [application/octet-stream] is not supported

Same issue here...

I've got the same issue

Fri, 24 Nov 2017 03:14:03 GMT | starting dump Fri, 24 Nov 2017 03:14:03 GMT | got 100 objects from source elasticsearch (offset: 0) Fri, 24 Nov 2017 03:14:04 GMT | sent 100 objects to destination elasticsearch, wrote 0 Fri, 24 Nov 2017 03:14:05 GMT | got 100 objects from source elasticsearch (offset: 100) Fri, 24 Nov 2017 03:14:06 GMT | sent 100 objects to destination elasticsearch, wrote 0 Fri, 24 Nov 2017 03:14:06 GMT | got 100 objects from source elasticsearch (offset: 200) Fri, 24 Nov 2017 03:14:07 GMT | sent 100 objects to destination elasticsearch, wrote 0 Fri, 24 Nov 2017 03:14:07 GMT | got 100 objects from source elasticsearch (offset: 300) Fri, 24 Nov 2017 03:14:07 GMT | sent 100 objects to destination elasticsearch, wrote 0 (...)

I do see an _id field in my json file...

Thanks for this option, it's awesome ! Are things missing before it can be merged ? Just to have an idea of when it will included in a release :)

any Idea? :/

PHP 5.4.0 tryed also PHP 5.4.8, PHP 5.3.8 hosting at A2 Hosting..

I had to use slightly different SQL to get it to work:

 bash
sqlite3 '/Library/Application Support/com.apple.TCC/TCC.db' 'update access set allowed=1 where client like "%org.shiftitapp.ShiftIt%"'

Note: - Different app ID org.shiftitapp.ShiftIt instead of com.grapewave.ShiftIt - Missing set keyword in the original

I just wanted to say thank you for continuing to review and merge pull requests at all!

Thanks, & . That wiki page looks great (I just fixed one minor typo in it).

I can confirm that after regenerating the initializer, we haven't seen the deprecation message again, and we haven't noticed any other upgrade problems either.

I just ran across https://github.com/justinfrench/formtastic/wiki/Upgrading-to-Formtastic-3.1 but it looks like it was forgotten :smile:

Thanks . We're still looking into this on our end, too.

It looks like adding this line to the initializer suppresses the message: https://github.com/justinfrench/formtastic/blob/master/lib/generators/templates/formtastic.rb#L96

 ruby
Formtastic::FormBuilder.input_class_finder = Formtastic::InputClassFinder

So maybe the best approach is to either mention that in the deprecation message, or issue a separate warning if that's undefined. It would be helpful to have an upgrade guide in the README, too. Happy to help out, but I'm not sure what else would need to be in there. Is it best to re-run rails generate formtastic:install on each upgrade?

could you raise a new issue (and ideally a pull request) for updating the doc example please?

It is already in the documentation:

https://github.com/lightbend/config/blob/master/HOCON.md#substitutions

Substitutions are not parsed inside quoted strings. To get a string containing a substitution, you must use value concatenation with the substitution in the unquoted portion:

key : ${animal.favorite} is my favorite animal

Or you could quote the non-substitution portion:

key : ${animal.favorite}" is my favorite animal"

I'm having the same issue as