Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Apr 09 18:08
    ddfreyne labeled #1543
  • Apr 05 09:55

    ddfreyne on 4.12.1

    Always write stack trace backwa… Merge branch 'stack-trace-alway… Expand paths in a more backward… and 5 more (compare)

  • Apr 05 09:55

    ddfreyne on 4.12.0

    (compare)

  • Apr 05 09:54

    ddfreyne on main

    Always write stack trace backwa… Merge branch 'stack-trace-alway… Expand paths in a more backward… and 5 more (compare)

  • Apr 05 09:53

    ddfreyne on 4.12.1

    (compare)

  • Apr 05 09:15
    ddfreyne commented #1543
  • Apr 05 09:14
    ddfreyne commented #1543
  • Apr 05 09:04

    ddfreyne on bundler

    (compare)

  • Apr 05 09:03

    ddfreyne on main

    Bump kramdown from 2.3.0 to 2.3… Merge pull request #254 from na… (compare)

  • Apr 05 09:03
    ddfreyne closed #254
  • Apr 04 08:53

    ddfreyne on main

    Upgrade Rubocop (compare)

  • Mar 29 16:38
    dependabot[bot] labeled #254
  • Mar 29 16:38
    dependabot[bot] opened #254
  • Mar 29 16:38

    dependabot[bot] on bundler

    Bump kramdown from 2.3.0 to 2.3… (compare)

  • Mar 24 19:21
    Ecco edited #1543
  • Mar 24 19:20
    Ecco opened #1543
  • Mar 22 10:09
    iay commented #1541
  • Mar 17 20:30

    ddfreyne on main

    Expand paths in filesystem data… Merge branch 'expand-dirs-in-fi… Add universal license at root (compare)

  • Mar 09 20:39
    tammersaleh edited #1542
  • Mar 09 20:38
    tammersaleh closed #1542
Gregory Pakosz
@gpakosz
what are gem update --system and gem update for?
Gregory Pakosz
@gpakosz
Hmm I thought all the Ruby 2.7 warnings were solved
/home/vagrant/.bundle/ruby/2.7.0/gems/nanoc-cli-4.11.16/lib/nanoc/cli/commands/show-plugins.rb:17: warning: already initialized constant Nanoc::CLI::Commands::ShowPlugins::PLUGIN_CLASS_ORDER
/home/vagrant/.bundle/ruby/2.7.0/gems/nanoc-cli-4.11.16/lib/nanoc/cli/commands/show-plugins.rb:17: warning: previous definition of PLUGIN_CLASS_ORDER was here
/home/vagrant/.bundle/ruby/2.7.0/gems/nanoc-cli-4.11.16/lib/nanoc/cli/commands/show-plugins.rb:22: warning: already initialized constant Nanoc::CLI::Commands::ShowPlugins::PLUGIN_CLASSES
/home/vagrant/.bundle/ruby/2.7.0/gems/nanoc-cli-4.11.16/lib/nanoc/cli/commands/show-plugins.rb:22: warning: previous definition of PLUGIN_CLASSES was here
/home/vagrant/.bundle/ruby/2.7.0/gems/nanoc-cli-4.11.16/lib/nanoc/cli/commands/view.rb:19: warning: already initialized constant Nanoc::CLI::Commands::View::DEFAULT_HANDLER_NAME
/home/vagrant/.bundle/ruby/2.7.0/gems/nanoc-cli-4.11.16/lib/nanoc/cli/commands/view.rb:19: warning: previous definition of DEFAULT_HANDLER_NAME was here
3 replies
Gregory Pakosz
@gpakosz
damn docker fs is so slow
running nanoc live from within the container is not really bearable
Denis Defreyne
@ddfreyne
I think I told you that the Docker filesystem is unbearably slow :D
Sad but true
Gregory Pakosz
@gpakosz
even bundle exec nanoc view takes ages to start :(
Gregory Pakosz
@gpakosz
I don't remember is Nanoc's tmp dir configurable?
Gregory Pakosz
@gpakosz
Also did something changed with nanoc view?
previously, when using Vagrant, I could forward port 3000 from host to guest guest
and just launch $ bundle exec nanoc view
now I need to do $ bundle exec nanoc view -o 0.0.0.0
Gregory Pakosz
@gpakosz
in that respect I wish cri was able to read options from environment variables
3 replies
Denis Defreyne
@ddfreyne
I think nanoc view defaults to binding to localhost only
(which makes sense from a security point of view)
Gregory Pakosz
@gpakosz
which doesn't make sense for a dev tool
I mean who serves a site with nanoc view?
:)
Gregory Pakosz
@gpakosz
does nanoc view still require adsf?
and what to do when trying to connect live reload yields Cannot download livereload.js
Gregory Pakosz
@gpakosz
hmm seems to be caused by
#<Thread:0x00007f98a1d07280 /usr/local/lib/ruby/gems/2.7.0/gems/guard-livereload-2.5.2/lib/guard/livereload/reactor.rb:11 run> terminated with exception (report_on_exception is true):
/usr/local/lib/ruby/gems/2.7.0/gems/eventmachine-1.2.7/lib/eventmachine.rb:531:in `start_tcp_server'14:17:51 - INFO - Guard is now watching at '/Users/greedo/Projects/myscript_sdk/doc'
: no acceptor (port is in use or requires root privileges) (RuntimeError)
        from /usr/local/lib/ruby/gems/2.7.0/gems/eventmachine-1.2.7/lib/eventmachine.rb:531:in `start_server'
        from /usr/local/lib/ruby/gems/2.7.0/gems/guard-livereload-2.5.2/lib/guard/livereload/reactor.rb:51:in `block in _start_reactor'
        from /usr/local/lib/ruby/gems/2.7.0/gems/eventmachine-1.2.7/lib/eventmachine.rb:171:in `run'
        from /usr/local/lib/ruby/gems/2.7.0/gems/guard-livereload-2.5.2/lib/guard/livereload/reactor.rb:50:in `_start_reactor'
        from /usr/local/lib/ruby/gems/2.7.0/gems/guard-livereload-2.5.2/lib/guard/livereload/reactor.rb:11:in `block in initialize'
