Apparently I just needed to restart Safari and it works now.

Thanks for the advice. I learned that bundle update does different things based 
on which directory I'm in.

Craig

> On Jan 23, 2018, at 4:45 PM, Sam Ruby <[email protected]> wrote:
> 
> Works for me on Chrome, Firefox, and Safari.
> 
> Furthermore, the workaround for the Safari issue of continuing to use
> a locally cached copy of the generated JavaScript without checking the
> server to see if there are any updates is in place.
> 
> Anything in the Safari javascript console?
> 
> - Sam Ruby
> 
> On Tue, Jan 23, 2018 at 5:36 PM, Craig Russell <[email protected]> wrote:
>> 
>>> On Jan 23, 2018, at 2:26 PM, Sam Ruby <[email protected]> wrote:
>>> 
>>> Can you try running 'bundle update' with no parameters from the
>>> whimsy/www/project/icla directory?
>> 
>> I had run bundle update from the /srv/whimsy directory and it updated a 
>> bunch of things.
>> 
>> After running bundle update from project/icla it updated a bunch of other 
>> things.
>> 
>> Fetching puma 3.11.2 (was 3.10.0)
>> Installing puma 3.11.2 (was 3.10.0) with native extensions
>> 
>> Fetching ruby2js 3.0.1 (was 2.1.21)
>> Installing ruby2js 3.0.1 (was 2.1.21)
>> 
>> Now project/icla loads ok in Chrome and Firefox but still fails with no 
>> error message on Safari.
>> 
>> Craig
>> 
>>> - Sam Ruby
>>> 
>>> On Tue, Jan 23, 2018 at 5:16 PM, Craig Russell <[email protected]> wrote:
>>>> Hi,
>>>> 
>>>> After pulling the latest from git and trying to load 
>>>> whimsy.local/project/icla:
>>>> 
>>>> Web application could not be started
>>>> It looks like Bundler could not find a gem. Maybe you didn't install all 
>>>> the gems that this application needs. To install your gems, please run:
>>>> 
>>>> bundle install
>>>> If that didn't work, then the problem is probably caused by your 
>>>> application being run under a different environment than it's supposed to. 
>>>> Please check the following:
>>>> 
>>>>       • Is this app supposed to be run as the clr user?
>>>>       • Is this app being run on the correct Ruby interpreter? Below you 
>>>> will see which Ruby interpreter Phusion Passenger attempted to use.
>>>> -------- The exception is as follows: -------
>>>> 
>>>> You have requested: wunderbar >= 1.2.6 The bundle currently has wunderbar 
>>>> locked at 1.2.4. Try running `bundle update wunderbar` If you are updating 
>>>> multiple gems in your Gemfile at once, try passing them all to `bundle 
>>>> update` (Bundler::GemNotFound)
>>>> /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/resolver.rb:396:in
>>>>  `block in verify_gemfile_dependencies_are_found!'
>>>> /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/resolver.rb:366:in
>>>>  `each'
>>>> /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/resolver.rb:366:in
>>>>  `verify_gemfile_dependencies_are_found!'
>>>> /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/resolver.rb:212:in
>>>>  `start'
>>>> /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/resolver.rb:191:in
>>>>  `resolve'
>>>> /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.15.4/lib/bundler/definition.rb:235:in
>>>>  `resolve'
>>>> Craig L Russell
>>>> Secretary, Apache Software Foundation
>>>> [email protected] http://db.apache.org/jdo
>>>> 
>> 
>> Craig L Russell
>> Secretary, Apache Software Foundation
>> [email protected] http://db.apache.org/jdo
>> 

Craig L Russell
Secretary, Apache Software Foundation
[email protected] http://db.apache.org/jdo

Reply via email to