I'm using bundle exec nanoc live -L -V
apparently I can't use nanoc live -L if I have guard live reload
it's both logical and so confusing
Gregory Pakosz
@gpakosz
Also @ddfreyne , a bigger timeout doesn't always help
I'm still hitting
Magick::ImageMagickError: unable to open image `/vagrant/output/images/convert-batch.png': No such file or directory @ error/blob.c/OpenBlob/2874

Current item: /tools/inktool/overview.md (:default representation)

  0. _factory/lib/images.rb:43:in `ping'
  1. _factory/lib/images.rb:43:in `image'
  2. item /tools/inktool/overview.md (rep default):185:in `get_binding'
Item A depends on Image B. And Item A's compilation tries to open image in output/ before it has arrived
I'm not sure if you commented that already but imho when an item A depends on a binary item B, the only correct option is to wait for item B to arrive in output/ before launching compilation of item A. Is it what Nanoc is currently doing?
2 replies
Gregory Pakosz
@gpakosz
damn and guard doesn't work with Vagrant :(
Gregory Pakosz
@gpakosz
is there a way I can ask nanoc live to launch guard -p to force polling ?
Denis Defreyne
@ddfreyne
@gpakosz I think in that case, I’d run nanoc live and guard separately
nanoc live (the one that is provided by guard-nanoc) is a thin wrapper around both
Gregory Pakosz
@gpakosz
you meant nanoc view and guard?
Denis Defreyne
@ddfreyne
Yep, sorry
Harald
@a4z

what it the 'trick' in the blogging extension, why the question if items are frozen, and if, the data gets assigned to a variable just to return that

      blk = -> { @items.select { |item| item[:kind] == 'article' } }
      if @items.frozen?
        @article_items ||= blk.call
      else
        blk.call
      end

I can understsand that there might be some caching wanted, and that the result is returned if it exists
or does this something different?
but why the items.frozen question ? if this is not the case there is no caching, when is which branch relevant?

Harald
@a4z
my second question for this evening is, is there a way to influence that certain item will pe written out after others ?
3 replies
Denis Defreyne
@ddfreyne
@a4z Yep, that is related to caching. The list of items is becomes frozen after preprocessing
Ian Young
@iay
Are the people having performance issues with the host file system in Docker running on Macs? The main issue is not file system speed per se but the overhead required to get bidirectional consistency. There are mount options that can improve performance a fair bit depending on what you're doing. See https://docs.docker.com/docker-for-mac/osxfs-caching/ for details.
Ran into this on a project I was working on recently: https://github.com/iay/shibboleth-build-docker/blob/master/README.md#performance
(The workround we used -- temporarily moving the data to /tmp in the container -- obviously wouldn't apply here)
Denis Defreyne
@ddfreyne
@iay So far I’ve avoided using Docker on Mac because of speed issues…
Harald
@a4z
is there a way to call compile from the post processign step?
Gregory Pakosz
@gpakosz
no because it's a post processing step, compilation and routing have happened by then
Harald
@a4z
hm, that what I have expected, but it is sad, have now all pieces together, and I am super happy, but I have that one use case where I would need to influence that one page is processed after others, and I do not know how to do that
8 replies
Gregory Pakosz
@gpakosz
@ddfreyne hello, do you think you can make a point release with the longer timeout soon?
3 replies
Harald
@a4z

So, if you have one blog index page that depends on all individual articles, you could do e.g. @items.find_all('/articles/*').each(&:path) to force a dependency onto all those pages

A question to this ... what does it mean.. :-) , what does .each(&:path) actually call on the item?
my ruby is not that strong, and from the doc I see there is a path property, but I am unsure how that relates, but I am very interested in understanding .

Denis Defreyne
@ddfreyne
.each(&:path) is the same as .each { |something| something.path } — it’s syntactic sugar
So essentially, it loops over the collection and calls the path method on it
(and the call to #path makes Nanoc record a dependency onto the item that you called the #path methd on)
Harald
@a4z
Thanks for the explanation! so I call the path method on all blog articles, but when do I do that and how does this relate the the blogindex page?
Do I need to have a own rule for the blogindex page and do this in this rule?